
From bob.hinden@gmail.com  Fri Apr  1 00:49:11 2011
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 770BD3A6BFB for <ietf@core3.amsl.com>; Fri,  1 Apr 2011 00:49:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.889
X-Spam-Level: 
X-Spam-Status: No, score=-102.889 tagged_above=-999 required=5 tests=[AWL=0.710, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9U9ter7Yp4PM for <ietf@core3.amsl.com>; Fri,  1 Apr 2011 00:49:11 -0700 (PDT)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by core3.amsl.com (Postfix) with ESMTP id EB0AA3A6BEC for <ietf@ietf.org>; Fri,  1 Apr 2011 00:49:10 -0700 (PDT)
Received: by pzk30 with SMTP id 30so745792pzk.31 for <ietf@ietf.org>; Fri, 01 Apr 2011 00:50:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=56EsI8dTUdgGDiqWGX4sljCyk1WuVykW4EoBvs878gI=; b=sohCUUHl2SJ/JyTAaN6/t9LJRRNVt5YO9Aopwoq3suDyfbWv7O+ZDEKHFn9YHa+WxA 0fJphL+7vCTSmZQMnxp7mf2zodWOWC2uQWEMmYuA0viCGTpXRZafqJGopy/aXdYrwAhf lNHyL6oPABndLOcdoKSPsOkT9CnUp0VEINDIg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=WqIukaXQgIF4sBC3FyGyHJLhXTnT65Hteb7/nkUhY4ARcHZa9A3cwrZYa2eXeDa8sj VzYRlJPrkOQvcirBPE8Dsiok3PSONe6u9IHLeOGzxpRz9cHRU4KGDLdoUd8nvKSQQkWb JNroYsScQS89QiXMZo0pPDkOcoumLfEyKh61c=
Received: by 10.142.148.16 with SMTP id v16mr2860352wfd.447.1301644251070; Fri, 01 Apr 2011 00:50:51 -0700 (PDT)
Received: from dhcp-6337.meeting.ietf.org (dhcp-6337.meeting.ietf.org [130.129.99.55]) by mx.google.com with ESMTPS id m10sm2577348wfl.23.2011.04.01.00.50.48 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 01 Apr 2011 00:50:50 -0700 (PDT)
Subject: Re: IAOC: delegating ex-officio responsibility
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <4D955661.8050502@gmail.com>
Date: Fri, 1 Apr 2011 09:50:45 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <9C81C0F6-3ABE-4479-8C5E-C20C486D052A@gmail.com>
References: <2BE582FA-2682-4232-9D83-23A03F01A0DB@NLnetLabs.nl> <6.2.5.6.2.20110330073936.0e1899d0@resistor.net> <E2E41FDE-3818-4513-9933-CB1E0326B43E@nlnetlabs.nl> <6.2.5.6.2.20110330113947.0c948bc0@resistor.net> <4D942843.4060804@gmail.com> <6.2.5.6.2.20110331120351.09488990@resistor.net> <4D955661.8050502@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1082)
Cc: SM <sm@resistor.net>, Bob Hinden <bob.hinden@gmail.com>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 07:49:11 -0000

Brian,

On Apr 1, 2011, at 6:36 AM, Brian E Carpenter wrote:

> On 2011-04-01 08:38, SM wrote:
>> Hi Brian,
>> At 00:07 31-03-2011, Brian E Carpenter wrote:
>>> And that is exactly the problem with 'non-voting' status in a =
committee
>>> that mainly operates by consensus. It allows people who really ought
>>> to share accountability to apear to avoid it.
>>=20
>> According to IOAC procedures:
>>=20
>>  "All decisions of the members must be approved by majority vote of
>>   the members then in office."
>>=20
>> I don't consider that as operating by consensus. =20
>=20
> That is the tie-break rule. I can't speak for recent IAOCs, but when
> I was a member we esentially always achieved consensus.

In my time on the IAOC, we usually reach consensus, but not always.  The =
votes are recorded in the public minutes. =20

>=20
> But my point is that I believe the IETF Chair *should* have =
accountability
> and that means being a formal voting member.

I agree.

Given the roles the IAB is taking on, such as the selection of an RSE, =
that have a close relationship with the IAOC, I am concerned if the IAB =
Chair is not also a IAOC voting member, or if the vote can or should be =
delegated.  I do note that the IAB chair is different from the IETF =
chair as the IAB chair is selected by the IAB vs. the IETF chair is =
selected directly by the NOMCOM.

Bob




From bob.hinden@gmail.com  Fri Apr  1 06:51:21 2011
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9ED043A6828; Fri,  1 Apr 2011 06:51:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.986
X-Spam-Level: 
X-Spam-Status: No, score=-102.986 tagged_above=-999 required=5 tests=[AWL=0.613, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jAsqBxIoV4ST; Fri,  1 Apr 2011 06:51:20 -0700 (PDT)
Received: from mail-pv0-f172.google.com (mail-pv0-f172.google.com [74.125.83.172]) by core3.amsl.com (Postfix) with ESMTP id E2C5D3A681C; Fri,  1 Apr 2011 06:51:19 -0700 (PDT)
Received: by pve39 with SMTP id 39so824305pve.31 for <multiple recipients>; Fri, 01 Apr 2011 06:53:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:content-type:content-transfer-encoding :subject:date:message-id:cc:to:mime-version:x-mailer; bh=dzqEz20/BZ6NDLxkiD5JZ5/3X9moRntKz4SLmwr7KZI=; b=VAtPh5DtaOAwDB63SKAi7O+jaWSt1iiXKigRjQP7RpldMFZ3MiO+bSxuHK2M+R5jqx qvLjWdhIWUd8D6eRI9yb5rT1lPvlt2dmbSaFhLitNmSv67p3glyUeGPNk8Woa8xezIRi CkMgg/BilsPj6qyldqsaLDAyk4Baxe+bXnYEg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:message-id :cc:to:mime-version:x-mailer; b=O+JgTFjd7B45FmsydXwEOTnx0HTXNrTv/wuHptJ2JuWLzw4a0hRsjFDdJWRQqOzfL4 Td/JYrOYFd+XMzXe/Ofk3pY5ADaxoGimO1VIQ8kQICwzXbMEoXpmd/mTHJalHc6bTTZF 6S5mscjKmRcDuwEmbOhcEGR5dIfdjTMlFKUp0=
Received: by 10.142.150.5 with SMTP id x5mr2985988wfd.419.1301665980274; Fri, 01 Apr 2011 06:53:00 -0700 (PDT)
Received: from dhcp-6337.meeting.ietf.org (dhcp-6337.meeting.ietf.org [130.129.99.55]) by mx.google.com with ESMTPS id o11sm2962615wfa.0.2011.04.01.06.52.57 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 01 Apr 2011 06:52:58 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: IETF Badge Checking
Date: Fri, 1 Apr 2011 15:52:55 +0200
Message-Id: <A71E5A76-A6AA-4646-A757-9124F8151E7D@gmail.com>
To: ietf@ietf.org
Mime-Version: 1.0 (Apple Message framework v1082)
X-Mailer: Apple Mail (2.1082)
Cc: iaoc@ietf.org, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 13:51:21 -0000

There was some discussion at the Wednesday plenary IAOC open mic about =
the badge checking that took place during the Beijing IETF meeting.  I =
thought it would be good to clarify what happened at that meeting.

The IAOC was not aware that badge checking was going to happen prior to =
this meeting. It was implemented by the meeting host in conjunction with =
the hotel. It is our understanding that the host wanted to ensure that =
only registered attendees were given access to the IETF meeting rooms.

Had the IAOC been made aware of this prior to the meeting, we would have =
notified the community, similar to the way we notified the community =
that there would be a need for wireless network login well in advance of =
the Beijing meeting.

In the future if there is a need for badge checking (or network login) =
at an IETF meeting, the IAOC will notify the community as early as =
possible. Also, if we plan meetings in similar venues we will determine =
if anything like this is a local requirement.

Bob Hinden
IAOC Chair



From mail@sabahattin-gucukoglu.com  Fri Apr  1 12:28:53 2011
Return-Path: <mail@sabahattin-gucukoglu.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C89563A6916 for <ietf@core3.amsl.com>; Fri,  1 Apr 2011 12:28:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.962
X-Spam-Level: 
X-Spam-Status: No, score=0.962 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HOST_EQ_MODEMCABLE=1.368, HOST_MISMATCH_COM=0.311, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RDNS_DYNAMIC=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6rNgg5AVoMmF for <ietf@core3.amsl.com>; Fri,  1 Apr 2011 12:28:52 -0700 (PDT)
Received: from Mintaka.sabahattin-gucukoglu.com (sgucukoglu-2-pt.tunnel.tserv8.dal1.ipv6.he.net [IPv6:2001:470:1f0e:7ef::2]) by core3.amsl.com (Postfix) with ESMTP id 209613A693C for <ietf@ietf.org>; Fri,  1 Apr 2011 12:28:51 -0700 (PDT)
Received: from Mintaka.sabahattin-gucukoglu.com ([::ffff:127.0.0.1]:45895) by Mintaka.sabahattin-gucukoglu.com with [XMail 1.27 ESMTP Server] id <S31DFE> for <ietf@ietf.org> from <mail@sabahattin-gucukoglu.com>; Fri, 1 Apr 2011 20:30:31 +0100
Received: from [192.168.1.13] (cpc2-dals7-0-0-cust570.hari.cable.virginmedia.com [82.35.114.59]) (using SMTP over TLS) by Mintaka.sabahattin-gucukoglu.com (tmda-ofmipd) with ESMTP; Fri, 01 Apr 2011 20:30:29 +0100
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Alternative to IPv6 in the Works
Date: Fri, 1 Apr 2011 20:30:25 +0100
Message-Id: <C684ABDF-BCB1-4584-9F48-FDED88CCE3DC@sabahattin-gucukoglu.com>
To: ietf@ietf.org
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
X-Delivery-Agent: TMDA/1.1.12-kg2 (Pluto)
From: Sabahattin Gucukoglu <mail@sabahattin-gucukoglu.com>
X-Primary-Address: mail@sabahattin-gucukoglu.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Sabahattin Gucukoglu <mail-dated-1304278231.e20661@sabahattin-gucukoglu.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 19:28:53 -0000

Hey, we do all the good gags!
http://packetlife.net/blog/2011/apr/1/alternative-ipv6-works/

Well, it's good to know IDs make headlines before they've even made it =
into the repository directories, a sign of changing times no doubt ...

Cheers,
Sabahattin

From johnl@iecc.com  Fri Apr  1 13:27:18 2011
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 236DC3A6964 for <ietf@core3.amsl.com>; Fri,  1 Apr 2011 13:27:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.529
X-Spam-Level: 
X-Spam-Status: No, score=-110.529 tagged_above=-999 required=5 tests=[AWL=0.670, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JRoqeA3JVgpf for <ietf@core3.amsl.com>; Fri,  1 Apr 2011 13:27:17 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by core3.amsl.com (Postfix) with ESMTP id C29BA3A697F for <ietf@ietf.org>; Fri,  1 Apr 2011 13:27:16 -0700 (PDT)
Received: (qmail 89752 invoked from network); 1 Apr 2011 20:28:56 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:mime-version:content-type:vbr-info:user-agent:cleverness; s=15e97.4d963588.k1104; i=johnl@submit.iecc.com; bh=2Jk8dsivambVsNxTC8nJsbK/2V9sesvgMdiDBnTNptY=; b=HGSDM1OjRIG2v4z37KHkKa9ECitzWNNxIEPhIvTn06M0f1CEQuVHY0wIrM9dzaDgLMo/sf4R3isJwKcLm2cOEMN03O2NIbtl24YOJGyuROMMuQTVSDcc84qM+Xhqwz/nyz92kyrwVc3wSexJSWqpCdxvADqBQ4qNU9KkfGPlGNI=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd johnl@64.57.183.62) with (DHE-RSA-AES256-SHA encrypted) SMTP; 1 Apr 2011 20:28:33 -0000
Date: 1 Apr 2011 16:28:55 -0400
Message-ID: <alpine.BSF.2.00.1104011624500.30110@joyce.lan>
From: "John R. Levine" <johnl@iecc.com>
To: ietf@ietf.org
Subject: Buckets of spam coming through IETF lists
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 20:27:18 -0000

Some clever spambot seems to have scraped a bunch of addresses out of the 
archives and is sending spam with multiple addresses on the From: line 
through IETF and IRTF mailing lists.  Surely I'm not the only one who's 
seeing it.

Given the amount of legitimate mail with multiple From: addresses (none, 
in practice) a quick shim in front of Mailman should deal with it until 
someone can go fix the underlying code.

Regards,
John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. http://jl.ly

---------- Forwarded message ----------
Date: Thu, 31 Mar 2011 14:47:22 -0700 (PDT)
From: gil@ISI.EDU, jtb@ISI.EDU, cakers@ISI.EDU, irsg@ISI.EDU, coreyc@ISI.EDU,
     jeanine@ISI.EDU, galstyan@ISI.EDU, rahul@ISI.EDU, end2end-tf@ISI.EDU,
     ns-users@ISI.EDU, ns-commits-owner@ISI.EDU, touch@ISI.EDU, kyamada@ISI.EDU,
     newuser@ISI.EDU, probing@ISI.EDU, csd@ISI.EDU, management-request@ISI.EDU,
     hannes@ISI.EDU, rbates@ISI.EDU
To: gil@ISI.EDU, jtb@ISI.EDU, cakers@ISI.EDU, irsg@ISI.EDU, coreyc@ISI.EDU,
     jeanine@ISI.EDU, galstyan@ISI.EDU, rahul@ISI.EDU, end2end-tf@ISI.EDU,
     ns-users@ISI.EDU, ns-commits-owner@ISI.EDU, touch@ISI.EDU, kyamada@ISI.EDU,
     newuser@ISI.EDU, probing@ISI.EDU, csd@ISI.EDU, management-request@ISI.EDU,
     hannes@ISI.EDU, rbates@ISI.EDU
Subject: [IRSG] An offer you can't refuse


From jaibuduvin@gmail.com  Fri Apr  1 13:42:08 2011
Return-Path: <jaibuduvin@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0737C28C0E3 for <ietf@core3.amsl.com>; Fri,  1 Apr 2011 13:42:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.997
X-Spam-Level: 
X-Spam-Status: No, score=-2.997 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, HTML_OBFUSCATE_05_10=0.001, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id junRLQSa1AAA for <ietf@core3.amsl.com>; Fri,  1 Apr 2011 13:42:07 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id C43B128C0EB for <Ietf@ietf.org>; Fri,  1 Apr 2011 13:42:06 -0700 (PDT)
Received: by wyb29 with SMTP id 29so3686946wyb.31 for <Ietf@ietf.org>; Fri, 01 Apr 2011 13:43:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=oXZR8yZJqaWXmJ05ywQZfHBj/AyLaac2Q6I5ZEe3osY=; b=KDTAUkUfrUxUzgGVIZLENU4PvrLCnhOyEM2nxTFVDBmKrSObwa1pcHH8dxvwybZDm1 VH5FdO6KeVc8/E1V5rdOdm3joUFFvufYKcnsP6f24OOLLSRFrYhIz1kP8lE1URuYS+WQ zeYq8JHbD2HB52DvjcEuef5w9XC6pQwV0mKHE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=aEstA1fAu0/WeNu+a7Spv1xOU0ejRaBRMvyhSBs8x8tW4PBHN5Srpcrgaxd0WUj6L3 59yWctHiVcSB3NJmgc5qaRS9rhiiXu98Uz/k+RbmheoihrWgjwWuLDe5r5EuBFBjvIx2 BryNLvy4jy6bFbtaPr6AzisLk/Pz9CHcQIxt4=
MIME-Version: 1.0
Received: by 10.227.196.208 with SMTP id eh16mr4540798wbb.224.1301690626613; Fri, 01 Apr 2011 13:43:46 -0700 (PDT)
Received: by 10.227.156.203 with HTTP; Fri, 1 Apr 2011 13:43:46 -0700 (PDT)
Date: Fri, 1 Apr 2011 15:43:46 -0500
Message-ID: <AANLkTimh-oRwkyM5FzZGbsrO45bphgV=2YATFJQ-qD3q@mail.gmail.com>
Subject: Alternative To IPv6
From: "J. C. Jones" <jaibuduvin@gmail.com>
To: Ietf@ietf.org
Content-Type: multipart/alternative; boundary=20cf3002592668258e049fe17703
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 20:42:08 -0000

--20cf3002592668258e049fe17703
Content-Type: text/plain; charset=ISO-8859-1

Hi All,

Those associated with the IETF and those with interest in computer
networking might be interested to know that a new, clean-slate network
protocol stack, an alternative to the IPv4 and IPv6, is due out in 2012.
This new protocol stack will provide the following features:


   1. A generalized solution to *naming*, *numbering*, and *addressing
*problems,
   where domain names and IP addresses have been given a sound, theoretical
   basis, with particular emphasis on rethinking the nature of domain names
   with respect to IP addresses. Well-known port numbers would become
   unnecessary for many applications.
   2. A generalized solution to the *mobility *problem, where networks of
   networks may be mobile, with continuously optimal routing from source to
   target and ultra-fast handover over multiple wireless technologies existing
   within the same node that allows PDA's to easily be used as cell phones
   while making and breaking of Wi-Fi links.
   3. A generalized solution to the *multicast *problem, where a PDA might
   serve as the root of a *1,000,000,000*-node multicast tree, and where an
   application sourcing the multicast can be written by a programmer in one
   afternoon whose possesses a near-minimum understanding of computer
   networking.
   4. A generalized solution to the *security *problem, where each feature
   commonly provided by an underlying security framework [hiding, signing,
   etc.] might be independently enabled or disabled without affecting the
   operation of cooperative features.
   5. A generalized solution to the *access control* problem, where
   specifying access control parameters makes sense to technical neophytes,
   where username/passwords are essentially non-existent, and where it is
   plainly evident from the model that it is regular and persistent.
   6. A gratuitous, parasitic framework that, if it were so chosen, would
   allow for the *elimination of the majority of email spam* and similar
   nuisances on the Internet.
   7. A strictly* 99.8% portable* reference implementation for most
   multi-threaded OS's, written in C++.
   8. A network application *library *that presents *persistent primitives
   of computer networking* [C++ classes].
   9. *International support* for almost all of the world's languages, not
   only for domain names, but for all textual processing under the purview of
   the protocol stack. Specifically, almost equal weight will be given for
   non-English languages as for English.
   10. A total executable size of l*ess than 1MB* [without a GUI] for a *
   full-featured* stack destined for small-footprint devices.
   11. *Initial compatibility with IPv4* routing, where new, disruptive
   applications may be created over the new protocol stack without requiring
   changes to existing IPv4 routing. A full-break from IPv4 would require no
   human intervention [renumbering] at the point of change-over, and after
   change-over, said disruptive applications would continue to function,
   unaware that change-over has occurred.
   12. *Simplicity*. The new stack should be understandable in its entirely
   by a single software engineer after 3 months of study.

I will send out notices as the release date in 2012 approaches.

Warm Regards,
-JC

--20cf3002592668258e049fe17703
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi All,<div><br></div><div>Those associated with the IETF and those with in=
terest in computer networking might be interested to know that a new, clean=
-slate network protocol stack, an alternative to the IPv4 and IPv6, is due =
out in 2012. This new protocol stack will provide the following features:</=
div>
<div><br></div><div><ol><li>A generalized solution to <b>naming</b>, <b>num=
bering</b>, and <b>addressing </b>problems, where domain names and IP addre=
sses have been given a sound, theoretical basis, with particular emphasis o=
n rethinking the nature of domain names with respect to IP addresses. Well-=
known port numbers would become unnecessary for many applications.</li>
<li>A generalized solution to the <b>mobility </b>problem, where networks o=
f networks may be mobile, with continuously optimal routing from source to =
target and ultra-fast handover over multiple wireless technologies existing=
 within the same node that allows PDA&#39;s to easily be used as cell phone=
s while making and breaking of Wi-Fi links.</li>
<li>A generalized solution to the <b>multicast </b>problem, where a PDA mig=
ht serve as the root of a <b>1,000,000,000</b>-node multicast tree, and whe=
re an application sourcing the multicast can be written by a programmer in =
one afternoon whose possesses a near-minimum understanding of computer netw=
orking.</li>
<li>A generalized solution to the <b>security </b>problem, where each featu=
re commonly provided by an underlying security framework [hiding, signing, =
etc.] might be independently enabled or disabled without affecting the oper=
ation of cooperative features.</li>
<li>A generalized solution to the <b>access control</b> problem, where spec=
ifying access control parameters makes sense to technical neophytes, where =
username/passwords are essentially non-existent, and where it is plainly ev=
ident from the model that it is regular and persistent.</li>
<li>A gratuitous, parasitic framework that, if it were so chosen, would all=
ow for the <b>elimination of the majority of email spam</b> and similar nui=
sances on the Internet.</li><li>A strictly<b> 99.8%=A0portable</b>=A0refere=
nce implementation for=A0most multi-threaded OS&#39;s, written in C++.</li>
<li>A network application=A0<b>library=A0</b>that presents=A0<b>persistent =
primitives of computer networking</b>=A0[C++ classes].</li><li><b>Internati=
onal support</b> for almost all of the world&#39;s languages, not only for =
domain names, but for all textual processing under the purview of the proto=
col stack. Specifically, almost equal weight will be given for non-English =
languages as for English.</li>
<li>A total executable size of l<b>ess than 1MB</b>=A0[without a GUI] for a=
 <b>full-featured</b> stack destined for small-footprint devices.</li><li><=
b>Initial compatibility with IPv4</b>=A0routing, where new, disruptive appl=
ications may be created over the new protocol stack without requiring chang=
es to existing IPv4 routing. A full-break from IPv4 would require no human =
intervention [renumbering] at the point of change-over, and after change-ov=
er, said disruptive applications would continue to function, unaware that c=
hange-over has occurred.</li>
<li><b>Simplicity</b>. The new stack should be understandable in its entire=
ly by a single software engineer after 3 months of study.</li></ol><div>I w=
ill send out notices as the release date in 2012 approaches.</div><div>
<br></div><div>Warm Regards,</div><div>-JC</div></div>

--20cf3002592668258e049fe17703--

From john-ietf@jck.com  Fri Apr  1 15:34:03 2011
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 61F4B3A698C for <ietf@core3.amsl.com>; Fri,  1 Apr 2011 15:34:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.567
X-Spam-Level: 
X-Spam-Status: No, score=-102.567 tagged_above=-999 required=5 tests=[AWL=0.032, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jb66ttuja7qz for <ietf@core3.amsl.com>; Fri,  1 Apr 2011 15:34:02 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 637443A6981 for <ietf@ietf.org>; Fri,  1 Apr 2011 15:34:02 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1Q5mwQ-000AhZ-Gb; Fri, 01 Apr 2011 18:35:42 -0400
Date: Fri, 01 Apr 2011 18:35:41 -0400
From: John C Klensin <john-ietf@jck.com>
To: "John R. Levine" <johnl@iecc.com>, ietf@ietf.org
Subject: Re: Buckets of spam coming through IETF lists
Message-ID: <0B2FA5315C21D0EFAD8F0BD3@PST.JCK.COM>
In-Reply-To: <alpine.BSF.2.00.1104011624500.30110@joyce.lan>
References: <alpine.BSF.2.00.1104011624500.30110@joyce.lan>
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.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 22:34:03 -0000

--On Friday, April 01, 2011 16:28 -0400 "John R. Levine"
<johnl@iecc.com> wrote:

> Some clever spambot seems to have scraped a bunch of addresses
> out of the archives and is sending spam with multiple
> addresses on the From: line through IETF and IRTF mailing
> lists.  Surely I'm not the only one who's seeing it.

Wouldn't that be ironic.  :-(

> Given the amount of legitimate mail with multiple From:
> addresses (none, in practice) a quick shim in front of Mailman
> should deal with it until someone can go fix the underlying
> code.

Yeah, although I find it really sad when the IETF concludes that
it needs to be non-conformant to its own standards.

    john


From evnikita2@gmail.com  Fri Apr  1 20:51:55 2011
Return-Path: <evnikita2@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3768028C104 for <ietf@core3.amsl.com>; Fri,  1 Apr 2011 20:51:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.489
X-Spam-Level: 
X-Spam-Status: No, score=-3.489 tagged_above=-999 required=5 tests=[AWL=0.110,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U2jh8lcHNnUJ for <ietf@core3.amsl.com>; Fri,  1 Apr 2011 20:51:54 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id AAB2928C0E3 for <ietf@ietf.org>; Fri,  1 Apr 2011 20:51:53 -0700 (PDT)
Received: by fxm15 with SMTP id 15so3393664fxm.31 for <ietf@ietf.org>; Fri, 01 Apr 2011 20:53:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=9dZ6UraTprQceC0s4Akkr1unbaKCvP94KlLYciyGu+Q=; b=PAeFzz6yUQ5zqGT6/PZJtJsxMrglLIUJmXlVh2A83Wap73qyqrPrduFq/X66Bg9Rxi MnFMeyY6Ko0C1p6GudyP8aySM5oHnpU6OQSgLhNF62GG8qtTx8o8xYHYxiInwbUXWiCH QBevj1Kb4lOXUsrfaQqjbE392wFdRPkssnaZ0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=SmcVmL3zKKZA3PFuMfou0gDzXk4+uIWWx7vwfCh6mi6DuYv9dElNn5P02DkA1MPQDJ anqTuSdmV7juZk+BNwsQz2tLlMB3/EqI3gY30si1vINQJeLAWyOmzfCk8PBIIglzYmOO TUK0QR+eoPnGXuY79TqqHZUFSmUKGCF6T1Gy8=
Received: by 10.223.100.86 with SMTP id x22mr392393fan.108.1301716413843; Fri, 01 Apr 2011 20:53:33 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.134]) by mx.google.com with ESMTPS id k5sm970953faa.15.2011.04.01.20.53.31 (version=SSLv3 cipher=OTHER); Fri, 01 Apr 2011 20:53:32 -0700 (PDT)
Message-ID: <4D969DE1.5070001@gmail.com>
Date: Sat, 02 Apr 2011 06:54:09 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Buckets of spam coming through IETF lists
References: <alpine.BSF.2.00.1104011624500.30110@joyce.lan>
In-Reply-To: <alpine.BSF.2.00.1104011624500.30110@joyce.lan>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 03:51:55 -0000

01.04.2011 23:28, John R. Levine wrote:
> Some clever spambot seems to have scraped a bunch of addresses out of 
> the archives and is sending spam with multiple addresses on the From: 
> line through IETF and IRTF mailing lists.  Surely I'm not the only one 
> who's seeing it.
>
> Given the amount of legitimate mail with multiple From: addresses 
> (none, in practice) a quick shim in front of Mailman should deal with 
> it until someone can go fix the underlying code.
>
> Regards,
> John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for 
> Dummies",
> Please consider the environment before reading this e-mail. http://jl.ly
>
> ---------- Forwarded message ----------
> Date: Thu, 31 Mar 2011 14:47:22 -0700 (PDT)
> From: gil@ISI.EDU, jtb@ISI.EDU, cakers@ISI.EDU, irsg@ISI.EDU, 
> coreyc@ISI.EDU,
>     jeanine@ISI.EDU, galstyan@ISI.EDU, rahul@ISI.EDU, end2end-tf@ISI.EDU,
>     ns-users@ISI.EDU, ns-commits-owner@ISI.EDU, touch@ISI.EDU, 
> kyamada@ISI.EDU,
>     newuser@ISI.EDU, probing@ISI.EDU, csd@ISI.EDU, 
> management-request@ISI.EDU,
>     hannes@ISI.EDU, rbates@ISI.EDU
> To: gil@ISI.EDU, jtb@ISI.EDU, cakers@ISI.EDU, irsg@ISI.EDU, 
> coreyc@ISI.EDU,
>     jeanine@ISI.EDU, galstyan@ISI.EDU, rahul@ISI.EDU, end2end-tf@ISI.EDU,
>     ns-users@ISI.EDU, ns-commits-owner@ISI.EDU, touch@ISI.EDU, 
> kyamada@ISI.EDU,
>     newuser@ISI.EDU, probing@ISI.EDU, csd@ISI.EDU, 
> management-request@ISI.EDU,
>     hannes@ISI.EDU, rbates@ISI.EDU
Such messages are not the only problem.  RFC-i list receives messages 
"from" internal Mailman addresses (*-bounces@... and *-request@...), 
that is impossible.  See, eg. this one:

> Message: 6
> Date: Fri,  1 Apr 2011 06:25:12 -0700 (PDT)
> From:<rfc-dist-bounces@rfc-editor.org>,<rfc-dist@rfc-editor.org>,
> 	<rfc-interest-owner@rfc-editor.org>,<rfc-editor@rfc-editor.org>,
> 	<rfc-interest@rfc-editor.org>,<rfc-ed@rfc-editor.org>,
> 	<rfc-info@rfc-editor.org>,<rfc-interest-request@rfc-editor.org>
> To:<rfc-dist-bounces@rfc-editor.org>,<rfc-dist@rfc-editor.org>,
> 	<rfc-interest-owner@rfc-editor.org>,<rfc-editor@rfc-editor.org>,
> 	<rfc-interest@rfc-editor.org>,<rfc-ed@rfc-editor.org>,
> 	<rfc-info@rfc-editor.org>,<rfc-interest-request@rfc-editor.org>
> Subject: [rfc-i] Last call for the money makers
Even provided this is the Fool Day's joke, those who dared to send 
surely has not very healthy sense of humor.

--Mykyta
> Subject: [IRSG] An offer you can't refuse
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>


From fred@cisco.com  Fri Apr  1 21:07:14 2011
Return-Path: <fred@cisco.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3615628C104 for <ietf@core3.amsl.com>; Fri,  1 Apr 2011 21:07:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.53
X-Spam-Level: 
X-Spam-Status: No, score=-110.53 tagged_above=-999 required=5 tests=[AWL=0.069, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gfnG70xWj-nP for <ietf@core3.amsl.com>; Fri,  1 Apr 2011 21:07:12 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 5874D28C0F7 for <ietf@ietf.org>; Fri,  1 Apr 2011 21:07:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=1785; q=dns/txt; s=iport; t=1301717333; x=1302926933; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to:content-transfer-encoding; bh=X8hS5uQGBdJ4+cXHm4RmD2pNVet13kVcW+nFWn98pE4=; b=CHi0VmBsmW5bWCcPM7gweqlT3HKkF4Cq+cUszeMzKOv/GqgsimpdvmbT p3uUFA/N3JgYo5AkueRE3dcKFMQrZ87NgxapqpjvdIV0+mI0jJKOfLcIO rf02CD5oJR7hMwZS58bBKYnvTFnB5ZDAy6xcF3dYVzz+EfWZUkauOqdIA U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgQEABiglk2Q/khLgWdsb2JhbAClYhQBARYmJYh5m3CcBYVrBI0hg1s
X-IronPort-AV: E=Sophos;i="4.63,286,1299456000"; d="scan'208";a="81905228"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-1.cisco.com with ESMTP; 02 Apr 2011 04:08:52 +0000
Received: from Freds-Computer.local (dhcp-10-61-105-161.cisco.com [10.61.105.161]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p3248l5J013899; Sat, 2 Apr 2011 04:08:52 GMT
Received: from [127.0.0.1] by Freds-Computer.local (PGP Universal service); Sat, 02 Apr 2011 06:08:52 +0200
X-PGP-Universal: processed; by Freds-Computer.local on Sat, 02 Apr 2011 06:08:52 +0200
Subject: Re: Buckets of spam coming through IETF lists
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <alpine.BSF.2.00.1104011624500.30110@joyce.lan>
Date: Sat, 2 Apr 2011 06:08:37 +0200
Message-Id: <E215C7B5-8CAB-400D-80DA-21DF7B6D138B@cisco.com>
References: <alpine.BSF.2.00.1104011624500.30110@joyce.lan>
To: "John R. Levine" <johnl@iecc.com>
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 04:07:14 -0000

On Apr 1, 2011, at 10:28 PM, John R. Levine wrote:

> Some clever spambot seems to have scraped a bunch of addresses out of =
the archives and is sending spam with multiple addresses on the From: =
line through IETF and IRTF mailing lists.  Surely I'm not the only one =
who's seeing it.

DKIM is directly designed to address this... What do we need to do to =
put it in play?

> Given the amount of legitimate mail with multiple From: addresses =
(none, in practice) a quick shim in front of Mailman should deal with it =
until someone can go fix the underlying code.
>=20
> Regards,
> John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for =
Dummies",
> Please consider the environment before reading this e-mail. =
http://jl.ly
>=20
> ---------- Forwarded message ----------
> Date: Thu, 31 Mar 2011 14:47:22 -0700 (PDT)
> From: gil@ISI.EDU, jtb@ISI.EDU, cakers@ISI.EDU, irsg@ISI.EDU, =
coreyc@ISI.EDU,
>    jeanine@ISI.EDU, galstyan@ISI.EDU, rahul@ISI.EDU, =
end2end-tf@ISI.EDU,
>    ns-users@ISI.EDU, ns-commits-owner@ISI.EDU, touch@ISI.EDU, =
kyamada@ISI.EDU,
>    newuser@ISI.EDU, probing@ISI.EDU, csd@ISI.EDU, =
management-request@ISI.EDU,
>    hannes@ISI.EDU, rbates@ISI.EDU
> To: gil@ISI.EDU, jtb@ISI.EDU, cakers@ISI.EDU, irsg@ISI.EDU, =
coreyc@ISI.EDU,
>    jeanine@ISI.EDU, galstyan@ISI.EDU, rahul@ISI.EDU, =
end2end-tf@ISI.EDU,
>    ns-users@ISI.EDU, ns-commits-owner@ISI.EDU, touch@ISI.EDU, =
kyamada@ISI.EDU,
>    newuser@ISI.EDU, probing@ISI.EDU, csd@ISI.EDU, =
management-request@ISI.EDU,
>    hannes@ISI.EDU, rbates@ISI.EDU
> Subject: [IRSG] An offer you can't refuse
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From bernard_aboba@hotmail.com  Fri Apr  1 21:30:56 2011
Return-Path: <bernard_aboba@hotmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5819328C11F for <ietf@core3.amsl.com>; Fri,  1 Apr 2011 21:30:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.51
X-Spam-Level: 
X-Spam-Status: No, score=-102.51 tagged_above=-999 required=5 tests=[AWL=0.088, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id etuXZPD8E4h0 for <ietf@core3.amsl.com>; Fri,  1 Apr 2011 21:30:55 -0700 (PDT)
Received: from blu0-omc2-s34.blu0.hotmail.com (blu0-omc2-s34.blu0.hotmail.com [65.55.111.109]) by core3.amsl.com (Postfix) with ESMTP id 1BA5B28C104 for <ietf@ietf.org>; Fri,  1 Apr 2011 21:30:55 -0700 (PDT)
Received: from BLU152-W38 ([65.55.111.72]) by blu0-omc2-s34.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 1 Apr 2011 21:32:36 -0700
Message-ID: <BLU152-w38DFEC24F71F05DD3808B093A10@phx.gbl>
Content-Type: multipart/alternative; boundary="_04d60d28-979a-48b1-8604-f077d101ce1f_"
X-Originating-IP: [62.168.35.7]
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: <ietf@ietf.org>
Subject: Appointment of IETF Liaison to ITU-T
Date: Fri, 1 Apr 2011 21:32:35 -0700
Importance: Normal
MIME-Version: 1.0
X-OriginalArrivalTime: 02 Apr 2011 04:32:36.0548 (UTC) FILETIME=[FE0F2840:01CBF0EE]
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 04:30:56 -0000

--_04d60d28-979a-48b1-8604-f077d101ce1f_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


The IAB has appointed Elliot Lear to replace Patrik Falstrom as the liaison=
 from IETF to ITU-T.=20

Please welcome Elliot as the new liaison. =20

Bernard Aboba
IAB Chair
 		 	   		  =

--_04d60d28-979a-48b1-8604-f077d101ce1f_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Tahoma
}
--></style>
</head>
<body class=3D'hmmessage'>
The IAB has appointed Elliot Lear to replace Patrik Falstrom as the liaison=
 from IETF to ITU-T. <br><br>Please welcome Elliot as the new liaison.&nbsp=
=3B <br><br>Bernard Aboba<br>IAB Chair<br> 		 	   		  </body>
</html>=

--_04d60d28-979a-48b1-8604-f077d101ce1f_--

From johnl@iecc.com  Fri Apr  1 21:34:44 2011
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 01EBE3A6A20 for <ietf@core3.amsl.com>; Fri,  1 Apr 2011 21:34:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.457
X-Spam-Level: 
X-Spam-Status: No, score=-110.457 tagged_above=-999 required=5 tests=[AWL=0.742, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kl+oLyUg2wTi for <ietf@core3.amsl.com>; Fri,  1 Apr 2011 21:34:42 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by core3.amsl.com (Postfix) with ESMTP id 9CED73A69E9 for <ietf@ietf.org>; Fri,  1 Apr 2011 21:34:41 -0700 (PDT)
Received: (qmail 69366 invoked from network); 2 Apr 2011 04:36:21 -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=10ef5.4d96a7c5.k1104; i=johnl@submit.iecc.com; bh=CCaVYjcv6z1J5sh+szrNVdre2I9JUtWNxRhecq2eDfY=; b=qjOSA6DmB0Y2u8DfO6QV+5pmWfOIR7VhsENUQ2UnbwrZVfMR9Hk6pva54UF12jL/b60I0yXiNXQien72z7W3fE/xnOCS84GZQSTZfSAd5moJC5xBfS03L8QX+RfO+u0idOK/6CP6vJEjuptsCAWOzVf18IzGkiy+5TKo9KLv8Uw=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd johnl@64.57.183.62) with (DHE-RSA-AES256-SHA encrypted) SMTP; 2 Apr 2011 04:35:59 -0000
Date: 2 Apr 2011 00:36:21 -0400
Message-ID: <alpine.BSF.2.00.1104020010400.249@joyce.lan>
From: "John R. Levine" <johnl@iecc.com>
To: "Fred Baker" <fred@cisco.com>
Subject: Re: Buckets of spam coming through IETF lists
In-Reply-To: <E215C7B5-8CAB-400D-80DA-21DF7B6D138B@cisco.com>
References: <alpine.BSF.2.00.1104011624500.30110@joyce.lan> <E215C7B5-8CAB-400D-80DA-21DF7B6D138B@cisco.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
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.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 04:34:44 -0000

>> Some clever spambot seems to have scraped a bunch of addresses out of the archives and is sending spam with multiple addresses on the From: line through IETF and IRTF mailing lists.  Surely I'm not the only one who's seeing it.
>
> DKIM is directly designed to address this... What do we need to do to put it in play?

Probably more than you want to try to do in a hurry.

It seems to me there are two separate problems.  One is that a bad guy is 
sending spam with fake IETF and IRTF return addresses, something that DKIM 
can mitigate.  The other is that the mailing list software is getting 
confused by multiple From line addresses, which is probably buggy code 
that wasn't written to handle them.

For the former, first you adjust the IETF's mail servers to put DKIM 
signatures on all the outgoing mail.  Once that works, you adjust the 
incoming spam filters so that mail that purports to be from the IETF or 
IRTF and doesn't have a signature is treated as spam.  (Spamassassin can 
easily be tuned to do that.)  You don't want to do that in a hurry, 
because there always turn out to be considerably more outgoing mail paths 
than you thought, and finding and securing them all is tedious.

It's not immediately apparent to me why Mailman is letting that mail 
through, since the addresses on the From: line aren't all subscribed to 
the various lists.  As a band-aid, it's straightforward to add a Mailman 
spam filter like

   from: .*<.*>.*,

which will catch any multiple from lines and either hold or discard them.

Regards,
John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. http://jl.ly

From olaf@NLnetLabs.nl  Sat Apr  2 01:27:26 2011
Return-Path: <olaf@NLnetLabs.nl>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 691463A6A5B for <ietf@core3.amsl.com>; Sat,  2 Apr 2011 01:27:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.592
X-Spam-Level: 
X-Spam-Status: No, score=-102.592 tagged_above=-999 required=5 tests=[AWL=0.008, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FO8HzNGdP7HS for <ietf@core3.amsl.com>; Sat,  2 Apr 2011 01:27:25 -0700 (PDT)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by core3.amsl.com (Postfix) with ESMTP id 45E743A6A59 for <ietf@ietf.org>; Sat,  2 Apr 2011 01:27:23 -0700 (PDT)
Received: from dhcp-2712.meeting.ietf.org (dhcp-2712.meeting.ietf.org [130.129.39.18]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.4/8.14.4) with ESMTP id p328SxXm017016 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Sat, 2 Apr 2011 10:29:00 +0200 (CEST) (envelope-from olaf@NLnetLabs.nl)
From: Olaf Kolkman <olaf@NLnetLabs.nl>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Apple-Mail-12--844296276"
Subject: Re: IAOC: delegating ex-officio responsibility
Date: Sat, 2 Apr 2011 10:28:49 +0200
In-Reply-To: <9C81C0F6-3ABE-4479-8C5E-C20C486D052A@gmail.com>
To: IETF Discussion <ietf@ietf.org>
References: <2BE582FA-2682-4232-9D83-23A03F01A0DB@NLnetLabs.nl> <6.2.5.6.2.20110330073936.0e1899d0@resistor.net> <E2E41FDE-3818-4513-9933-CB1E0326B43E@nlnetlabs.nl> <6.2.5.6.2.20110330113947.0c948bc0@resistor.net> <4D942843.4060804@gmail.com> <6.2.5.6.2.20110331120351.09488990@resistor.net> <4D955661.8050502@gmail.com> <9C81C0F6-3ABE-4479-8C5E-C20C486D052A@gmail.com>
Message-Id: <82A347CC-BB19-4A73-8E8A-924FBAA92A5F@NLnetLabs.nl>
Content-Transfer-Encoding: 7bit
X-Pgp-Agent: GPGMail 1.3.3
X-Mailer: Apple Mail (2.1084)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (open.nlnetlabs.nl [213.154.224.1]); Sat, 02 Apr 2011 10:29:00 +0200 (CEST)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 08:27:26 -0000

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--Apple-Mail-12--844296276
Content-Type: multipart/signed; boundary=Apple-Mail-11--844296279; protocol="application/pkcs7-signature"; micalg=sha1


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


[as editor:]

It seems that the high order bit of this discussion circles around the =
question on whether it a requirement for the IETF Chair to have a voting =
position in order to effectively perform oversight. Once we figured out =
where we want to go with that we can think about delegation by the chair =
vs appointment by the bodies and the implementation details with respect =
to the trust.

[as olaf:]

I agree that the IETF chair needs to have a good oversight about what =
goes on in the IETF, to a lesser extend it is good that the IAB has that =
oversight too (specifically with respect to its chartered =
responsibilities) but I wonder if a voting membership is the appropriate =
instrument.

I believe effective oversight depends on having the appropriate high =
level information and having the opportunity to timely inject =
information that is needed to steer an outcome. An alternative method =
for sharing and injecting is having regular meetings between the I* =
chairs and the ISOC President/CEO. I believe that such meetings are much =
more effective for the parties involved than being exposed to all =
details.

This only an illustration of an instrument, there may be other =
instruments for oversight as well. But I do not think the ex-officio =
membership is the only method.


--Olaf



________________________________________________________=20

Olaf M. Kolkman                        NLnet Labs
                                       Science Park 140,=20
http://www.nlnetlabs.nl/               1098 XG Amsterdam


--Apple-Mail-11--844296279
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIFMTCCBS0w
ggMVoAMCAQICAwbqdTANBgkqhkiG9w0BAQUFADB5MRAwDgYDVQQKEwdSb290IENBMR4wHAYDVQQL
ExVodHRwOi8vd3d3LmNhY2VydC5vcmcxIjAgBgNVBAMTGUNBIENlcnQgU2lnbmluZyBBdXRob3Jp
dHkxITAfBgkqhkiG9w0BCQEWEnN1cHBvcnRAY2FjZXJ0Lm9yZzAeFw0wOTA1MjUwODQ4MTJaFw0x
MTA1MjUwODQ4MTJaMDkxFTATBgNVBAMTDE9sYWYgS29sa21hbjEgMB4GCSqGSIb3DQEJARYRb2xh
ZkBubG5ldGxhYnMubmwwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCtxtZNngmuLgcf
rto+Uax1WhonECqb5W8US2Z+ZPw/ASKsjKEF8Wa3Nnispys6Gj9Sl7C1X0/2pH//qauLpBqA+lHW
L9mgdGW1T9KU1Fb8Odqw0PBnIIhbLNQzecZL+BchEetcrubplQWzDOpROCJ00IwXksusBiKqhew4
u7X2QoraW+z32Knj5ogajIhdkAeBHUy1pwXsk/mDnV8cIEdz1MhaZWDSn7kJUQtRMVCpFBjVoiXh
ToXMJfiMvn0CKaeFxFm72dcdzvFsw906Ndafd2MOfdP7QSsTVP6sG9am790AOgkzxT5CM77IDPbD
zxZlQ8jTdhcp/WtUrFWIU4QBAgMBAAGjgf0wgfowDAYDVR0TAQH/BAIwADBWBglghkgBhvhCAQ0E
SRZHVG8gZ2V0IHlvdXIgb3duIGNlcnRpZmljYXRlIGZvciBGUkVFIGhlYWQgb3ZlciB0byBodHRw
Oi8vd3d3LkNBY2VydC5vcmcwQAYDVR0lBDkwNwYIKwYBBQUHAwQGCCsGAQUFBwMCBgorBgEEAYI3
CgMEBgorBgEEAYI3CgMDBglghkgBhvhCBAEwMgYIKwYBBQUHAQEEJjAkMCIGCCsGAQUFBzABhhZo
dHRwOi8vb2NzcC5jYWNlcnQub3JnMBwGA1UdEQQVMBOBEW9sYWZAbmxuZXRsYWJzLm5sMA0GCSqG
SIb3DQEBBQUAA4ICAQCLpawAoUQAxivf6blyMswVokRmDl2JGEbtmEu8j0h1BVOlGh6hlI8WaeWy
3x2jJ9uun3VK6oYnHy45ez+dUDjBLjOZdAgwFg225lm1OPdmisghDDVwCIiEogHPqmJtvKYMFoPF
3iFUambJDoQF8DeVeg8ctDvsxsaVGjA8OrMpo0K4I11vnNbCLv7mWCjnaZWt/6Y6TD8ErHQl5dmI
rpsHmEZx1/nsocdPkZGRA4QVf1omYHUNs79DtxpYdGKHoorpBNzlzIIjpceiqeOeykoDeYLTZX2G
c7Mh4Gdj2MHFqZucxV1cHibb8XKv8ebaGltMV5SrciqRn8yFXmiyTvmId6myNXLiOx+VJiGbLSS3
TltM/kf7UejXeEHulEKufU6Ya6EfH7W2/spTayYCauyLljOjE2Ey5A4oIoJV9eY64OCDuLF2nmGR
jOh3JB9nGkZIPhmTUwGZnMELLhzKz+eOZoulM4tXH6KEubed1shQEq1dkJ+tFtRS3Lm+vLCKWvVo
1iZScqPaQf9riPApAVrL+3Wat0p/jtCk5gLBF02uTiWvT2t4ZfSHMEBXR7CvVm58etRQuyZSMHyz
UQC4wkDvCeVawNRCZjq6wWdvx5hmr2JeDSkkRtSZ/Fa1WXf26b3BZugI75p5JXafbWdOTRpNc8M5
YMk7tx29ZG3u0qODgDGCAzMwggMvAgEBMIGAMHkxEDAOBgNVBAoTB1Jvb3QgQ0ExHjAcBgNVBAsT
FWh0dHA6Ly93d3cuY2FjZXJ0Lm9yZzEiMCAGA1UEAxMZQ0EgQ2VydCBTaWduaW5nIEF1dGhvcml0
eTEhMB8GCSqGSIb3DQEJARYSc3VwcG9ydEBjYWNlcnQub3JnAgMG6nUwCQYFKw4DAhoFAKCCAYcw
GAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTEwNDAyMDgyODUwWjAj
BgkqhkiG9w0BCQQxFgQUxHgueZlDr4AQJVjWr0I6vaFNLh8wgZEGCSsGAQQBgjcQBDGBgzCBgDB5
MRAwDgYDVQQKEwdSb290IENBMR4wHAYDVQQLExVodHRwOi8vd3d3LmNhY2VydC5vcmcxIjAgBgNV
BAMTGUNBIENlcnQgU2lnbmluZyBBdXRob3JpdHkxITAfBgkqhkiG9w0BCQEWEnN1cHBvcnRAY2Fj
ZXJ0Lm9yZwIDBup1MIGTBgsqhkiG9w0BCRACCzGBg6CBgDB5MRAwDgYDVQQKEwdSb290IENBMR4w
HAYDVQQLExVodHRwOi8vd3d3LmNhY2VydC5vcmcxIjAgBgNVBAMTGUNBIENlcnQgU2lnbmluZyBB
dXRob3JpdHkxITAfBgkqhkiG9w0BCQEWEnN1cHBvcnRAY2FjZXJ0Lm9yZwIDBup1MA0GCSqGSIb3
DQEBAQUABIIBAKZy4y4CvUXwOTUIgHRh9cU4qPZ+YP7QE3HReaA3EjKWeGXhI5j7z8ASvPYLB9a7
ITZMRSVdjy4BdoX4OYLib+HlzM2FH/54e2v052ThsBvpje6/gtX09dH+EOgSA0TR36fMU31Hu8fG
XqI/RpayBT/pFwjza2Ip68pqR7AYk9AQVUUvUkCYntmfuAu0ZEFZonr8oE04HAboxrLTCTudAVkb
Yh7+l/M7i1emZdqbVwctYQGWA4dwqg0SjE0rCgGtho4nAAg94ygX1U4KgGeDbSh1tLC9OPJf8ukF
qFKz1UXxpIAUq5t5223gSF7CbDYsSOhJpQXNslwv83qLi7+OARMAAAAAAAA=

--Apple-Mail-11--844296279--

--Apple-Mail-12--844296276
content-type: application/pgp-signature; x-mac-type=70674453;
	name=PGP.sig
content-description: This is a digitally signed message part
content-disposition: inline; filename=PGP.sig
content-transfer-encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: This message is locally signed.
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAk2W3ksACgkQtN/ca3YJIocSGACfc9RUUANCHz0k8DJSuAatb0em
KzIAoIGzS13S/DraFzsuxmUo/BQ1/M0e
=itBd
-----END PGP SIGNATURE-----

--Apple-Mail-12--844296276--

From turchanyi.geza@gmail.com  Sat Apr  2 02:37:05 2011
Return-Path: <turchanyi.geza@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 45F6B3A6A6B for <ietf@core3.amsl.com>; Sat,  2 Apr 2011 02:37:05 -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_13=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B0quG4SP6Bwg for <ietf@core3.amsl.com>; Sat,  2 Apr 2011 02:37:03 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 908C03A65A5 for <Ietf@ietf.org>; Sat,  2 Apr 2011 02:37:02 -0700 (PDT)
Received: by wwa36 with SMTP id 36so3445052wwa.13 for <Ietf@ietf.org>; Sat, 02 Apr 2011 02:38:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=XL8hkRVgmgm+wAWxNMsxx0ONq2XkAEkKSPJ0ee9Mc2s=; b=EU2qm8FPEBXFWJXqdBWveyNNUGDYQNbNM5BYZpjdUTvs4Tk8lO7lGoeBKCFXZ0KjGZ X7/gZWnws3M6cc99fUn682dxoFdSeuwblnL4vEkKmrnifLrj6ARPqFXai83eHIp1YE+H IZv/49cDKRuyXBFevGIW+08fehe5Ysy1AboTM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=ALTodtez/R9I8pwOlDVqqxenOKtPbiVWEJP0ux0TijM9lj/f9L5FEfhoeLncBWExnS X+dQHsFSeWCD7cdkJj7fOgKRe8AUKYHNEcAjCavm/5SITPE8f3T2pENHSihKHUBuTmT8 yVmyfxLbTS+oURCftSdo6y6rndl6nNakzrNUw=
MIME-Version: 1.0
Received: by 10.227.198.5 with SMTP id em5mr5168500wbb.163.1301737122132; Sat, 02 Apr 2011 02:38:42 -0700 (PDT)
Received: by 10.227.157.196 with HTTP; Sat, 2 Apr 2011 02:38:42 -0700 (PDT)
In-Reply-To: <AANLkTimh-oRwkyM5FzZGbsrO45bphgV=2YATFJQ-qD3q@mail.gmail.com>
References: <AANLkTimh-oRwkyM5FzZGbsrO45bphgV=2YATFJQ-qD3q@mail.gmail.com>
Date: Sat, 2 Apr 2011 11:38:42 +0200
Message-ID: <BANLkTi=Lz_GHUWdAXc55yW_VMr8W1kSuEQ@mail.gmail.com>
Subject: Re: Alternative To IPv6
From: Turchanyi Geza <turchanyi.geza@gmail.com>
To: "J. C. Jones" <jaibuduvin@gmail.com>
Content-Type: multipart/alternative; boundary=0015174bf26ec175cd049fec4a96
Cc: Ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 09:37:05 -0000

--0015174bf26ec175cd049fec4a96
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

.... and of course you will have a magic transition scenario as well, and
all the content providers will adapt within 3 months, without any problems
of load balancing what we have today....

IF NOT, your announcement just will provoque more delay in transition to
IPv6, the only viable and urgent solution ahead of us.

Regards,

G=E9za

On Fri, Apr 1, 2011 at 10:43 PM, J. C. Jones <jaibuduvin@gmail.com> wrote:

> Hi All,
>
> Those associated with the IETF and those with interest in computer
> networking might be interested to know that a new, clean-slate network
> protocol stack, an alternative to the IPv4 and IPv6, is due out in 2012.
> This new protocol stack will provide the following features:
>
>
>    1. A generalized solution to *naming*, *numbering*, and *addressing *p=
roblems,
>    where domain names and IP addresses have been given a sound, theoretic=
al
>    basis, with particular emphasis on rethinking the nature of domain nam=
es
>    with respect to IP addresses. Well-known port numbers would become
>    unnecessary for many applications.
>    2. A generalized solution to the *mobility *problem, where networks of
>    networks may be mobile, with continuously optimal routing from source =
to
>    target and ultra-fast handover over multiple wireless technologies exi=
sting
>    within the same node that allows PDA's to easily be used as cell phone=
s
>    while making and breaking of Wi-Fi links.
>    3. A generalized solution to the *multicast *problem, where a PDA migh=
t
>    serve as the root of a *1,000,000,000*-node multicast tree, and where
>    an application sourcing the multicast can be written by a programmer i=
n one
>    afternoon whose possesses a near-minimum understanding of computer
>    networking.
>    4. A generalized solution to the *security *problem, where each featur=
e
>    commonly provided by an underlying security framework [hiding, signing=
,
>    etc.] might be independently enabled or disabled without affecting the
>    operation of cooperative features.
>    5. A generalized solution to the *access control* problem, where
>    specifying access control parameters makes sense to technical neophyte=
s,
>    where username/passwords are essentially non-existent, and where it is
>    plainly evident from the model that it is regular and persistent.
>    6. A gratuitous, parasitic framework that, if it were so chosen, would
>    allow for the *elimination of the majority of email spam* and similar
>    nuisances on the Internet.
>    7. A strictly* 99.8% portable* reference implementation for most
>    multi-threaded OS's, written in C++.
>    8. A network application *library *that presents *persistent primitive=
s
>    of computer networking* [C++ classes].
>    9. *International support* for almost all of the world's languages, no=
t
>    only for domain names, but for all textual processing under the purvie=
w of
>    the protocol stack. Specifically, almost equal weight will be given fo=
r
>    non-English languages as for English.
>    10. A total executable size of l*ess than 1MB* [without a GUI] for a *
>    full-featured* stack destined for small-footprint devices.
>    11. *Initial compatibility with IPv4* routing, where new, disruptive
>    applications may be created over the new protocol stack without requir=
ing
>    changes to existing IPv4 routing. A full-break from IPv4 would require=
 no
>    human intervention [renumbering] at the point of change-over, and afte=
r
>    change-over, said disruptive applications would continue to function,
>    unaware that change-over has occurred.
>    12. *Simplicity*. The new stack should be understandable in its
>    entirely by a single software engineer after 3 months of study.
>
> I will send out notices as the release date in 2012 approaches.
>
> Warm Regards,
> -JC
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>
>

--0015174bf26ec175cd049fec4a96
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

.... and of course you will have a magic transition scenario as well,=20
and all the content providers will adapt within 3 months, without any=20
problems of load balancing what we have today....<br>
<br>
IF NOT, your announcement just will provoque more delay in transition to IP=
v6, the only viable and urgent solution ahead of us.<br>
<br>
Regards,<br>
<br>
G=E9za<br><br><div class=3D"gmail_quote">On Fri, Apr 1, 2011 at 10:43 PM, J=
. C. Jones <span dir=3D"ltr">&lt;<a href=3D"mailto:jaibuduvin@gmail.com">ja=
ibuduvin@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quot=
e" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204,=
 204); padding-left: 1ex;">
Hi All,<div><br></div><div>Those associated with the IETF and those with in=
terest in computer networking might be interested to know that a new, clean=
-slate network protocol stack, an alternative to the IPv4 and IPv6, is due =
out in 2012. This new protocol stack will provide the following features:</=
div>

<div><br></div><div><ol><li>A generalized solution to <b>naming</b>, <b>num=
bering</b>, and <b>addressing </b>problems, where domain names and IP addre=
sses have been given a sound, theoretical basis, with particular emphasis o=
n rethinking the nature of domain names with respect to IP addresses. Well-=
known port numbers would become unnecessary for many applications.</li>

<li>A generalized solution to the <b>mobility </b>problem, where networks o=
f networks may be mobile, with continuously optimal routing from source to =
target and ultra-fast handover over multiple wireless technologies existing=
 within the same node that allows PDA&#39;s to easily be used as cell phone=
s while making and breaking of Wi-Fi links.</li>

<li>A generalized solution to the <b>multicast </b>problem, where a PDA mig=
ht serve as the root of a <b>1,000,000,000</b>-node multicast tree, and whe=
re an application sourcing the multicast can be written by a programmer in =
one afternoon whose possesses a near-minimum understanding of computer netw=
orking.</li>

<li>A generalized solution to the <b>security </b>problem, where each featu=
re commonly provided by an underlying security framework [hiding, signing, =
etc.] might be independently enabled or disabled without affecting the oper=
ation of cooperative features.</li>

<li>A generalized solution to the <b>access control</b> problem, where spec=
ifying access control parameters makes sense to technical neophytes, where =
username/passwords are essentially non-existent, and where it is plainly ev=
ident from the model that it is regular and persistent.</li>

<li>A gratuitous, parasitic framework that, if it were so chosen, would all=
ow for the <b>elimination of the majority of email spam</b> and similar nui=
sances on the Internet.</li><li>A strictly<b> 99.8%=A0portable</b>=A0refere=
nce implementation for=A0most multi-threaded OS&#39;s, written in C++.</li>

<li>A network application=A0<b>library=A0</b>that presents=A0<b>persistent =
primitives of computer networking</b>=A0[C++ classes].</li><li><b>Internati=
onal support</b> for almost all of the world&#39;s languages, not only for =
domain names, but for all textual processing under the purview of the proto=
col stack. Specifically, almost equal weight will be given for non-English =
languages as for English.</li>

<li>A total executable size of l<b>ess than 1MB</b>=A0[without a GUI] for a=
 <b>full-featured</b> stack destined for small-footprint devices.</li><li><=
b>Initial compatibility with IPv4</b>=A0routing, where new, disruptive appl=
ications may be created over the new protocol stack without requiring chang=
es to existing IPv4 routing. A full-break from IPv4 would require no human =
intervention [renumbering] at the point of change-over, and after change-ov=
er, said disruptive applications would continue to function, unaware that c=
hange-over has occurred.</li>

<li><b>Simplicity</b>. The new stack should be understandable in its entire=
ly by a single software engineer after 3 months of study.</li></ol><div>I w=
ill send out notices as the release date in 2012 approaches.</div><div>

<br></div><div>Warm Regards,</div><div>-JC</div></div>
<br>_______________________________________________<br>
Ietf mailing list<br>
<a href=3D"mailto:Ietf@ietf.org">Ietf@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/ietf" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/ietf</a><br>
<br></blockquote></div><br>

--0015174bf26ec175cd049fec4a96--

From bob.hinden@gmail.com  Sat Apr  2 07:55:17 2011
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EBA373A6830 for <ietf@core3.amsl.com>; Sat,  2 Apr 2011 07:55:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.009
X-Spam-Level: 
X-Spam-Status: No, score=-103.009 tagged_above=-999 required=5 tests=[AWL=0.590, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1mWEcoiF7Dcq for <ietf@core3.amsl.com>; Sat,  2 Apr 2011 07:55:16 -0700 (PDT)
Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by core3.amsl.com (Postfix) with ESMTP id C6E703A63D2 for <ietf@ietf.org>; Sat,  2 Apr 2011 07:55:16 -0700 (PDT)
Received: by pwi5 with SMTP id 5so1142631pwi.31 for <ietf@ietf.org>; Sat, 02 Apr 2011 07:56:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=ExFphSHkq3ZDaaQUxamlX/jSuiX5jPYssxKAgnopB6Q=; b=wCJaR9eW4JpG5rTqw731uGUzhL4yB0Y0IzkYTcQKg4QCCUpVHK4iDPEpcLPs0funQj OBj6frbd+ULfVpqJuRdmAMLRR4XEYtL1XM9S2LMtM1vTmnRRCq1UBXLhTRY8Z2HucCMW 5b17TOJ+gvC//qSBIHwLxmzn6uG7MrAgG4G2o=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=Xw+bl7Il0FvnaxRlRgq61/UtFYbbC+pZCc474FiH9+A/AaavxEfdta08xtR2gQZhtB 5Z5cVri8qA+leZLiCXhNbVUog9CikC7mOrKgHkmr7gTheY8RsZqTIvbKhy8LRglzzrjS o2ykJlpsaQ/vo1jgxKw4Cfo3h1SgnDGWSBnF4=
Received: by 10.142.250.2 with SMTP id x2mr4104004wfh.381.1301756217904; Sat, 02 Apr 2011 07:56:57 -0700 (PDT)
Received: from dhcp-23bc.meeting.ietf.org (dhcp-23bc.meeting.ietf.org [130.129.35.188]) by mx.google.com with ESMTPS id s39sm4534624wfc.4.2011.04.02.07.56.55 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 02 Apr 2011 07:56:57 -0700 (PDT)
Subject: Re: Buckets of spam coming through IETF lists
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <alpine.BSF.2.00.1104011624500.30110@joyce.lan>
Date: Sat, 2 Apr 2011 16:56:53 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <813B6188-ED14-4D65-B537-0F5CFA685B56@gmail.com>
References: <alpine.BSF.2.00.1104011624500.30110@joyce.lan>
To: John R. Levine <johnl@iecc.com>
X-Mailer: Apple Mail (2.1082)
Cc: Bob Hinden <bob.hinden@gmail.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 14:55:18 -0000

John,

If you want to report a SPAM problem with an IETF mailing list, please =
report it to <ietf-action@ietf.org>.  It will get prompt response. =20

=46rom the email you forwarded, it looks like a problem with lists =
hosted at ISI.EDU (that is, not at ietf.org). =20

Bob

p.s. Or should I have taken the date you sent this more seriously?



On Apr 1, 2011, at 10:28 PM, John R. Levine wrote:

> Some clever spambot seems to have scraped a bunch of addresses out of =
the archives and is sending spam with multiple addresses on the From: =
line through IETF and IRTF mailing lists.  Surely I'm not the only one =
who's seeing it.
>=20
> Given the amount of legitimate mail with multiple From: addresses =
(none, in practice) a quick shim in front of Mailman should deal with it =
until someone can go fix the underlying code.
>=20
> Regards,
> John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for =
Dummies",
> Please consider the environment before reading this e-mail. =
http://jl.ly
>=20
> ---------- Forwarded message ----------
> Date: Thu, 31 Mar 2011 14:47:22 -0700 (PDT)
> From: gil@ISI.EDU, jtb@ISI.EDU, cakers@ISI.EDU, irsg@ISI.EDU, =
coreyc@ISI.EDU,
>    jeanine@ISI.EDU, galstyan@ISI.EDU, rahul@ISI.EDU, =
end2end-tf@ISI.EDU,
>    ns-users@ISI.EDU, ns-commits-owner@ISI.EDU, touch@ISI.EDU, =
kyamada@ISI.EDU,
>    newuser@ISI.EDU, probing@ISI.EDU, csd@ISI.EDU, =
management-request@ISI.EDU,
>    hannes@ISI.EDU, rbates@ISI.EDU
> To: gil@ISI.EDU, jtb@ISI.EDU, cakers@ISI.EDU, irsg@ISI.EDU, =
coreyc@ISI.EDU,
>    jeanine@ISI.EDU, galstyan@ISI.EDU, rahul@ISI.EDU, =
end2end-tf@ISI.EDU,
>    ns-users@ISI.EDU, ns-commits-owner@ISI.EDU, touch@ISI.EDU, =
kyamada@ISI.EDU,
>    newuser@ISI.EDU, probing@ISI.EDU, csd@ISI.EDU, =
management-request@ISI.EDU,
>    hannes@ISI.EDU, rbates@ISI.EDU
> Subject: [IRSG] An offer you can't refuse
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From jnc@mercury.lcs.mit.edu  Sat Apr  2 08:01:06 2011
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9CA373A6835 for <ietf@core3.amsl.com>; Sat,  2 Apr 2011 08:01:06 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c2+SawP9D1Ei for <ietf@core3.amsl.com>; Sat,  2 Apr 2011 08:01:05 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by core3.amsl.com (Postfix) with ESMTP id C00C63A6834 for <Ietf@ietf.org>; Sat,  2 Apr 2011 08:01:05 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 5FBCB18C13A; Sat,  2 Apr 2011 11:02:46 -0400 (EDT)
To: Ietf@ietf.org
Subject: Re: Alternative To IPv6
Message-Id: <20110402150246.5FBCB18C13A@mercury.lcs.mit.edu>
Date: Sat,  2 Apr 2011 11:02:46 -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.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 15:01:06 -0000

'    > From: Turchanyi Geza <turchanyi.geza@gmail.com>

    > IF NOT, your announcement just will provoque more delay in transition
    > to IPv6

Well, he did send his email on April 1.... :-)

    > the only viable and urgent solution ahead of us.

Hey, it was April 2 when you sent this!

	Noel

From jmamodio@gmail.com  Sat Apr  2 16:00:35 2011
Return-Path: <jmamodio@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F12123A68EF for <ietf@core3.amsl.com>; Sat,  2 Apr 2011 16:00:34 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ux0pC+RFKnF3 for <ietf@core3.amsl.com>; Sat,  2 Apr 2011 16:00:34 -0700 (PDT)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id 15AC63A68E3 for <Ietf@ietf.org>; Sat,  2 Apr 2011 16:00:34 -0700 (PDT)
Received: by iwn39 with SMTP id 39so5352178iwn.31 for <Ietf@ietf.org>; Sat, 02 Apr 2011 16:02:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=tfSTRSC042Ttn1S/N6iu3e0u3NJQ6ZjgZxTsxlxO7ko=; b=gfyt86FH8lI0DfDVbIRFK2cBw9V6OvrYiT6xozC5RtMvRaEHO8hMkG8t4/e0URLSO6 gCBQRaNkTlaHv9klvY0P+fdGcoD3UsLnvRnWb2aT+VulTKr/SnkD2yE06mOlG8FGJdtq MKTMrpPRLD7kV7cN5kEZsZNElUpGBznbapPOU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=h80bTeLW6OGcWivvy1r1vyE9j5B9N+dkjEtWSGtI4gxDpmTMapqtSJ9JarExjeFd7u E4RleKIUVpomuOB9521H8sFmdfNE6JspoXt77PfTqttoVy3U5iHIidNgb7NhznV+mLYv YZPLteiUdwr51bIKNtAq1kC8WwMDh4/eQbN28=
MIME-Version: 1.0
Received: by 10.42.138.4 with SMTP id a4mr1989269icu.258.1301785335379; Sat, 02 Apr 2011 16:02:15 -0700 (PDT)
Received: by 10.231.14.76 with HTTP; Sat, 2 Apr 2011 16:02:15 -0700 (PDT)
In-Reply-To: <AANLkTimh-oRwkyM5FzZGbsrO45bphgV=2YATFJQ-qD3q@mail.gmail.com>
References: <AANLkTimh-oRwkyM5FzZGbsrO45bphgV=2YATFJQ-qD3q@mail.gmail.com>
Date: Sat, 2 Apr 2011 18:02:15 -0500
Message-ID: <BANLkTimwARGve5Vr2imo25=SC02CEkVfhg@mail.gmail.com>
Subject: Re: Alternative To IPv6
From: Jorge Amodio <jmamodio@gmail.com>
To: "J. C. Jones" <jaibuduvin@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 23:00:35 -0000

> I will send out notices as the release date in 2012 approaches.

That's excellent, please send the notice before the Mayan calendar ends. Tnx.

-J

From turchanyi.geza@gmail.com  Sat Apr  2 20:27:06 2011
Return-Path: <turchanyi.geza@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EE8F528C0D6 for <ietf@core3.amsl.com>; Sat,  2 Apr 2011 20:27:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.298
X-Spam-Level: 
X-Spam-Status: No, score=-3.298 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NpIaIrIFFqfk for <ietf@core3.amsl.com>; Sat,  2 Apr 2011 20:27:05 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 9B84C28C0D0 for <Ietf@ietf.org>; Sat,  2 Apr 2011 20:27:05 -0700 (PDT)
Received: by wwa36 with SMTP id 36so3757652wwa.13 for <Ietf@ietf.org>; Sat, 02 Apr 2011 20:28:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=H7db2NmZNEWnZpEF7ky3UO+I7YnYT1N66UiXeRtwSl4=; b=ksOXZZ96Ka9Mq5CLiZh2+WS49iwdP9gR7WeT3OVMlqyQRQnF3Loj0pkfcFesudCaBM gHqVfyb3c/IOOeLuM2Ms2PuCQO2yETeGLqXU4nGWelrI7rds0Lx9KztYMDxxAbya3qG/ Hxhp9SZDeXOBo2hUjmncs6BAUUHGCjrXuxV2o=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=BPJ4E/JgiC4IcTROxmEQtsArKjmvmD1EYT5t4u8RUsjwAFItA8AUioCGeufN7piljM 7QdZoVO+W/+lEyP/f28Wl/Wwuo3YzIqq+RGer2o2U0+QRdUEvuKr+WhaGcj/xAca+yGZ 0IePpWIp58y//K5vD8uz8jshUPnnp+SULXRr8=
MIME-Version: 1.0
Received: by 10.227.12.13 with SMTP id v13mr3180847wbv.134.1301801325082; Sat, 02 Apr 2011 20:28:45 -0700 (PDT)
Received: by 10.227.157.196 with HTTP; Sat, 2 Apr 2011 20:28:45 -0700 (PDT)
In-Reply-To: <BANLkTimwARGve5Vr2imo25=SC02CEkVfhg@mail.gmail.com>
References: <AANLkTimh-oRwkyM5FzZGbsrO45bphgV=2YATFJQ-qD3q@mail.gmail.com> <BANLkTimwARGve5Vr2imo25=SC02CEkVfhg@mail.gmail.com>
Date: Sun, 3 Apr 2011 05:28:45 +0200
Message-ID: <BANLkTingg7Yjp8syHPH3XFxiJZVpc4Qp7Q@mail.gmail.com>
Subject: Re: Alternative To IPv6
From: Turchanyi Geza <turchanyi.geza@gmail.com>
To: "J. C. Jones" <jaibuduvin@gmail.com>
Content-Type: multipart/alternative; boundary=002215974a768cb85d049ffb3d21
Cc: Ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 03:27:07 -0000

--002215974a768cb85d049ffb3d21
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,

Quite a few people reminded me for the date of your message, which was All
Fool Day.

Oh yes, I surely forgot to check this! Then I realised one more thing: I
surely forgot to translate "jaibuduvin"! "J'ai bu du vin" is in French, tha=
t
I know at least, and translates to "I was drinking wine"!

My serious congratulation to your jokes!

Mes felicitacions serieux!

Amiti=E9,

G=E9za

On Sun, Apr 3, 2011 at 1:02 AM, Jorge Amodio <jmamodio@gmail.com> wrote:

> > I will send out notices as the release date in 2012 approaches.
>
> That's excellent, please send the notice before the Mayan calendar ends.
> Tnx.
>
> -J
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>

--002215974a768cb85d049ffb3d21
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,<br><br>Quite a few people reminded me for the date of your message, whi=
ch was All Fool Day.<br><br>Oh yes, I surely forgot to check this! Then I r=
ealised one more thing: I surely forgot to translate &quot;jaibuduvin&quot;=
! &quot;J&#39;ai bu du vin&quot; is in French, that I know at least, and tr=
anslates to &quot;I was drinking wine&quot;!<br>
<br>My serious congratulation to your jokes! <br><br>Mes felicitacions seri=
eux!<br><br>Amiti=E9,<br><br>G=E9za<br><br><div class=3D"gmail_quote">On Su=
n, Apr 3, 2011 at 1:02 AM, Jorge Amodio <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:jmamodio@gmail.com">jmamodio@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class=3D"im"=
>&gt; I will send out notices as the release date in 2012 approaches.<br>
<br>
</div>That&#39;s excellent, please send the notice before the Mayan calenda=
r ends. Tnx.<br>
<font color=3D"#888888"><br>
-J<br>
</font><div><div></div><div class=3D"h5">__________________________________=
_____________<br>
Ietf mailing list<br>
<a href=3D"mailto:Ietf@ietf.org">Ietf@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/ietf" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/ietf</a><br>
</div></div></blockquote></div><br>

--002215974a768cb85d049ffb3d21--

From randy_presuhn@mindspring.com  Mon Apr  4 11:00:20 2011
Return-Path: <randy_presuhn@mindspring.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 674523A686E for <ietf@core3.amsl.com>; Mon,  4 Apr 2011 11:00:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.392
X-Spam-Level: 
X-Spam-Status: No, score=-101.392 tagged_above=-999 required=5 tests=[AWL=1.207, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c3wyL4TbV879 for <ietf@core3.amsl.com>; Mon,  4 Apr 2011 11:00:19 -0700 (PDT)
Received: from elasmtp-galgo.atl.sa.earthlink.net (elasmtp-galgo.atl.sa.earthlink.net [209.86.89.61]) by core3.amsl.com (Postfix) with ESMTP id 837323A6867 for <ietf@ietf.org>; Mon,  4 Apr 2011 11:00:19 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=uFPtK7xWoCbv8Gi0IC+gFf35VdwSisXtwRdbDa8rP8twWvSGbGDk/gEMF9CHGJ41; h=Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [99.23.160.97] (helo=oemcomputer) by elasmtp-galgo.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1Q6o6D-0001SD-QC for ietf@ietf.org; Mon, 04 Apr 2011 14:02:02 -0400
Message-ID: <009201cbf2f2$921ef1a0$6801a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <ietf@ietf.org>
References: <tsl1v1q4a4j.fsf@mit.edu> <ldv4o6kb82w.fsf@cathode-dark-space.mit.edu>
Subject: Re: IETF and APIs
Date: Mon, 4 Apr 2011 11:03:14 -0700
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.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d888cc964a8bf633b382e401e7fb895483b8c10814bf8b80129e350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.23.160.97
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 18:00:20 -0000

Hi -

> From: "Tom Yu" <tlyu@MIT.EDU>
> To: "Sam Hartman" <hartmans-ietf@mit.edu>
> Cc: <iab@ietf.org>; <ietf@ietf.org>
> Sent: Wednesday, March 30, 2011 2:40 PM
> Subject: Re: IETF and APIs
>
> Personal observation: "API" is a subclass of "interface".  "Network
> protocol" is a subclass of "interface".  Interfaces (in the general
> case) are valuable things to standardize.  An abstract interface
> ("abstract API"?) that gives guidance to implementors above and beyond
> the bare specification of the network protocol is useful for achieving
> conceptual alignment.
> 
> Do people agree?

Yes and no.  The experience with SNMPv3's ASIs (Abstract Service
Interfaces) might be instructive.

   (1) because implementations of the protocol (or something very
         similar to it) already existed, requiring conformance to the
         ASIs (beyond the externally-visible behaviour they described)
         found no support.

   (2) Despite (1), there are *still* people who think the ASIs will be reflected
         in implementations' APIs.  (They generally aren't.)

   (3) Even though there was already considerable experience with the
         implementation of the protocol when these Abstract Service
         Interfaces were defined, later work (especially in the isms WG)
         found that these definitions required some serious tweaks to
         handle cases that people were already thinking about when the
         interfaces were defined in the first place.

   (4) Some of the lengthy WG discussions and awkward hacks 
         resulting from (3) in subsequent RFCs  were only an artifact of
         the specification technique, and were not necessitated by
         actual protocol or implementation constraints, in my opinion.

Still, I think it can be very helpful to specify a C library API for things that are
actually intended to be used like libraries, but I also know that it can
be surprisingly difficult to get them "right" for all environments.

Randy


From lear@cisco.com  Tue Apr  5 00:01:04 2011
Return-Path: <lear@cisco.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EFDA43A67EF for <ietf@core3.amsl.com>; Tue,  5 Apr 2011 00:01:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.585
X-Spam-Level: 
X-Spam-Status: No, score=-110.585 tagged_above=-999 required=5 tests=[AWL=0.014, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9AOXiDgmYqDp for <ietf@core3.amsl.com>; Tue,  5 Apr 2011 00:01:04 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id A97B03A68B5 for <ietf@ietf.org>; Tue,  5 Apr 2011 00:01:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=lear@cisco.com; l=906; q=dns/txt; s=iport; t=1301986967; x=1303196567; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=APEyXcC4hB3FEvJ1Cu0oxdFJwBNLCRiqMItKTe3AZmI=; b=f3K229/p2QKfI1hu5YpzZO2CRAIWwWqakV4R8M4ina5OAKpVgFmGc9CC CqJPfS2mbSSGSzl5rBnTCnvtSkLxpfDgnpQ4cJIe0AyB7qCA0ixr8Q4Bo AmdCHIGVEOi6UAKQTYJdtyCekR66Qke08oiwIbg7Zrma+C+zuLuMou0Wi s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhsHANi9mk2Q/khLgWdsb2JhbACETJQUjQkUAQEWJiWleYtOkGeBKINMdwSNJYxw
X-IronPort-AV: E=Sophos;i="4.63,303,1299456000"; d="scan'208";a="82194402"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-1.cisco.com with ESMTP; 05 Apr 2011 07:02:46 +0000
Received: from dhcp-10-55-85-10.cisco.com (dhcp-10-55-85-10.cisco.com [10.55.85.10]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p3572jFl017661; Tue, 5 Apr 2011 07:02:46 GMT
Message-ID: <4D9ABE73.2080402@cisco.com>
Date: Tue, 05 Apr 2011 09:02:11 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.15) Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: braden@isi.edu
Subject: Re: IETF and APIs
References: <tsl1v1q4a4j.fsf@mit.edu>	<4D919E0C.3030604@dcrocker.net>	<tslsju62sll.fsf@mit.edu>	<4D92E5C0.3070308@isi.edu> <4D9371E6.1090507@isi.edu>
In-Reply-To: <4D9371E6.1090507@isi.edu>
X-Enigmail-Version: 1.1.1
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.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 07:01:05 -0000

Bob, Joe,

Given this viewpoint, what guidance would you give, then, to protocol
designers who are writing specifications?

Eliot

On 3/30/11 8:09 PM, Bob Braden wrote:
> +1
>
> Bpb Braden
>
> On 3/30/2011 1:11 AM, Joe Touch wrote:
>> Hi, all,
>>
>> Perhaps we're not talking about an API, or even an abstract API, but
>> just the "application interface" (or just "upper layer service"
>> specification).
>>
>> RFC793 is a great example that a protocol provides a service, and
>> that service needs to be explained - and that explaining it does NOT
>> need to be done in a specific language.
>>
>> Joe
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>

From touch@isi.edu  Tue Apr  5 10:19:43 2011
Return-Path: <touch@isi.edu>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2BE4F28C132 for <ietf@core3.amsl.com>; Tue,  5 Apr 2011 10:19:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.496
X-Spam-Level: 
X-Spam-Status: No, score=-105.496 tagged_above=-999 required=5 tests=[AWL=1.103, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g8ICwBMLdnfh for <ietf@core3.amsl.com>; Tue,  5 Apr 2011 10:19:42 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 347A728C131 for <ietf@ietf.org>; Tue,  5 Apr 2011 10:19:42 -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 p35HL1hc003308 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Tue, 5 Apr 2011 10:21:01 -0700 (PDT)
Message-ID: <4D9B4F7C.60002@isi.edu>
Date: Tue, 05 Apr 2011 10:21:00 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Eliot Lear <lear@cisco.com>
Subject: Re: IETF and APIs
References: <tsl1v1q4a4j.fsf@mit.edu>	<4D919E0C.3030604@dcrocker.net>	<tslsju62sll.fsf@mit.edu>	<4D92E5C0.3070308@isi.edu>	<4D9371E6.1090507@isi.edu> <4D9ABE73.2080402@cisco.com>
In-Reply-To: <4D9ABE73.2080402@cisco.com>
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: braden@isi.edu, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 17:19:43 -0000

On 4/5/2011 12:02 AM, Eliot Lear wrote:
> Bob, Joe,
>
> Given this viewpoint, what guidance would you give, then, to protocol
> designers who are writing specifications?

IMO, we have never really explained what we expect in a protocol 
specification. We focus on required sections like "security 
considerations" and "IANA considerations", but we've never explained 
what we're looking for in a protocol spec.

Here's what I expect:

- description/format of "on the wire" messages
	basically the I/O to the layer below

- state at the endpoints
	if any (it's rare that there is none, even for so-called
	'stateless' protocols), and whether it's hard or soft

- upper layer service
	the I/O to the layer above

- event and action table
	a list of events:
		- message arrival
		- upper layer service request
		- timer event
		- other event (queue overload, etc.; any other
		condition that can act as a trigger)

	for each event, in each state:
		list the actions
			e.g., messages to emit,
			upper layer responses/signals
			timers to set/reset
			other state (e.g., queues) to manage
		and whether the state changes

Overall, this is basically a Mealy machine description. That's what I 
expect, and why it includes the upper layer service, IMO.

If this sort of thing is useful, I'd be glad to write it up - and keep 
it short. I still expect that protocol designers are familiar with the 
basics of protocols. ;-)

Joe


> Eliot
>
> On 3/30/11 8:09 PM, Bob Braden wrote:
>> +1
>>
>> Bpb Braden
>>
>> On 3/30/2011 1:11 AM, Joe Touch wrote:
>>> Hi, all,
>>>
>>> Perhaps we're not talking about an API, or even an abstract API, but
>>> just the "application interface" (or just "upper layer service"
>>> specification).
>>>
>>> RFC793 is a great example that a protocol provides a service, and
>>> that service needs to be explained - and that explaining it does NOT
>>> need to be done in a specific language.
>>>
>>> Joe
>>> _______________________________________________
>>> Ietf mailing list
>>> Ietf@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ietf
>>
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

From balaji.1manarmy@gmail.com  Wed Apr  6 00:20:57 2011
Return-Path: <balaji.1manarmy@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6995D3A68BB; Wed,  6 Apr 2011 00:20:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.397
X-Spam-Level: 
X-Spam-Status: No, score=-2.397 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_42=0.6, J_CHICKENPOX_53=0.6, NORMAL_HTTP_TO_IP=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BziquFES6euk; Wed,  6 Apr 2011 00:20:56 -0700 (PDT)
Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by core3.amsl.com (Postfix) with ESMTP id E352D3A68BF; Wed,  6 Apr 2011 00:20:55 -0700 (PDT)
Received: by qyk7 with SMTP id 7so766478qyk.10 for <multiple recipients>; Wed, 06 Apr 2011 00:22:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=9V89qokl/t+pDxcXZ1Y1BpoclRY1JHidIBj9Fo0+LCg=; b=VG7GWYEqvDT2Wfv8j/0auK+mGu15eYqhdjHop+OUU+NmnfFxlWPXsUvCJ4Q9VTjpXh uJiZcbc+Op2sxR1DMLglfMv+7I30P+YwNh2xviQOnKWQzT1WxUhPFjLBoHZQXbKrCcQ+ 3RpnTIbnOIQ6IgNkMSZDA+QIViF2wYgzQt7gk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=KPB6o0uQhTBEIadstc2CkPMV3UF1ZUszJjo+PsveX4DqjXkseW6fzCZIVCc726fXIS OdHnLW3kaV4ffweKiPNviBG0RMNqzfKBNe7CsWZrCNv+kksPcGYMQKUXv23lupsWjAnc tK4bZE78WBEck8OcpduzDZZJNP8R/JNof6pp8=
MIME-Version: 1.0
Received: by 10.229.95.144 with SMTP id d16mr499388qcn.37.1302074559322; Wed, 06 Apr 2011 00:22:39 -0700 (PDT)
Received: by 10.229.12.145 with HTTP; Wed, 6 Apr 2011 00:22:39 -0700 (PDT)
Date: Wed, 6 Apr 2011 12:52:39 +0530
Message-ID: <BANLkTinuvDwvkHsdizFFcfkxzpLzXXs8DQ@mail.gmail.com>
Subject: clarification needed in address assignment using IKEv2 Configuration Payload
From: Balaji J <balaji.1manarmy@gmail.com>
To: ietf@ietf.org, ipsec@ietf.org
Content-Type: multipart/alternative; boundary=001636832048945bcd04a03adb8c
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 07:24:10 -0000

--001636832048945bcd04a03adb8c
Content-Type: text/plain; charset=ISO-8859-1

Hi ppl,

Recently i have started reading the IKEv2 RFC(5996).
I need a clarification on assigning the ip address using ikev2 protocol as
below which i couldn't find in the RFC4718:

Is it valid to assign 0.0.0.0 IP address in the CFG_REPLY paylaod in
IKE_AUTH message to the initiator?
I need this information for the scenario where the initiator can obtain the
IP address by some other means(say DHCP).
But still if the initiator needs a secure channel to communicate with the
gateway first, before sending the DHCP request for obtaining IP address.
Now when the DHCP server provides the IP-address to the initiator,
can the SPD be updated updated at that time(by extracting the ip assigned to
the initator from the DHCP message) rather than
doing the same during the IKE_AUTH response?(as i am thinking of assigning
0.0.0.0 ip during initial IKE_AUTH response in CFG payload)

Because when i looked in to RFC4306 under section 2.19(Requesting an
Internal Address on a Remote Network) , it says,
"Message from responder to initiator:
                   CP(CFG_REPLY)= INTERNAL_ADDRESS(192.0.2.202)

INTERNAL_NETMASK(255.255.255.0)
                                                INTERNAL_SUBNET(
192.0.2.0/255.255.255.0)
                                                TSi = (0,
0-65535,192.0.2.202-192.0.2.202)
                                                TSr = (0,
0-65535,192.0.2.0-192.0.2.255)
 * All returned values will be implementation dependent."

There is no mention in RFC something like "assigning 0.0.0.0 should be
handled as ERROR".
So can i safely say assigning 0.0.0.0 ip address is compliant with RFC?

Also section 3.15.4. (Address Assignment Failures) says,
"If the initiator does not receive the IP address(es) required by its
 policy, it MAY keep the IKE SA up and retry the Configuration payload
 as separate INFORMATIONAL exchange after suitable timeout"

Does it mean that the IPSEC-SA cannot be created unless a valid ip is
assigned?
It is possible to create IPSEC-SA with the traffic-selector alone, rite? why
do we need to bother about IP allocation?
Assume that there is policy in initiator which says "0.0.0.0 MUST be the
ip-address allocated by NAS", then is it valid
to send the same in CFG_REPLY payload?

Any help is highly appreciated.

Thanks,
...Balaji.J

--001636832048945bcd04a03adb8c
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi ppl,<br><br>Recently i have started reading the IKEv2 RFC(5996).<br>I ne=
ed a clarification on assigning the ip address using ikev2 protocol as belo=
w which i couldn&#39;t find in the RFC4718:<br><br>Is it valid to assign 0.=
0.0.0 IP address in the CFG_REPLY paylaod in IKE_AUTH message to the initia=
tor?<br>
I need this information for the scenario where the initiator can obtain the=
 IP address by some other means(say DHCP).<br>But still if the initiator ne=
eds a secure channel to communicate with the gateway first, before sending =
the DHCP request for obtaining IP address.<br>
Now when the DHCP server provides the IP-address to the initiator,<br>can t=
he SPD be updated updated at that time(by extracting the ip assigned to the=
 initator from the DHCP message) rather than<br>doing the same during the I=
KE_AUTH response?(as i am thinking of assigning 0.0.0.0 ip during initial I=
KE_AUTH response in CFG payload)<br>
<br>Because when i looked in to RFC4306 under section 2.19(Requesting an In=
ternal Address on a Remote Network) , it says,<br>&quot;Message from respon=
der to initiator:<br>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
 CP(CFG_REPLY)=3D INTERNAL_ADDRESS(192.0.2.202)<br>
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 INTERNAL=
_NETMASK(255.255.255.0)<br>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0 INTERNAL_SUBNET(<a href=3D"http://192.0.2.0/255.255.255.=
0">192.0.2.0/255.255.255.0</a>)<br>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0 TSi =3D (0, 0-65535,192.0.2.202-192.0.2.202)<br=
>
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 TSr =3D =
(0, 0-65535,192.0.2.0-192.0.2.255)<br>=A0* All returned values will be impl=
ementation dependent.&quot;<br><br>There is no mention in RFC something lik=
e &quot;assigning 0.0.0.0 should be handled as ERROR&quot;.<br>
So can i safely say assigning 0.0.0.0 ip address is compliant with RFC?<br>=
<br>Also section <a name=3D"section-3.15.4">3.15.4</a>.  (Address Assignmen=
t Failures) says,<br>&quot;If the initiator does not receive the IP address=
(es) required by its<br>
=A0policy, it MAY keep the IKE SA up and retry the Configuration payload<br=
>=A0as separate INFORMATIONAL exchange after suitable timeout&quot;<br><br>=
Does it mean that the IPSEC-SA cannot be created unless a valid ip is assig=
ned?<br>
It is possible to create IPSEC-SA with the traffic-selector alone, rite? wh=
y do we need to bother about IP allocation?<br>Assume that there is policy =
in initiator which says &quot;0.0.0.0 MUST be the ip-address allocated by N=
AS&quot;, then is it valid<br>
to send the same in CFG_REPLY payload?<br><br><span class=3D"h4"></span>Any=
 help is highly appreciated.<br><br>Thanks,<br>...Balaji.J<br><br>

--001636832048945bcd04a03adb8c--

From dhc2@dcrocker.net  Wed Apr  6 06:59:31 2011
Return-Path: <dhc2@dcrocker.net>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 80A0E3A69C5 for <ietf@core3.amsl.com>; Wed,  6 Apr 2011 06:59:31 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wAgblGvpBBAb for <ietf@core3.amsl.com>; Wed,  6 Apr 2011 06:59:30 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id A57173A693E for <ietf@ietf.org>; Wed,  6 Apr 2011 06:59:30 -0700 (PDT)
Received: from [192.168.1.9] (adsl-67-127-56-68.dsl.pltn13.pacbell.net [67.127.56.68]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p36E18lR025691 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Wed, 6 Apr 2011 07:01:13 -0700
Message-ID: <4D9C7223.8050302@dcrocker.net>
Date: Wed, 06 Apr 2011 07:01:07 -0700
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>
Subject: Re: Buckets of spam coming through IETF lists
References: <alpine.BSF.2.00.1104011624500.30110@joyce.lan> <E215C7B5-8CAB-400D-80DA-21DF7B6D138B@cisco.com>
In-Reply-To: <E215C7B5-8CAB-400D-80DA-21DF7B6D138B@cisco.com>
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]); Wed, 06 Apr 2011 07:01:13 -0700 (PDT)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 13:59:31 -0000

On 4/1/2011 9:08 PM, Fred Baker wrote:
> On Apr 1, 2011, at 10:28 PM, John R. Levine wrote:
>> Some clever spambot seems to have scraped a bunch of addresses out of the
>> archives and is sending spam with multiple addresses on the From: line
>> through IETF and IRTF mailing lists.  Surely I'm not the only one who's
>> seeing it.
>
> DKIM is directly designed to address this... What do we need to do to put it
> in play?


Unfortunately, DKIM is /not/ design to address this.  DKIM is designed to 
provide a reliable, accurate identifier upon which reputation data can be developed.

That's a fundamentally different task from detected invalid From: field contents.

ADSP, and add-on to DKIM, is felt by its promoters to be useful for detecting 
invalid From: fields, but it does not work through mailing lists.

d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From housley@vigilsec.com  Wed Apr  6 08:25:27 2011
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 806873A680A for <ietf@core3.amsl.com>; Wed,  6 Apr 2011 08:25:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.514
X-Spam-Level: 
X-Spam-Status: No, score=-102.514 tagged_above=-999 required=5 tests=[AWL=0.085, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fFLa+CbgNbck for <ietf@core3.amsl.com>; Wed,  6 Apr 2011 08:25:26 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by core3.amsl.com (Postfix) with ESMTP id F361728C122 for <ietf@ietf.org>; Wed,  6 Apr 2011 08:25:23 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id E21989A485A for <ietf@ietf.org>; Wed,  6 Apr 2011 11:27:16 -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 scRUnJcO+RJu for <ietf@ietf.org>; Wed,  6 Apr 2011 11:26:57 -0400 (EDT)
Received: from [192.168.2.100] (pool-71-178-218-117.washdc.fios.verizon.net [71.178.218.117]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 76D399A4859 for <ietf@ietf.org>; Wed,  6 Apr 2011 11:27:16 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: draft-housley-two-maturity-levels-05 
Date: Wed, 6 Apr 2011 11:27:07 -0400
References: <20110406152226.000AF3A6803@core3.amsl.com>
To: IETF <ietf@ietf.org>
Message-Id: <24582656-5993-46C3-B82A-883E8BA4E9A0@vigilsec.com>
Mime-Version: 1.0 (Apple Message framework v1082)
X-Mailer: Apple Mail (2.1082)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 15:25:27 -0000

This revision proposes a solution to the issue raised by Brian Carpenter =
about documents lingering at Draft Standard.  Some people thought it was =
a problem.  Others thought it did not matter.  The proposed solution =
leaves the matter in the hands of the IESG.

Russ


Begin forwarded message:

> From: IETF I-D Submission Tool <idsubmission@ietf.org>
> Date: April 6, 2011 11:22:25 AM EDT
> To: housley@vigilsec.com
> Cc: dcrocker@bbiw.net, eburger@standardstrack.com
> Subject: New Version Notification for =
draft-housley-two-maturity-levels-05=20
>=20
>=20
> A new version of I-D, draft-housley-two-maturity-levels-05.txt has =
been successfully submitted by Russ Housley and posted to the IETF =
repository.
>=20
> Filename:	 draft-housley-two-maturity-levels
> Revision:	 05
> Title:		 Reducing the Standards Track to Two Maturity =
Levels
> Creation_date:	 2011-04-06
> WG ID:		 Independent Submission
> Number_of_pages: 7
>=20
> Abstract:
> This document proposes several changes to the Internet Engineering
> Task Force (IETF) Standards Process defined in RFC 2026, primarily a
> reduction from three IETF standards track maturity levels to two.
>=20
> {{ RFC Editor: please change "proposes several changes to the" to
> "changes the". }}
>=20
>=20
>=20
> The IETF Secretariat.
>=20
>=20


From fluffy@cisco.com  Wed Apr  6 08:41:26 2011
Return-Path: <fluffy@cisco.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0FA343A6945 for <ietf@core3.amsl.com>; Wed,  6 Apr 2011 08:41:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.569
X-Spam-Level: 
X-Spam-Status: No, score=-110.569 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pxlZQRuXZR8L for <ietf@core3.amsl.com>; Wed,  6 Apr 2011 08:41:25 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id 49B643A6819 for <ietf@ietf.org>; Wed,  6 Apr 2011 08:41:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fluffy@cisco.com; l=1118; q=dns/txt; s=iport; t=1302104589; x=1303314189; h=mime-version:subject:from:in-reply-to:date: content-transfer-encoding:message-id:references:to; bh=liqRcS44eueKbnFaxskIdiDiLAZ7901piloobpZhDjc=; b=fVEstdogfbDzUhzDZJ6ELYUksanXxZNqusmycayIaB1PcODa93IxPq4d +eJr6jB9Z/O87SBbIgyN7piRADsL3/MJqp9bIzzdvvNYnwMntJJUih8cz P5Ls2zOpXtkKZdxqCy/2VR+WrJFdVr0S/U8sIoNq1euq0fuIhP36Ka2MN U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAPaInE2rRDoH/2dsb2JhbACleHeIeZwnnEGFbASFTodug2M
X-IronPort-AV: E=Sophos;i="4.63,310,1299456000"; d="scan'208";a="331820039"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by sj-iport-2.cisco.com with ESMTP; 06 Apr 2011 15:43:09 +0000
Received: from [192.168.4.100] (rcdn-fluffy-8712.cisco.com [10.99.9.19]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p36Fh8vP008081 for <ietf@ietf.org>; Wed, 6 Apr 2011 15:43:08 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: Last Call: <draft-ietf-enum-iax-10.txt> (IANA Registration for Enumservice 'iax') to Informational RFC
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <20110405114802.9938.53269.idtracker@localhost>
Date: Wed, 6 Apr 2011 09:46:21 -0600
Content-Transfer-Encoding: 7bit
Message-Id: <6AA9EF58-AF11-4539-AA3D-BF4DEE5ABAC0@cisco.com>
References: <20110405114802.9938.53269.idtracker@localhost>
To: IETF Discussion <ietf@ietf.org>
X-Mailer: Apple Mail (2.1084)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 15:41:26 -0000

FWIW ... I reviewed this and thought it looked fine. 

On Apr 5, 2011, at 5:48 AM, The IESG wrote:

> 
> The IESG has received a request from the Telephone Number Mapping WG
> (enum) to consider the following document:
> - 'IANA Registration for Enumservice 'iax''
>  <draft-ietf-enum-iax-10.txt> as an 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 2011-04-19. 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.
> 
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-enum-iax/
> 
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-enum-iax/
> 
> 
> 
> No IPR declarations have been submitted directly on this I-D.
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce


From vesely@tana.it  Wed Apr  6 08:47:30 2011
Return-Path: <vesely@tana.it>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3D2163A68CF for <ietf@core3.amsl.com>; Wed,  6 Apr 2011 08:47:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.25
X-Spam-Level: 
X-Spam-Status: No, score=-5.25 tagged_above=-999 required=5 tests=[AWL=-0.531,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LZmc1t-ozQ-v for <ietf@core3.amsl.com>; Wed,  6 Apr 2011 08:47:27 -0700 (PDT)
Received: from wmail.tana.it (www.tana.it [62.94.243.226]) by core3.amsl.com (Postfix) with ESMTP id 465673A6819 for <ietf@ietf.org>; Wed,  6 Apr 2011 08:47:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tana.it; s=test; t=1302104949; bh=SJjJxuexDbzHAUsHC3dmewxO3uOMMxSXs9e7s8H5SXM=; l=2230; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Content-Transfer-Encoding; b=hsEp5Sjgc4Q7gLcyS4VaTR8ayasRIB1gzL0utOxRImRHaEVtrRq3FmmEJvF5wz+DG 0EhM/MD+kqnxkC1qsfwjdjP+GmrCe53m7O7ZYizlcMPJfIhJ+OLtAndRIeU0xY+bXY yfWteNjReK7K/dzYcmWGakgppztl+CjW7xtdj/84=
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; Wed, 06 Apr 2011 17:49:09 +0200 id 00000000005DC035.000000004D9C8B75.000033F0
Message-ID: <4D9C8B75.5020503@tana.it>
Date: Wed, 06 Apr 2011 17:49:09 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.15) Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Buckets of spam coming through IETF lists
References: <alpine.BSF.2.00.1104011624500.30110@joyce.lan>	<E215C7B5-8CAB-400D-80DA-21DF7B6D138B@cisco.com> <4D9C7223.8050302@dcrocker.net>
In-Reply-To: <4D9C7223.8050302@dcrocker.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 15:47:30 -0000

On 06/Apr/11 16:01, Dave CROCKER wrote:
> On 4/1/2011 9:08 PM, Fred Baker wrote:
>> On Apr 1, 2011, at 10:28 PM, John R. Levine wrote:
>>> Some clever spambot seems to have scraped a bunch of addresses out
>>> of the
>>> archives and is sending spam with multiple addresses on the From: line
>>> through IETF and IRTF mailing lists.  Surely I'm not the only one
>>> who's
>>> seeing it.
>>
>> DKIM is directly designed to address this... What do we need to do
>> to put it in play?
> 
> Unfortunately, DKIM is /not/ designed to address this.  DKIM is designed
> to provide a reliable, accurate identifier upon which reputation data
> can be developed.

Yet, as the MLM-draft documents:

  MLMs typically attempt to authenticate messages posted through them.
  They usually do this through the trivial (and insecure) means of
  verifying the RFC5322.From field email address (or, less frequently,
  the RFC5321.MailFrom parameter) against a list registry.  DKIM
  enables a stronger form of authentication, although this is not yet
  formally documented: It can require that messages using a given
  RFC5322.From address also have a DKIM signature with a corresponding
  "d=" domain.  This feature would be somewhat similar to using ADSP,
  except that the requirement for it would be imposed by the MLM and
  not the author's organization.
               http://tools.ietf.org/html/draft-ietf-dkim-mailinglists

It would be interesting to implement such authentication for IETF
lists, e.g. as part of some IETF Code Sprint.  It will alleviate
moderation, although it will require some maintenance for itself.

> That's a fundamentally different task from detected invalid From:
> field contents.

Likewise, DKIM hardly supports non-repudiation of content, if at all.

> ADSP, and add-on to DKIM, is felt by its promoters to be useful for
> detecting invalid From: fields, but it does not work through
> mailing lists.

The "somewhat similar feature" described in the MLM-draft assumes that
(some) posters consistently use submission servers that DKIM-sign
relayed mail.  Thus, the MLM can automatically reject posts claiming
to be from such posters, if they are not validly signed.

From rja.lists@gmail.com  Wed Apr  6 09:25:13 2011
Return-Path: <rja.lists@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7B7153A694F for <ietf@core3.amsl.com>; Wed,  6 Apr 2011 09:25:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.904
X-Spam-Level: 
X-Spam-Status: No, score=-2.904 tagged_above=-999 required=5 tests=[AWL=-0.305, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EuTgZUTb4kw5 for <ietf@core3.amsl.com>; Wed,  6 Apr 2011 09:25:12 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by core3.amsl.com (Postfix) with ESMTP id 62DE73A67AF for <ietf@ietf.org>; Wed,  6 Apr 2011 09:25:12 -0700 (PDT)
Received: by vxg33 with SMTP id 33so1523736vxg.31 for <ietf@ietf.org>; Wed, 06 Apr 2011 09:26:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:content-type:content-transfer-encoding :subject:date:message-id:to:mime-version:x-mailer; bh=g3q8NiEG2kUXS/jr3L0bQj3TMBSz5nFdrP+jq3Czugc=; b=SpVevBbAvIxNfRDPojHEhQsQekQAtCP2xXlzd+er26hrI+RU4viUaKgmg+OrGMWJGw WoqtKXbGlyao94HQ9eIRnROBDPSI0Yr7VxBQCXAtFdrnRGnO83R1EWkuFaN/RNtq9DFj Nu+Ucy0NbcX1vBViqyOQ6hORlF8ujPRVDxdtY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:message-id :to:mime-version:x-mailer; b=Wo/I1J5RDNeXdpzwOvNyb17ZZ/cS0eUwKOffRvIPDV11/KDwoTi02CbssV8JEOPV5S OH+xqh3RHF9+5hP1cWbHGlQJrGAgWR5OF6buoWOPo7NNv1Ipad+jEAzGFKQHr7yd+Poh UfoXctCaJHbYg3deLCHw9hON/t6lvn/MGFF4w=
Received: by 10.52.18.74 with SMTP id u10mr1685113vdd.192.1302107215964; Wed, 06 Apr 2011 09:26:55 -0700 (PDT)
Received: from [10.30.20.7] (pool-96-225-170-25.nrflva.fios.verizon.net [96.225.170.25]) by mx.google.com with ESMTPS id e37sm434150vbm.17.2011.04.06.09.26.54 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 06 Apr 2011 09:26:54 -0700 (PDT)
From: RJ Atkinson <rja.lists@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: draft-housley-two-maturity-levels-05  
Date: Wed, 6 Apr 2011 12:26:51 -0400
Message-Id: <90C62BD8-45F6-4192-8234-0645B483AC32@gmail.com>
To: 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.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 16:25:13 -0000

The last *several* revisions have been perfectly fine.  
The most recent edits are also fine.

We're micro-editing this document at this point, meaning that 
"perfect" is impeding our ability to deploy "more than good enough" 
to replace 3-tier system that most IETF folks agree is broken,
and has been broken for at least a decade.

A tiny few people might like to edit this document more, 
but the IETF supposedly operates upon rough consensus, 
rather than either smooth consensus or unanimity.  

Could we please Last Call, approve, and ship this right now ?

Yours,

Ran Atkinson


From julian.reschke@gmx.de  Wed Apr  6 09:49:13 2011
Return-Path: <julian.reschke@gmx.de>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3449C3A6959 for <ietf@core3.amsl.com>; Wed,  6 Apr 2011 09:48:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.795
X-Spam-Level: 
X-Spam-Status: No, score=-103.795 tagged_above=-999 required=5 tests=[AWL=-1.196, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5yzjZK55w27R for <ietf@core3.amsl.com>; Wed,  6 Apr 2011 09:48:41 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by core3.amsl.com (Postfix) with SMTP id 384643A69DD for <ietf@ietf.org>; Wed,  6 Apr 2011 09:45:14 -0700 (PDT)
Received: (qmail invoked by alias); 06 Apr 2011 16:45:34 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.131]) [217.91.35.233] by mail.gmx.net (mp056) with SMTP; 06 Apr 2011 18:45:34 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/RL2xs5eLRE2UtjDYMrD1VIqTWQRRwG14QaHM7iF A+tiKTeH6Jstgv
Message-ID: <4D9C98A6.8000608@gmx.de>
Date: Wed, 06 Apr 2011 18:45:26 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
Subject: Re: draft-housley-two-maturity-levels-05
References: <20110406152226.000AF3A6803@core3.amsl.com> <24582656-5993-46C3-B82A-883E8BA4E9A0@vigilsec.com>
In-Reply-To: <24582656-5993-46C3-B82A-883E8BA4E9A0@vigilsec.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 16:49:13 -0000

On 06.04.2011 17:27, Russ Housley wrote:
> This revision proposes a solution to the issue raised by Brian Carpenter about documents lingering at Draft Standard.  Some people thought it was a problem.  Others thought it did not matter.  The proposed solution leaves the matter in the hands of the IESG.
>
> Russ
> ...

A question...:

>    A specification shall remain at the Proposed Standard maturity level
>    for at least six (6) months before consideration for advancement to
>    the Internet Standard maturity level.

It would probably good to clarify when the six month period starts (IESG 
approval? RFC publication?).

Best regards, Julian

From stpeter@stpeter.im  Wed Apr  6 10:13:00 2011
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 77CB328C0DE for <ietf@core3.amsl.com>; Wed,  6 Apr 2011 10:13:00 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y6Moeau8-bBw for <ietf@core3.amsl.com>; Wed,  6 Apr 2011 10:12:59 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id 7BF9A3A68AB for <ietf@ietf.org>; Wed,  6 Apr 2011 10:12:59 -0700 (PDT)
Received: from leavealone.cisco.com (72-163-0-129.cisco.com [72.163.0.129]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 0B5CA40D15; Wed,  6 Apr 2011 11:17:06 -0600 (MDT)
Message-ID: <4D9C9F7F.7010609@stpeter.im>
Date: Wed, 06 Apr 2011 11:14:39 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Julian Reschke <julian.reschke@gmx.de>
Subject: Re: draft-housley-two-maturity-levels-05
References: <20110406152226.000AF3A6803@core3.amsl.com>	<24582656-5993-46C3-B82A-883E8BA4E9A0@vigilsec.com> <4D9C98A6.8000608@gmx.de>
In-Reply-To: <4D9C98A6.8000608@gmx.de>
X-Enigmail-Version: 1.1.1
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms010506080102090306010301"
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 17:13:00 -0000

This is a cryptographically signed message in MIME format.

--------------ms010506080102090306010301
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 4/6/11 10:45 AM, Julian Reschke wrote:
> On 06.04.2011 17:27, Russ Housley wrote:
>> This revision proposes a solution to the issue raised by Brian
>> Carpenter about documents lingering at Draft Standard.  Some people
>> thought it was a problem.  Others thought it did not matter.  The
>> proposed solution leaves the matter in the hands of the IESG.
>>
>> Russ
>> ...
>=20
> A question...:
>=20
>>    A specification shall remain at the Proposed Standard maturity leve=
l
>>    for at least six (6) months before consideration for advancement to=

>>    the Internet Standard maturity level.
>=20
> It would probably good to clarify when the six month period starts (IES=
G
> approval? RFC publication?).

RFC publication seems sensible -- sometimes it can take more than six
months between IESG approval and RFC publication! (Slow authors during
AUTH48, dependencies on yet-to-be-published specs, etc.)

Peter

--=20
Peter Saint-Andre
https://stpeter.im/




--------------ms010506080102090306010301
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIITzjCC
BjQwggQcoAMCAQICASMwDQYJKoZIhvcNAQELBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoT
DVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNp
Z25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3
MTAyNDIxMDMzM1oXDTE3MTAyNDIxMDMzM1owgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1T
dGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu
aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAzIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBALmjSW4SPiDKlAinvVeL
ZOVfItiuP1aRHL530E7QUc9icCwL33+PH+Js1HAh8CgWFl34sOxx1FJyS/C4VLPRsqDfP72j
tzCVUAL0DAxZ7wgzQvFz7x61jGxfhYhqYb1+PPOLkYBbkRIrPMg3dLEdKmXIYJYXDH+mB/V/
jLo73/Kb7h/rNoNg/oHHSv5Jolyvp5IY2btfcTBfW/telEFj5rDTX2juTvZ3Qhf3XQX5ca3Q
7A10zrUV/cWJOJ7F5RltbEIaboZmX5JBUb3FhUiAdBotehAX6DbDOuYoJtVxmGof6GuVGcPo
98K4TJf8FHo+UA9EOVDp/W7fCqKT4sXk/XkCAwEAAaOCAa0wggGpMA8GA1UdEwEB/wQFMAMB
Af8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBR7iZySlyShhEcCy3T8LvSs3DLl8zAfBgNV
HSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRaMFgwJwYIKwYBBQUH
MAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYhaHR0cDovL3d3
dy5zdGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6Ly93d3cu
c3RhcnRzc2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5jb20v
c2ZzY2EuY3JsMIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQELBQADggIBAGpd
SbdLFMhirxK37V4gE00+uW74UdAXtDgQI3AsRZWtaRtKHgAxFBSteqz4kDkeAjH/1b+K8tQR
6cxSI2nho7qOaPW/UpzOfSS/MeKK/9vfM2lfs+uItXH7LWtvS9wD1erfH1a+BXHCrCp4LA1l
fADDhRIiGTSS3i0Zu5xV3INNRHrCCCl6patltQ8RZTqzDMri7ombgIxjN51Zo7xV77EZcThV
0GA8iIN+7T53uHhUJpjfLIztHs/69OclRvHux9hCflfOm7GY5Sc4nqjfES+5XPArGGWiQSEk
ez37QfXqsxO3oCHK4b3DFZysG4uyOuC/WL80ab3muQ3tgwjBhq0D3JZN5kvu5gSuNZPa1WrV
hEgXkd6C7s5stqB6/htVpshG08jRz9DEutGM9oKQ1ncTivbfPNx7pILoHWvvT7N5i/puVoNu
bPUmLXh/2wA6wzAzuuoONiIL14Xpw6jLSnqpaLWElo2yTIFZ/CU/nCvvpW1Dj1457P3Ci9bD
0RPkWSR+CuucpgxrEmaw4UOLxflzuYYaq1RJwygOO5K0s2bAWOcXpgteyUOnQ3d/EjJAWRri
2v0ubiq+4H3KUOMlbznlPAY/1T8YyyJPM88+Ueahe/AW1zoUwZayNcTnuM7cq6yBV8Wr3GOI
LFXhtT0UVuJLChPMJKVKVsa7qNorlLkMMIIGxzCCBa+gAwIBAgICAIswDQYJKoZIhvcNAQEF
BQAwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJT
ZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBD
bGFzcyAzIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTAeFw0xMDEwMTQwMTM2MzRa
Fw0xMjEwMTQxMjAxMDdaMIHAMSAwHgYDVQQNExcyNzQ1ODEtOU5YMDRxeExEYjBvNDY5VDEL
MAkGA1UEBhMCVVMxETAPBgNVBAgTCENvbG9yYWRvMQ8wDQYDVQQHEwZEZW52ZXIxLDAqBgNV
BAsTI1N0YXJ0Q29tIFRydXN0ZWQgQ2VydGlmaWNhdGUgTWVtYmVyMRowGAYDVQQDExFQZXRl
ciBTYWludC1BbmRyZTEhMB8GCSqGSIb3DQEJARYSc3RwZXRlckBzdHBldGVyLmltMIIBIjAN
BgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAuERvnrkpQTx9wbJfgxbNKEYvt0IilecZRUM6
wrbCzIUPCocuYhaAJcQoqIyHaKybPQ7f+DIGIAolAa3dHnNdlsXP2smTft/ZNpj10PIG5bil
NAqLUYwmLJaEaqY7BMW8423U3blW43/luLJk/Pq4OsWcw7AK3LeVh1U/HOgqhin26N3h72X1
nbLEpZFrgcp8egmWtXLCbLBDMqUK3j6wjLldni79muzYEVqU0A5GqSeb8Wc4kIx8VI5yL24J
KzinG2iVRP5ZDEbOZETzBXJabUsV56XSxqPG9DK6ke+ybCiL/wKV1HFqdtFB1y25lfvHgOP2
gyEApBKEDNjgLmKyyQIDAQABo4IC+zCCAvcwCQYDVR0TBAIwADALBgNVHQ8EBAMCBLAwHQYD
VR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMB0GA1UdDgQWBBS2EW2iNB+g0EibKJLBdv8I
eLovVDAfBgNVHSMEGDAWgBR7iZySlyShhEcCy3T8LvSs3DLl8zAdBgNVHREEFjAUgRJzdHBl
dGVyQHN0cGV0ZXIuaW0wggFCBgNVHSAEggE5MIIBNTCCATEGCysGAQQBgbU3AQICMIIBIDAu
BggrBgEFBQcCARYiaHR0cDovL3d3dy5zdGFydHNzbC5jb20vcG9saWN5LnBkZjA0BggrBgEF
BQcCARYoaHR0cDovL3d3dy5zdGFydHNzbC5jb20vaW50ZXJtZWRpYXRlLnBkZjCBtwYIKwYB
BQUHAgIwgaowFBYNU3RhcnRDb20gTHRkLjADAgEBGoGRTGltaXRlZCBMaWFiaWxpdHksIHNl
ZSBzZWN0aW9uICpMZWdhbCBMaW1pdGF0aW9ucyogb2YgdGhlIFN0YXJ0Q29tIENlcnRpZmlj
YXRpb24gQXV0aG9yaXR5IFBvbGljeSBhdmFpbGFibGUgYXQgaHR0cDovL3d3dy5zdGFydHNz
bC5jb20vcG9saWN5LnBkZjBjBgNVHR8EXDBaMCugKaAnhiVodHRwOi8vd3d3LnN0YXJ0c3Ns
LmNvbS9jcnR1My1jcmwuY3JsMCugKaAnhiVodHRwOi8vY3JsLnN0YXJ0c3NsLmNvbS9jcnR1
My1jcmwuY3JsMIGOBggrBgEFBQcBAQSBgTB/MDkGCCsGAQUFBzABhi1odHRwOi8vb2NzcC5z
dGFydHNzbC5jb20vc3ViL2NsYXNzMy9jbGllbnQvY2EwQgYIKwYBBQUHMAKGNmh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2NlcnRzL3N1Yi5jbGFzczMuY2xpZW50LmNhLmNydDAjBgNVHRIE
HDAahhhodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS8wDQYJKoZIhvcNAQEFBQADggEBADVtbXJG
tKAr55xc/OUM546gXUybI72Bank0w739Mv+9BBNtq9rMEvCnLmSKhBi76c1mdXh6zXs8RQDo
6nR/aPabE3llF2T4z80smi9jfnl3y9dpu9TcgDoqDLZ7a2lBlW656XAAQzHjvLp2MC7/mxlg
PYH2axa+q40mAYM20GbNsAEGbWQT1IqIh0BcLLsgbaMJHbyG/57zd9JLyMX3Vry1L1fJRQr3
GeLxMV5RtxN+mBgxrwFz/cOc09COiFExlsHgekpB5O43gqsAU16MXypyoSt4MrSfKTMHIGx6
2RF/M6vqUlvhi28gk2ZUvQ/+OX5+gjcZyooEzAAn4RuOKNswggbHMIIFr6ADAgECAgIAizAN
BgkqhkiG9w0BAQUFADCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4x
KzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMT
L1N0YXJ0Q29tIENsYXNzIDMgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBMB4XDTEw
MTAxNDAxMzYzNFoXDTEyMTAxNDEyMDEwN1owgcAxIDAeBgNVBA0TFzI3NDU4MS05TlgwNHF4
TERiMG80NjlUMQswCQYDVQQGEwJVUzERMA8GA1UECBMIQ29sb3JhZG8xDzANBgNVBAcTBkRl
bnZlcjEsMCoGA1UECxMjU3RhcnRDb20gVHJ1c3RlZCBDZXJ0aWZpY2F0ZSBNZW1iZXIxGjAY
BgNVBAMTEVBldGVyIFNhaW50LUFuZHJlMSEwHwYJKoZIhvcNAQkBFhJzdHBldGVyQHN0cGV0
ZXIuaW0wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC4RG+euSlBPH3Bsl+DFs0o
Ri+3QiKV5xlFQzrCtsLMhQ8Khy5iFoAlxCiojIdorJs9Dt/4MgYgCiUBrd0ec12Wxc/ayZN+
39k2mPXQ8gbluKU0CotRjCYsloRqpjsExbzjbdTduVbjf+W4smT8+rg6xZzDsArct5WHVT8c
6CqGKfbo3eHvZfWdssSlkWuBynx6CZa1csJssEMypQrePrCMuV2eLv2a7NgRWpTQDkapJ5vx
ZziQjHxUjnIvbgkrOKcbaJVE/lkMRs5kRPMFclptSxXnpdLGo8b0MrqR77JsKIv/ApXUcWp2
0UHXLbmV+8eA4/aDIQCkEoQM2OAuYrLJAgMBAAGjggL7MIIC9zAJBgNVHRMEAjAAMAsGA1Ud
DwQEAwIEsDAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwHQYDVR0OBBYEFLYRbaI0
H6DQSJsoksF2/wh4ui9UMB8GA1UdIwQYMBaAFHuJnJKXJKGERwLLdPwu9KzcMuXzMB0GA1Ud
EQQWMBSBEnN0cGV0ZXJAc3RwZXRlci5pbTCCAUIGA1UdIASCATkwggE1MIIBMQYLKwYBBAGB
tTcBAgIwggEgMC4GCCsGAQUFBwIBFiJodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9wb2xpY3ku
cGRmMDQGCCsGAQUFBwIBFihodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9pbnRlcm1lZGlhdGUu
cGRmMIG3BggrBgEFBQcCAjCBqjAUFg1TdGFydENvbSBMdGQuMAMCAQEagZFMaW1pdGVkIExp
YWJpbGl0eSwgc2VlIHNlY3Rpb24gKkxlZ2FsIExpbWl0YXRpb25zKiBvZiB0aGUgU3RhcnRD
b20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgUG9saWN5IGF2YWlsYWJsZSBhdCBodHRwOi8v
d3d3LnN0YXJ0c3NsLmNvbS9wb2xpY3kucGRmMGMGA1UdHwRcMFowK6ApoCeGJWh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2NydHUzLWNybC5jcmwwK6ApoCeGJWh0dHA6Ly9jcmwuc3RhcnRz
c2wuY29tL2NydHUzLWNybC5jcmwwgY4GCCsGAQUFBwEBBIGBMH8wOQYIKwYBBQUHMAGGLWh0
dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9zdWIvY2xhc3MzL2NsaWVudC9jYTBCBggrBgEFBQcw
AoY2aHR0cDovL3d3dy5zdGFydHNzbC5jb20vY2VydHMvc3ViLmNsYXNzMy5jbGllbnQuY2Eu
Y3J0MCMGA1UdEgQcMBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tLzANBgkqhkiG9w0BAQUF
AAOCAQEANW1tcka0oCvnnFz85QznjqBdTJsjvYFqeTTDvf0y/70EE22r2swS8KcuZIqEGLvp
zWZ1eHrNezxFAOjqdH9o9psTeWUXZPjPzSyaL2N+eXfL12m71NyAOioMtntraUGVbrnpcABD
MeO8unYwLv+bGWA9gfZrFr6rjSYBgzbQZs2wAQZtZBPUioiHQFwsuyBtowkdvIb/nvN30kvI
xfdWvLUvV8lFCvcZ4vExXlG3E36YGDGvAXP9w5zT0I6IUTGWweB6SkHk7jeCqwBTXoxfKnKh
K3gytJ8pMwcgbHrZEX8zq+pSW+GLbyCTZlS9D/45fn6CNxnKigTMACfhG44o2zGCA80wggPJ
AgEBMIGTMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UE
CxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRD
b20gQ2xhc3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAgCLMAkGBSsOAwIa
BQCgggIOMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDQw
NjE3MTQzOVowIwYJKoZIhvcNAQkEMRYEFBN92nMwvOL4BKhTQNGpFTURq8VqMF8GCSqGSIb3
DQEJDzFSMFAwCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggq
hkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBpAYJKwYBBAGCNxAEMYGWMIGT
MIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2Vj
dXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xh
c3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAgCLMIGmBgsqhkiG9w0BCRAC
CzGBlqCBkzCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNV
BAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMTL1N0YXJ0
Q29tIENsYXNzIDMgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBAgIAizANBgkqhkiG
9w0BAQEFAASCAQA7aYxu8vLCked5REwLUuKoy9rHaOU6ohtxHqAt82jAbwsPUtNyWpD5+bSD
szm4ofJNYWSDkE/B/HmqSSS2SEBVRiEVOnjMkd5YmGLW4/RviivMkTDFxsO4QqJHexDDpZJD
7UggrrKUey5JHCEOlTrhdGnOHyUeXg5Ey4riWIDYqL0HbQsV4T8m1WxLUSu2EUQ99EXTrIZd
RRhVb/iT8g7+iRaZj/Y2iYXvubhR9Tx8Ez9Fb8fpLVg8Md0ALwQcWNOKsU8JxNSHyOuzVEdI
wmJMHUVjZLMua11nQ9IATFi/wv8kuXhuoFCgQcHDoIheSu8l5aUlpawessfxm1SqQRXGAAAA
AAAA
--------------ms010506080102090306010301--

From housley@vigilsec.com  Wed Apr  6 10:28:05 2011
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9DEDB3A695F for <ietf@core3.amsl.com>; Wed,  6 Apr 2011 10:28:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.593
X-Spam-Level: 
X-Spam-Status: No, score=-102.593 tagged_above=-999 required=5 tests=[AWL=0.006, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3hwI5VpZXkJd for <ietf@core3.amsl.com>; Wed,  6 Apr 2011 10:28:05 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by core3.amsl.com (Postfix) with ESMTP id 1BF613A68AB for <ietf@ietf.org>; Wed,  6 Apr 2011 10:28:05 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 7C6FE9A47A3; Wed,  6 Apr 2011 13:30:01 -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 Z3+Pv9i81+i6; Wed,  6 Apr 2011 13:29:48 -0400 (EDT)
Received: from [192.168.2.100] (pool-71-178-218-117.washdc.fios.verizon.net [71.178.218.117]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 0E3779A4728; Wed,  6 Apr 2011 13:30:01 -0400 (EDT)
Subject: Re: draft-housley-two-maturity-levels-05
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <4D9C98A6.8000608@gmx.de>
Date: Wed, 6 Apr 2011 13:29:48 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <EA5F4FC8-20D4-404C-A1C4-B3964592F275@vigilsec.com>
References: <20110406152226.000AF3A6803@core3.amsl.com> <24582656-5993-46C3-B82A-883E8BA4E9A0@vigilsec.com> <4D9C98A6.8000608@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.1082)
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 17:28:05 -0000

Julian:

> A question...:
>=20
>>   A specification shall remain at the Proposed Standard maturity =
level
>>   for at least six (6) months before consideration for advancement to
>>   the Internet Standard maturity level.
>=20
> It would probably good to clarify when the six month period starts =
(IESG approval? RFC publication?).

This is not a new question.  It comes up every few years, and it was a =
big topic a few yers back when there was a long delay between approval =
and RFC publication.

The 6 months starts with RFC publication.

Russ=

From hartmans@mit.edu  Wed Apr  6 10:36:40 2011
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EF5D93A696B for <ietf@core3.amsl.com>; Wed,  6 Apr 2011 10:36:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.847
X-Spam-Level: 
X-Spam-Status: No, score=-102.847 tagged_above=-999 required=5 tests=[AWL=-0.582, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rEFnXwJXPj4l for <ietf@core3.amsl.com>; Wed,  6 Apr 2011 10:36:39 -0700 (PDT)
Received: from mail.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by core3.amsl.com (Postfix) with ESMTP id 766853A6957 for <ietf@ietf.org>; Wed,  6 Apr 2011 10:36:39 -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 1F84520265; Wed,  6 Apr 2011 13:35:08 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 7BB1F446E; Wed,  6 Apr 2011 13:38:22 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Russ Housley <housley@vigilsec.com>
Subject: Re: draft-housley-two-maturity-levels-05
References: <20110406152226.000AF3A6803@core3.amsl.com> <24582656-5993-46C3-B82A-883E8BA4E9A0@vigilsec.com> <4D9C98A6.8000608@gmx.de> <EA5F4FC8-20D4-404C-A1C4-B3964592F275@vigilsec.com>
Date: Wed, 06 Apr 2011 13:38:22 -0400
In-Reply-To: <EA5F4FC8-20D4-404C-A1C4-B3964592F275@vigilsec.com> (Russ Housley's message of "Wed, 6 Apr 2011 13:29:48 -0400")
Message-ID: <tslaag3e0vl.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: Julian Reschke <julian.reschke@gmx.de>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 17:36:40 -0000

>>>>> "Russ" == Russ Housley <housley@vigilsec.com> writes:


    Russ> The 6 months starts with RFC publication.

Please say that in the draft then.
I had a different take away from the last version of this discussion I
participated in.
I don't care much what the answer is, but it seems clear that it
requires documentation.

Apologies if it is already stated elsewhere in the draft: I have not
read 05 yet.

From housley@vigilsec.com  Wed Apr  6 10:48:47 2011
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0811C3A69D2 for <ietf@core3.amsl.com>; Wed,  6 Apr 2011 10:48:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.594
X-Spam-Level: 
X-Spam-Status: No, score=-102.594 tagged_above=-999 required=5 tests=[AWL=0.005, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AtQ78Hu7iQLR for <ietf@core3.amsl.com>; Wed,  6 Apr 2011 10:48:46 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by core3.amsl.com (Postfix) with ESMTP id 6EAEC3A69B9 for <ietf@ietf.org>; Wed,  6 Apr 2011 10:48:46 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id ABFEF9A4728; Wed,  6 Apr 2011 13:50: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 MiwqzP5RRv21; Wed,  6 Apr 2011 13:50:23 -0400 (EDT)
Received: from [192.168.2.100] (pool-71-178-218-117.washdc.fios.verizon.net [71.178.218.117]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 37C9D9A4732; Wed,  6 Apr 2011 13:50:55 -0400 (EDT)
Subject: Re: draft-housley-two-maturity-levels-05
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <tslaag3e0vl.fsf@mit.edu>
Date: Wed, 6 Apr 2011 13:50:29 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <1E22DD62-993B-4A7B-8221-CDE75B9DF122@vigilsec.com>
References: <20110406152226.000AF3A6803@core3.amsl.com> <24582656-5993-46C3-B82A-883E8BA4E9A0@vigilsec.com> <4D9C98A6.8000608@gmx.de> <EA5F4FC8-20D4-404C-A1C4-B3964592F275@vigilsec.com> <tslaag3e0vl.fsf@mit.edu>
To: Sam Hartman <hartmans-ietf@mit.edu>, Julian Reschke <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.1082)
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 17:48:47 -0000

Sam and Julian:

>>>>>> "Russ" == Russ Housley <housley@vigilsec.com> writes:
> 
> 
>    Russ> The 6 months starts with RFC publication.
> 
> Please say that in the draft then.
> I had a different take away from the last version of this discussion I
> participated in.
> I don't care much what the answer is, but it seems clear that it
> requires documentation.
> 
> Apologies if it is already stated elsewhere in the draft: I have not
> read 05 yet.

I will add a sentence in -06 to make this clear.

Russ

From brian.e.carpenter@gmail.com  Wed Apr  6 11:20:55 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5C3F228C11D for <ietf@core3.amsl.com>; Wed,  6 Apr 2011 11:20:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.567
X-Spam-Level: 
X-Spam-Status: No, score=-103.567 tagged_above=-999 required=5 tests=[AWL=0.032, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2kH+AzJ0kNvU for <ietf@core3.amsl.com>; Wed,  6 Apr 2011 11:20:54 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 87A6C28C120 for <ietf@ietf.org>; Wed,  6 Apr 2011 11:20:54 -0700 (PDT)
Received: by wyb29 with SMTP id 29so1716931wyb.31 for <ietf@ietf.org>; Wed, 06 Apr 2011 11:22:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=6SsnqbzU2zNq/trjzSPb1ZvHD/cv+edC9nR62AOdyi8=; b=BUEP/cJPv5J+K0/avA3XWEoh651KXbfbvSB4gCiBIz/XVonszw9OqdXWBCIyiZCkrl sFiYNPDeAcs3j09tHVq6JuZgPHe7D1IyzqfOTucem1Gnp7NbQLZiEn3tWTK+4rKY9i5q gQKy13YRZ2tjWMTnhWMGn6zL7i3N9AdBCo8t0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=quHSzWzQbiSOXDtNYfCitGnpShYi4GSiRNjVMHNyPjBQ37Xma6ZrZTfB7zfEwjQEix axmg4T9i4XoO4c+znCWJ5It2cmpDk4SUmIDBKFUQ23mMDZSy+iKVS6SwRebqP2q1nC6a d3MDYJPQUvbv0BfbcUUk/aRGRYDoRMwVVqobY=
Received: by 10.227.32.69 with SMTP id b5mr1412864wbd.99.1302114158060; Wed, 06 Apr 2011 11:22:38 -0700 (PDT)
Received: from [192.168.1.65] (host86-162-222-107.range86-162.btcentralplus.com [86.162.222.107]) by mx.google.com with ESMTPS id p5sm541820wbg.45.2011.04.06.11.22.36 (version=SSLv3 cipher=OTHER); Wed, 06 Apr 2011 11:22:37 -0700 (PDT)
Message-ID: <4D9CAF69.8070809@gmail.com>
Date: Thu, 07 Apr 2011 06:22:33 +1200
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: Russ Housley <housley@vigilsec.com>
Subject: Re: draft-housley-two-maturity-levels-05
References: <20110406152226.000AF3A6803@core3.amsl.com> <24582656-5993-46C3-B82A-883E8BA4E9A0@vigilsec.com>
In-Reply-To: <24582656-5993-46C3-B82A-883E8BA4E9A0@vigilsec.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 18:20:55 -0000

On 2011-04-07 03:27, Russ Housley wrote:
> This revision proposes a solution to the issue raised by Brian Carpenter about documents lingering at Draft Standard.  Some people thought it was a problem.  Others thought it did not matter.  The proposed solution leaves the matter in the hands of the IESG.

That seems like a fine approach; it allows common sense to be applied.

   Brian

From chair@ietf.org  Wed Apr  6 13:33:53 2011
Return-Path: <chair@ietf.org>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9252B3A69D4 for <ietf@core3.amsl.com>; Wed,  6 Apr 2011 13:33:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.849
X-Spam-Level: 
X-Spam-Status: No, score=-102.849 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kPuddr1NwpaS for <ietf@core3.amsl.com>; Wed,  6 Apr 2011 13:33:52 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [64.170.98.20]) by core3.amsl.com (Postfix) with ESMTP id A6ACF3A69C8 for <ietf@ietf.org>; Wed,  6 Apr 2011 13:33:52 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c1a.amsl.com (Postfix) with ESMTP id 1B3D6E08D2 for <ietf@ietf.org>; Wed,  6 Apr 2011 13:35:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c1a.amsl.com ([127.0.0.1]) by localhost (c1a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EGbcD5FlEzna for <ietf@ietf.org>; Wed,  6 Apr 2011 13:35:13 -0700 (PDT)
Received: from [192.168.2.101] (pool-71-178-218-117.washdc.fios.verizon.net [71.178.218.117]) by c1a.amsl.com (Postfix) with ESMTPSA id CED79E0851 for <ietf@ietf.org>; Wed,  6 Apr 2011 13:35:12 -0700 (PDT)
From: IETF Chair <chair@ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Admin Plenary Minutes
Date: Wed, 6 Apr 2011 16:35:34 -0400
Message-Id: <6FF7E036-A8B4-4639-97A8-5D5E20FC66E3@ietf.org>
To: IETF <ietf@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1082)
X-Mailer: Apple Mail (2.1082)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 20:33:53 -0000

http://www.ietf.org/proceedings/80/minutes/plenaryw.txt

The Admin Plenary minutes are now available for review.  Please let me =
know if there are any changes needed,

Many thanks to Mirjam Kuehne for her help generating this minutes.

Russ=

From evnikita2@gmail.com  Thu Apr  7 07:07:30 2011
Return-Path: <evnikita2@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CCC323A692A for <ietf@core3.amsl.com>; Thu,  7 Apr 2011 07:07:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.495
X-Spam-Level: 
X-Spam-Status: No, score=-3.495 tagged_above=-999 required=5 tests=[AWL=0.104,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PaieYhxG6GOr for <ietf@core3.amsl.com>; Thu,  7 Apr 2011 07:07:30 -0700 (PDT)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by core3.amsl.com (Postfix) with ESMTP id AEF8A3A68C4 for <ietf@ietf.org>; Thu,  7 Apr 2011 07:07:29 -0700 (PDT)
Received: by bwz13 with SMTP id 13so2314051bwz.31 for <ietf@ietf.org>; Thu, 07 Apr 2011 07:09:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=4zSNZdAUM0E6jm2SAn7+qmDdEvkhFjlnTm2qkqP35A0=; b=HLAvnIjPey4B3JvrLrSbRtPryeJ+8EmEMIcUhnybhw18aAaWMmQTGOqR+VDd+W9DeN yApefz8+FdU1UaKK1AZjuVuJvpjmfH9INAjUoI6dUBJpFIQCUij1wHEj7iNn92fqPOva PBJooj0qjqFGKpEFAWQ1GFIXg8+TeqCPQrnR0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=VneVqLLrNY/RThEoZ3ldArgg38VohnBYLRmkTQ+z9jNgQaPY7J2LYLtdLXD8yKpUK/ kUPhvWm7SrnKUcHhhJcpDkJZvnHOAcgjEAsAlJn5U0PN6EAhLiYsmh8XiWSZS/VJ2oBY dIbx0IBxp2GjlDqwSfLPjE7gXeVshuKrJJHaQ=
Received: by 10.204.19.74 with SMTP id z10mr838664bka.183.1302185352599; Thu, 07 Apr 2011 07:09:12 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id w3sm1096446bkt.17.2011.04.07.07.09.10 (version=SSLv3 cipher=OTHER); Thu, 07 Apr 2011 07:09:11 -0700 (PDT)
Message-ID: <4D9DC5AB.2040604@gmail.com>
Date: Thu, 07 Apr 2011 17:09:47 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
Subject: Re: draft-housley-two-maturity-levels-05
References: <20110406152226.000AF3A6803@core3.amsl.com> <24582656-5993-46C3-B82A-883E8BA4E9A0@vigilsec.com>
In-Reply-To: <24582656-5993-46C3-B82A-883E8BA4E9A0@vigilsec.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 14:07:30 -0000

06.04.2011 18:27, Russ Housley wrote:
> This revision proposes a solution to the issue raised by Brian Carpenter about documents lingering at Draft Standard.  Some people thought it was a problem.  Others thought it did not matter.  The proposed solution leaves the matter in the hands of the IESG.
I can hardly see my comments from 18 March 
(http://www.ietf.org/mail-archive/web/ietf/current/msg65911.html) 
considered in -05.  Are you planning to make any changes regarding this 
in -06?

Mykyta Yevstifeyev
> Russ
>
>
> Begin forwarded message:
>
>> From: IETF I-D Submission Tool<idsubmission@ietf.org>
>> Date: April 6, 2011 11:22:25 AM EDT
>> To: housley@vigilsec.com
>> Cc: dcrocker@bbiw.net, eburger@standardstrack.com
>> Subject: New Version Notification for draft-housley-two-maturity-levels-05
>>
>>
>> A new version of I-D, draft-housley-two-maturity-levels-05.txt has been successfully submitted by Russ Housley and posted to the IETF repository.
>>
>> Filename:	 draft-housley-two-maturity-levels
>> Revision:	 05
>> Title:		 Reducing the Standards Track to Two Maturity Levels
>> Creation_date:	 2011-04-06
>> WG ID:		 Independent Submission
>> Number_of_pages: 7
>>
>> Abstract:
>> This document proposes several changes to the Internet Engineering
>> Task Force (IETF) Standards Process defined in RFC 2026, primarily a
>> reduction from three IETF standards track maturity levels to two.
>>
>> {{ RFC Editor: please change "proposes several changes to the" to
>> "changes the". }}
>>
>>
>>
>> The IETF Secretariat.
>>
>>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>


From housley@vigilsec.com  Thu Apr  7 11:53:54 2011
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F353B3A696E for <ietf@core3.amsl.com>; Thu,  7 Apr 2011 11:53:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.596
X-Spam-Level: 
X-Spam-Status: No, score=-102.596 tagged_above=-999 required=5 tests=[AWL=0.003, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CNjXsfCsUHNy for <ietf@core3.amsl.com>; Thu,  7 Apr 2011 11:53:53 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by core3.amsl.com (Postfix) with ESMTP id 1537F3A696D for <ietf@ietf.org>; Thu,  7 Apr 2011 11:53:53 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 10C5D9A4737; Thu,  7 Apr 2011 14:56:04 -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 5QOxraZ0DGJM; Thu,  7 Apr 2011 14:55:29 -0400 (EDT)
Received: from [192.168.2.100] (pool-71-178-218-117.washdc.fios.verizon.net [71.178.218.117]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 512649A4730; Thu,  7 Apr 2011 14:56:03 -0400 (EDT)
Subject: Re: draft-housley-two-maturity-levels-05
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <4D9DC5AB.2040604@gmail.com>
Date: Thu, 7 Apr 2011 14:55:36 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <710968D5-A9F2-4F11-8B41-63439FA8BDF5@vigilsec.com>
References: <20110406152226.000AF3A6803@core3.amsl.com> <24582656-5993-46C3-B82A-883E8BA4E9A0@vigilsec.com> <4D9DC5AB.2040604@gmail.com>
To: Mykyta Yevstifeyev <evnikita2@gmail.com>
X-Mailer: Apple Mail (2.1082)
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 18:53:54 -0000

Mykyta:

If this approach is acceptable to the community, implementation reports =
will no longer be needed at all.

Russ


On Apr 7, 2011, at 10:09 AM, Mykyta Yevstifeyev wrote:

> 06.04.2011 18:27, Russ Housley wrote:
>> This revision proposes a solution to the issue raised by Brian =
Carpenter about documents lingering at Draft Standard.  Some people =
thought it was a problem.  Others thought it did not matter.  The =
proposed solution leaves the matter in the hands of the IESG.
> I can hardly see my comments from 18 March =
(http://www.ietf.org/mail-archive/web/ietf/current/msg65911.html) =
considered in -05.  Are you planning to make any changes regarding this =
in -06?
>=20
> Mykyta Yevstifeyev
>> Russ
>>=20
>>=20
>> Begin forwarded message:
>>=20
>>> From: IETF I-D Submission Tool<idsubmission@ietf.org>
>>> Date: April 6, 2011 11:22:25 AM EDT
>>> To: housley@vigilsec.com
>>> Cc: dcrocker@bbiw.net, eburger@standardstrack.com
>>> Subject: New Version Notification for =
draft-housley-two-maturity-levels-05
>>>=20
>>>=20
>>> A new version of I-D, draft-housley-two-maturity-levels-05.txt has =
been successfully submitted by Russ Housley and posted to the IETF =
repository.
>>>=20
>>> Filename:	 draft-housley-two-maturity-levels
>>> Revision:	 05
>>> Title:		 Reducing the Standards Track to Two Maturity =
Levels
>>> Creation_date:	 2011-04-06
>>> WG ID:		 Independent Submission
>>> Number_of_pages: 7
>>>=20
>>> Abstract:
>>> This document proposes several changes to the Internet Engineering
>>> Task Force (IETF) Standards Process defined in RFC 2026, primarily a
>>> reduction from three IETF standards track maturity levels to two.
>>>=20
>>> {{ RFC Editor: please change "proposes several changes to the" to
>>> "changes the". }}
>>>=20
>>>=20
>>>=20
>>> The IETF Secretariat.
>>>=20
>>>=20
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>>=20
>=20


From narten@us.ibm.com  Thu Apr  7 21:51:29 2011
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 102EF3A6869 for <ietf@core3.amsl.com>; Thu,  7 Apr 2011 21:51:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.388
X-Spam-Level: 
X-Spam-Status: No, score=-106.388 tagged_above=-999 required=5 tests=[AWL=0.211, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SNudwL1M40EH for <ietf@core3.amsl.com>; Thu,  7 Apr 2011 21:51:28 -0700 (PDT)
Received: from e38.co.us.ibm.com (e38.co.us.ibm.com [32.97.110.159]) by core3.amsl.com (Postfix) with ESMTP id 56AED3A67E6 for <ietf@ietf.org>; Thu,  7 Apr 2011 21:51:28 -0700 (PDT)
Received: from d03relay03.boulder.ibm.com (d03relay03.boulder.ibm.com [9.17.195.228]) by e38.co.us.ibm.com (8.14.4/8.13.1) with ESMTP id p384bXFM004378 for <ietf@ietf.org>; Thu, 7 Apr 2011 22:37:33 -0600
Received: from d03av05.boulder.ibm.com (d03av05.boulder.ibm.com [9.17.195.85]) by d03relay03.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p384r6IU106602 for <ietf@ietf.org>; Thu, 7 Apr 2011 22:53:06 -0600
Received: from d03av05.boulder.ibm.com (loopback [127.0.0.1]) by d03av05.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id p384r58c018289 for <ietf@ietf.org>; Thu, 7 Apr 2011 22:53:05 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.151.17]) by d03av05.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id p384r5HJ018223 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 7 Apr 2011 22:53:05 -0600
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id p384r2e1000325 for <ietf@ietf.org>; Fri, 8 Apr 2011 00:53:02 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.4/8.14.4/Submit) id p384r2MD032752 for ietf@ietf.org; Fri, 8 Apr 2011 00:53:02 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201104080453.p384r2MD032752@rotala.raleigh.ibm.com>
Date: Fri, 08 Apr 2011 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-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 04:51:29 -0000

Total of 37 messages in the last 7 days.
 
script run at: Fri Apr  8 00:53:02 EDT 2011
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 13.51% |    5 | 10.76% |    25057 | housley@vigilsec.com
  8.11% |    3 |  7.90% |    18406 | bob.hinden@gmail.com
  5.41% |    2 |  8.81% |    20524 | turchanyi.geza@gmail.com
  5.41% |    2 |  5.80% |    13500 | evnikita2@gmail.com
  5.41% |    2 |  4.78% |    11133 | johnl@iecc.com
  5.41% |    2 |  4.64% |    10804 | brian.e.carpenter@gmail.com
  2.70% |    1 |  5.93% |    13813 | stpeter@stpeter.im
  2.70% |    1 |  4.92% |    11461 | jaibuduvin@gmail.com
  2.70% |    1 |  4.38% |    10199 | olaf@nlnetlabs.nl
  2.70% |    1 |  4.34% |    10121 | balaji.1manarmy@gmail.com
  2.70% |    1 |  3.76% |     8749 | narten@us.ibm.com
  2.70% |    1 |  2.69% |     6272 | vesely@tana.it
  2.70% |    1 |  2.68% |     6253 | fred@cisco.com
  2.70% |    1 |  2.63% |     6123 | touch@isi.edu
  2.70% |    1 |  2.61% |     6083 | randy_presuhn@mindspring.com
  2.70% |    1 |  2.35% |     5467 | fluffy@cisco.com
  2.70% |    1 |  2.28% |     5312 | lear@cisco.com
  2.70% |    1 |  2.14% |     4975 | rja.lists@gmail.com
  2.70% |    1 |  2.06% |     4793 | dhc2@dcrocker.net
  2.70% |    1 |  1.99% |     4639 | bernard_aboba@hotmail.com
  2.70% |    1 |  1.92% |     4475 | jmamodio@gmail.com
  2.70% |    1 |  1.92% |     4468 | julian.reschke@gmx.de
  2.70% |    1 |  1.91% |     4455 | hartmans-ietf@mit.edu
  2.70% |    1 |  1.81% |     4218 | mail@sabahattin-gucukoglu.com
  2.70% |    1 |  1.77% |     4120 | john-ietf@jck.com
  2.70% |    1 |  1.71% |     3985 | chair@ietf.org
  2.70% |    1 |  1.52% |     3543 | jnc@mercury.lcs.mit.edu
--------+------+--------+----------+------------------------
100.00% |   37 |100.00% |   232948 | Total

From evnikita2@gmail.com  Thu Apr  7 23:29:12 2011
Return-Path: <evnikita2@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4DA123A690B for <ietf@core3.amsl.com>; Thu,  7 Apr 2011 23:29:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.234
X-Spam-Level: 
X-Spam-Status: No, score=-3.234 tagged_above=-999 required=5 tests=[AWL=0.365,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WlRQeIPyqd3r for <ietf@core3.amsl.com>; Thu,  7 Apr 2011 23:29:11 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by core3.amsl.com (Postfix) with ESMTP id 5F3D63A6892 for <ietf@ietf.org>; Thu,  7 Apr 2011 23:29:11 -0700 (PDT)
Received: by yxk30 with SMTP id 30so1569429yxk.31 for <ietf@ietf.org>; Thu, 07 Apr 2011 23:30:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=fRZilKsJPjiobSgrZWJb85Um84kVfQ/gYoH5kkZUGS0=; b=R/zXfjmvGoNf1Ll5q4SXBtryjOa6qvM/UNhWewrjkHdeq1W95kTFKdPS+UpD05ztnT 7sbe3YLpRfSSdPIP0j0QX96as5dwEtNUKFwoJuJKUAlDAh+QvNZnRa7v+36EmE22WdZP Nm+dHkjweZpZ8GXRzUFztnDAnNPJm7W3NQ1to=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=i7JHttDXHPTdvXNQ1v92Wc+EKvEn/6KVLTjOekOPgcU86lRaQ8UO5ZWFd6jeCcYC68 6bOvdntrOIEUK3F31PdvyC0Nr1cRctw6bskYILdm/pTEMGZ81YFfFBG0ehYj7Po+XcnB bjrDAN9tnApWqXxuZE0gRqO7hZaCZgkopJ//A=
MIME-Version: 1.0
Received: by 10.151.63.3 with SMTP id q3mr1528988ybk.443.1302244256092; Thu, 07 Apr 2011 23:30:56 -0700 (PDT)
Received: by 10.150.198.17 with HTTP; Thu, 7 Apr 2011 23:30:55 -0700 (PDT)
In-Reply-To: <710968D5-A9F2-4F11-8B41-63439FA8BDF5@vigilsec.com>
References: <20110406152226.000AF3A6803@core3.amsl.com> <24582656-5993-46C3-B82A-883E8BA4E9A0@vigilsec.com> <4D9DC5AB.2040604@gmail.com> <710968D5-A9F2-4F11-8B41-63439FA8BDF5@vigilsec.com>
Date: Fri, 8 Apr 2011 09:30:55 +0300
Message-ID: <BANLkTiksL5KKcBD0UOvhC2p5Rsqa8G=BcA@mail.gmail.com>
Subject: Re: draft-housley-two-maturity-levels-05
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
To: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 06:29:12 -0000

2011/4/7, Russ Housley <housley@vigilsec.com>:
> Mykyta:
>
> If this approach is acceptable to the community, implementation reports will
> no longer be needed at all.
>
In this case your document should obsolete RFC 5657 and mention this.

Mykyta
>
> Russ
>
>
> On Apr 7, 2011, at 10:09 AM, Mykyta Yevstifeyev wrote:
>
>> 06.04.2011 18:27, Russ Housley wrote:
>>> This revision proposes a solution to the issue raised by Brian Carpenter
>>> about documents lingering at Draft Standard.  Some people thought it was
>>> a problem.  Others thought it did not matter.  The proposed solution
>>> leaves the matter in the hands of the IESG.
>> I can hardly see my comments from 18 March
>> (http://www.ietf.org/mail-archive/web/ietf/current/msg65911.html)
>> considered in -05.  Are you planning to make any changes regarding this in
>> -06?
>>
>> Mykyta Yevstifeyev
>>> Russ
>>>
>>>
>>> Begin forwarded message:
>>>
>>>> From: IETF I-D Submission Tool<idsubmission@ietf.org>
>>>> Date: April 6, 2011 11:22:25 AM EDT
>>>> To: housley@vigilsec.com
>>>> Cc: dcrocker@bbiw.net, eburger@standardstrack.com
>>>> Subject: New Version Notification for
>>>> draft-housley-two-maturity-levels-05
>>>>
>>>>
>>>> A new version of I-D, draft-housley-two-maturity-levels-05.txt has been
>>>> successfully submitted by Russ Housley and posted to the IETF
>>>> repository.
>>>>
>>>> Filename:	 draft-housley-two-maturity-levels
>>>> Revision:	 05
>>>> Title:		 Reducing the Standards Track to Two Maturity Levels
>>>> Creation_date:	 2011-04-06
>>>> WG ID:		 Independent Submission
>>>> Number_of_pages: 7
>>>>
>>>> Abstract:
>>>> This document proposes several changes to the Internet Engineering
>>>> Task Force (IETF) Standards Process defined in RFC 2026, primarily a
>>>> reduction from three IETF standards track maturity levels to two.
>>>>
>>>> {{ RFC Editor: please change "proposes several changes to the" to
>>>> "changes the". }}
>>>>
>>>>
>>>>
>>>> The IETF Secretariat.
>>>>
>>>>
>>> _______________________________________________
>>> Ietf mailing list
>>> Ietf@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ietf
>>>
>>
>
>

From ron.even.tlv@gmail.com  Sat Apr  9 04:52:14 2011
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 19B683A6A91; Sat,  9 Apr 2011 04:52:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.34
X-Spam-Level: 
X-Spam-Status: No, score=-3.34 tagged_above=-999 required=5 tests=[AWL=0.260,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5e4AjfR6K7NQ; Sat,  9 Apr 2011 04:52:13 -0700 (PDT)
Received: from mail-ww0-f42.google.com (mail-ww0-f42.google.com [74.125.82.42]) by core3.amsl.com (Postfix) with ESMTP id B4B193A6A00; Sat,  9 Apr 2011 04:52:12 -0700 (PDT)
Received: by wwk4 with SMTP id 4so1307044wwk.1 for <multiple recipients>; Sat, 09 Apr 2011 04:53:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-type:content-transfer-encoding :x-mailer:thread-index:content-language; bh=N1aKEkRRqaprl1j1GsA8VzaOkK8XdSphp7LdAIwvIoc=; b=Z7ffDgkgbO7bCnFO1f9LL7mqRhJaRzXUoE0TjpgzQ/y5buPzL9TA2l76rMyAFRjW/R 8vhMGw7BvAPdcCovdBD6NEISqST0ATooluMIGBq6O3rRQtBOC0vBfQdj5GYmV+gzi5yU rcwhhPyfsnVMTwWhaOS88LNuTUhLhbyWI7iW4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:x-mailer :thread-index:content-language; b=ponUUUPA7vTKDPQbBHEzbSYcJIKl0F63zsDrZVGacubzL0D7S0utgQBL3HT+aAihEA pF7EWH16yII1I4oyRX1b4dTqZZxqoERIUKZnhThXE3nGLjkaBZOZ4yBbykEwkHEV24P8 srr56hYlQCMHdHTd5HnbmDpz3SPP+fjRvMhvk=
Received: by 10.216.81.69 with SMTP id l47mr732762wee.78.1302350037712; Sat, 09 Apr 2011 04:53:57 -0700 (PDT)
Received: from windows8d787f9 (bzq-79-179-29-234.red.bezeqint.net [79.179.29.234]) by mx.google.com with ESMTPS id t5sm1756841wes.33.2011.04.09.04.53.55 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 09 Apr 2011 04:53:56 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Paul Hoffman'" <paul.hoffman@vpnc.org>
References: <4d78dc6c.537c0e0a.3695.ffffb160@mx.google.com> <4D79A021.2020106@vpnc.org>
In-Reply-To: <4D79A021.2020106@vpnc.org>
Subject: RE: Gen-ART LC review of draft-ietf-genarea-datatracker-community-07
Date: Sat, 9 Apr 2011 14:53:19 +0300
Message-ID: <4da048d4.0504d90a.5dd9.ffffb191@mx.google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcvfoevcGXGG5phzRdSglDzaFnKmOwXCrGxw
Content-Language: en-us
Cc: gen-art@ietf.org, 'IETF-Discussion list' <ietf@ietf.org>, draft-ietf-genarea-datatracker-community.all@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 11:52:14 -0000

Hi,
I reviewed version 7  and all my comments were addressed.
Roni Even

> -----Original Message-----
> From: Paul Hoffman [mailto:paul.hoffman@vpnc.org]
> Sent: Friday, March 11, 2011 6:08 AM
> To: Roni Even
> Cc: draft-ietf-genarea-datatracker-community.all@tools.ietf.org; gen-
> art@ietf.org; 'IETF-Discussion list'
> Subject: Re: Gen-ART LC review of draft-ietf-genarea-datatracker-
> community-06
> 
> On 3/10/11 6:12 AM, Roni Even 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.
> 
> Thanks for the review. Everything on your list seemed fine, and will
> appear in the next draft.
> 
> --Paul Hoffman


From ron.even.tlv@gmail.com  Mon Apr 11 05:12:47 2011
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1206628C0EC; Mon, 11 Apr 2011 05:12:47 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VaXipqmARouR; Mon, 11 Apr 2011 05:12:44 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 23DC528C0F0; Mon, 11 Apr 2011 05:12:40 -0700 (PDT)
Received: by wwa36 with SMTP id 36so4536349wwa.13 for <multiple recipients>; Mon, 11 Apr 2011 05:12:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:to:cc:subject:date:message-id:mime-version :content-type:x-mailer:thread-index:content-language; bh=8dJBlsrHtl40KVpDncBTpvNhlm12++DczRD7vf3p6B8=; b=HlUU1UsYASmSsrFbH7BnN8ndLwd8EC25dIminfRRAdC+aa3gv+DNvBkD0k45GwJu6b q2bK1TLIUMFrN5FconuaIEjDxynO/b6DMDZHKFs/LW+U9U2oO5dXFn3jRTyrEg2PSMRU N8l8MF+XAC5MES73fQqg3VXTrAwsi+yu4hSz8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:subject:date:message-id:mime-version:content-type :x-mailer:thread-index:content-language; b=NQpDpQO+xv3Hzp1YP43QSuhV/9hQb8/Jnsx13Q3w0PIN2uLR8S+rDz/VCf/HEUGr86 08Vt2o0zJSIQ1ETs9AeWThKZ7bspNgD/8u2Gcot0T+LMdjAHDPbWHnXIaHcGCd/tafGW oQeyAqgtS5+uFVgJQgW/OD5JgdZd5Tn8pYlo0=
Received: by 10.216.168.67 with SMTP id j45mr2600327wel.101.1302523960677; Mon, 11 Apr 2011 05:12:40 -0700 (PDT)
Received: from windows8d787f9 (bzq-79-176-31-195.red.bezeqint.net [79.176.31.195]) by mx.google.com with ESMTPS id r57sm2624359wes.25.2011.04.11.05.12.37 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 11 Apr 2011 05:12:39 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-harkins-ipsecme-spsk-auth.all@tools.ietf.org>
Subject: Gen-ART LC review of draft-harkins-ipsecme-spsk-auth-03
Date: Mon, 11 Apr 2011 15:11:55 +0300
Message-ID: <4da2f037.cf03d90a.5d44.fffff941@mx.google.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_003D_01CBF85A.CDAC5740"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acv4QaPRVpsdKx61SZSFiZ0ojWfylg==
Content-Language: en-us
Cc: gen-art@ietf.org, 'IETF-Discussion list' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 12:12:47 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_003D_01CBF85A.CDAC5740
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-harkins-ipsecme-spsk-auth-03

Reviewer: Roni Even

Review Date:2011-4-11

IETF LC End Date: 2011-4-23

IESG Telechat date:

 

Summary: This draft is almost ready for publication as an Experimental RFC.

 

Major issues:

 

 

Minor issues:

 

1.	In section 8.5 and 8.6 the draft says that "If no more password
pre-processing techniques are supported the exchange MUST be   terminated."
Reading section 6, I thought that NONE MUST be supported for
interoperability purpose.
2.	In section 8.1 and in figure 1 and figure 2 is there a maximum value
for "counter"?

 

 

Nits/editorial comments:

 

1.       In section 1 just before 1.1 you have "suceed" instead of "succeed"

2.       In section 4 third bullet "an" instead of "and"

3.       In section 4.2 "Two elementx" instead of "Two elements"

4.       In section 5 second row "authenticaiton" should be "authentication"

5.       In section 6 fourth row "identitcal" instead of "identical"

 

 


------=_NextPart_000_003D_01CBF85A.CDAC5740
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:"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:785730766;
	mso-list-type:hybrid;
	mso-list-template-ids:-549430472 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;}
@list l1
	{mso-list-id:1268463154;
	mso-list-type:hybrid;
	mso-list-template-ids:-213336278 -460948864 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-bidi-font-family:Arial;}
@list l1:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1: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>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-harki=
ns-ipsecme-spsk-auth-03<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:2011&#8211;4&#8211;11<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: 2011&#8211;4&#8211;23<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 an </span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Experimenta=
l </span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>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"'><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"'><o:p>&nbsp;=
</o:p></span></p><ol style=3D'margin-top:0in' start=3D1 type=3D1><li =
class=3DMsoNormal style=3D'mso-list:l1 level1 lfo1'>In section 8.5 and =
8.6 the draft says that &#8220;If no more password pre-processing =
techniques are supported the exchange MUST be&nbsp;&nbsp; =
terminated.&#8221;&nbsp; Reading section 6, I thought that NONE MUST be =
supported for interoperability purpose.<o:p></o:p></li><li =
class=3DMsoNormal style=3D'mso-list:l1 level1 lfo1'>In section 8.1 and =
in figure 1 and figure 2 is there a maximum value for =
&#8220;counter&#8221;?<o:p></o:p></li></ol><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 =
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 =
1 just before 1.1 you have &#8220;suceed&#8221; instead of =
&#8220;succeed&#8221;<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'>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 =
4 third bullet &#8220;an&#8221; instead of =
&#8220;and&#8221;<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'>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 section =
4.2 &#8220;Two elementx&#8221; instead of &#8220;Two =
elements&#8221;<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'>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"'>In section =
5 second row &#8220;authenticaiton&#8221; should be =
&#8220;authentication&#8221;<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'>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 =
6 fourth row &#8220;identitcal&#8221; instead of =
&#8220;identical&#8221;<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=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_003D_01CBF85A.CDAC5740--


From mail@sabahattin-gucukoglu.com  Mon Apr 11 15:18:52 2011
Return-Path: <mail@sabahattin-gucukoglu.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id C0E3EE068D for <ietf@ietfc.amsl.com>; Mon, 11 Apr 2011 15:18:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.451
X-Spam-Level: **
X-Spam-Status: No, score=2.451 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, HOST_EQ_MODEMCABLE=1.368, HOST_MISMATCH_COM=0.311, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RDNS_DYNAMIC=0.1]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1HI1xMQIocOL for <ietf@ietfc.amsl.com>; Mon, 11 Apr 2011 15:18:48 -0700 (PDT)
Received: from Mintaka.sabahattin-gucukoglu.com (sgucukoglu-2-pt.tunnel.tserv8.dal1.ipv6.he.net [IPv6:2001:470:1f0e:7ef::2]) by ietfc.amsl.com (Postfix) with ESMTP id F0AD4E066B for <ietf@ietf.org>; Mon, 11 Apr 2011 15:18:46 -0700 (PDT)
Received: from Mintaka.sabahattin-gucukoglu.com ([::ffff:127.0.0.1]:45338) by Mintaka.sabahattin-gucukoglu.com with [XMail 1.27 ESMTP Server] id <S32691> for <ietf@ietf.org> from <mail@sabahattin-gucukoglu.com>; Mon, 11 Apr 2011 21:41:51 +0100
Received: from [192.168.1.3] (cpc2-dals7-0-0-cust570.hari.cable.virginmedia.com [82.35.114.59]) (using SMTP over TLS) by Mintaka (tmda-ofmipd) with ESMTP; Mon, 11 Apr 2011 21:41:49 +0100
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Adventures in IPv6
Date: Mon, 11 Apr 2011 21:41:48 +0100
Message-Id: <725F5094-D5D6-4731-B0EE-9ABD99752317@sabahattin-gucukoglu.com>
To: ietf@ietf.org
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
X-Delivery-Agent: TMDA/1.1.12-kg3 (Haumea)
From: Sabahattin Gucukoglu <mail@sabahattin-gucukoglu.com>
X-Primary-Address: mail@sabahattin-gucukoglu.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Sabahattin Gucukoglu <mail-dated-1305146510.84e3c2@sabahattin-gucukoglu.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 Apr 2011 22:18:52 -0000

This is just a blog posting, but I think it has valid illustrative =
points of the general frustration in it:
http://bens.me.uk/2011/adventures-in-ipv6

Of course, I think the conclusion is basically wrong, *not* doing IPv6 =
is much worse than breaking the finger-pointing circle, and making it =
work by whatever means necessary.  We won't make the situation better by =
not doing anything.  And yes, I know how tired this all is, but it's =
starting to look like some people in this world just aren't going to be =
convinced until there's an actual, real crisis on top of us.

Cheers,
Sabahattin

From ben@estacado.net  Mon Apr 11 15:22:37 2011
Return-Path: <ben@estacado.net>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 3FF32E068E; Mon, 11 Apr 2011 15:22:37 -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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QKmfvnfN+oEu; Mon, 11 Apr 2011 15:22:34 -0700 (PDT)
Received: from estacado.net (estacado-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:266::2]) by ietfc.amsl.com (Postfix) with ESMTP id AE813E0679; Mon, 11 Apr 2011 15:22:18 -0700 (PDT)
Received: from dn3-227.estacado.net (dn3-227.estacado.net [172.16.3.227]) (authenticated bits=0) by estacado.net (8.14.3/8.14.2) with ESMTP id p3BKuMix038953 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 11 Apr 2011 15:56:23 -0500 (CDT) (envelope-from ben@estacado.net)
From: Ben Campbell <ben@estacado.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Gen-ART LC review of draft-ietf-kitten-digest-to-historic-03
Date: Mon, 11 Apr 2011 15:56:23 -0500
Message-Id: <802CB0FD-9C90-421A-98D2-F1E2F2D644B7@estacado.net>
To: draft-ietf-kitten-digest-to-historic.all@tools.ietf.org
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Cc: General Area 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: Mon, 11 Apr 2011 22:22:37 -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-kitten-digest-to-historic-03
Reviewer: Ben Campbell
Review Date: 2011-04-11
IETF LC End Date: 2011-04-15

Summary: This draft is essentially ready for publication as an =
informational RFC. I have a couple of editorial comments that should be =
considered prior to final publication.

Major issues: None

Minor issues: None

Nits/editorial comments:

-- Note following abstract:

Will this note stay in the RFC? The note makes me unsure whether the =
resulting RFC is intended to actually execute the deprecation, recommend =
deprecation, or start a discussion about deprecation. I assume from the =
IANA section, you intend the first.-

-- Section 1, 7B. "Lack of hash agility."

Can you elaborate on what this means? (I think I know, but I don't know =
if it will be obvious to all readers)



From glen@amsl.com  Mon Apr 11 15:45:20 2011
Return-Path: <glen@amsl.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 4C860E06DB for <ietf@ietfc.amsl.com>; Mon, 11 Apr 2011 15:45: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=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8XQLQF3r-1vA for <ietf@ietfc.amsl.com>; Mon, 11 Apr 2011 15:45:19 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [64.170.98.20]) by ietfc.amsl.com (Postfix) with ESMTP id 7BC10E0675 for <ietf@ietf.org>; Mon, 11 Apr 2011 15:45:19 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c1a.amsl.com (Postfix) with ESMTP id 32F4BE08D4 for <ietf@ietf.org>; Mon, 11 Apr 2011 15:45:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c1a.amsl.com ([127.0.0.1]) by localhost (c1a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wCA8P-niY6zD for <ietf@ietf.org>; Mon, 11 Apr 2011 15:45:19 -0700 (PDT)
Received: from [192.168.1.198] (173-8-133-92-SFBA.hfc.comcastbusiness.net [173.8.133.92]) by c1a.amsl.com (Postfix) with ESMTPSA id 11CDDE08CA for <ietf@ietf.org>; Mon, 11 Apr 2011 15:45:19 -0700 (PDT)
From: Glen Barney <glen@amsl.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Test, please ignore
Date: Mon, 11 Apr 2011 15:45:18 -0700
Message-Id: <FEFED824-AECB-417A-AE9C-0028FFA2580F@amsl.com>
To: 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: Mon, 11 Apr 2011 22:45:20 -0000

Test, please ignore.

Glen
Glen Barney
IT Director
AMS (IETF Secretariat)


From tglassey@earthlink.net  Mon Apr 11 15:47:02 2011
Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 5B33AE06DB for <ietf@ietfc.amsl.com>; Mon, 11 Apr 2011 15:47:02 -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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mTQComrrz3f4 for <ietf@ietfc.amsl.com>; Mon, 11 Apr 2011 15:47:01 -0700 (PDT)
Received: from elasmtp-scoter.atl.sa.earthlink.net (elasmtp-scoter.atl.sa.earthlink.net [209.86.89.67]) by ietfc.amsl.com (Postfix) with ESMTP id 4BB80E066A for <ietf@ietf.org>; Mon, 11 Apr 2011 15:47:01 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=m5DX+36xRak73aEpoq/0gN0YxB9/8Z9Q4qrT4VlmxbVZ+lFceWfYSi1SFN1eUTz1; 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 [207.111.209.5] (helo=[192.168.1.102]) by elasmtp-scoter.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1Q9O9P-0005Dm-Gf for ietf@ietf.org; Mon, 11 Apr 2011 16:55:59 -0400
Message-ID: <4DA36AEB.5010600@earthlink.net>
Date: Mon, 11 Apr 2011 13:56:11 -0700
From: todd glassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Call for a Jasmine Revolution in the IETF: Privacy, Integrity, Obscurity
References: <69C307E5-8B96-4604-960B-3270B8D01D8D@softarmor.com>	<4CA7D36B-B8DE-431F-AEEB-57675B6951AD@mnot.net>	<877B733B-F1CB-4087-BE82-0A1B07623D24@softarmor.com>	<DEC3D7BB-0EDE-4584-B5A0-35C6F54CD2CC@mnot.net>	<D44303D5-288B-4A44-BD07-8D5A3059BE45@softarmor.com>	<4D88BEE2.90504@tana.it>	<6.2.5.6.2.20110322211644.0db72cf8@resistor.net> <D85C5068-0F54-40D3-9A94-058C07894CFB@gmx.net>
In-Reply-To: <D85C5068-0F54-40D3-9A94-058C07894CFB@gmx.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec79e7f1e980041c5c91fa13cc7bb33fb404350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 207.111.209.5
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 22:47:02 -0000

On 3/23/2011 12:02 AM, Hannes Tschofenig wrote:
> On Mar 23, 2011, at 6:52 AM, SM wrote:
>
>> The IETF can only address the technical problems.
> This is an argument I often hear. I do, however, believe that you cannot see technology in isolation.
Yeah - sure you can... if you want to be totally about the original 
design and practice of the IETF and its vision. It was built to advance 
protocol standardization and not to decide what protocols it would allow 
on the Internet and which it wouldn't.  But  lately many have forgotten 
this and are using the IETF as a formal lobby for technological policy 
advancement and that's a no-no.

Bluntly the IETF members are becoming more and more aggressively 
politically and this statement is based on IAB and other publication on 
what the IETF does and does not allow through its frameworks. In doing 
so their statements about allowing protocols or not allowing protocols 
to be standardized based on their stated perception of "what damages the 
Internet" or what they personally want to see as a "free access to all 
information and ideas" model, creates a real serious divergence from the 
Standards Practice this organization was set up as, and IMHO is one 
which is designed clearly to destroy global Intellectual Property law 
and practice.
> However, in many cases the technology, regulatory environment, business aspects, and the social context gets mixed together.
No Hannes  - it doesn't unless the Chair allows it to - meaning that the 
Chair in this instance has allowed political materials to be fielded 
(filed in this instance) into the IETF and trust me I am already filing 
a formal complaint with the Treasury about ISOC's becoming a formal PAC 
and its locking out protocol efforts based on its own desires therein...

http://tools.ietf.org/html/draft-morris-policy-cons-00


I suggest that the Chair immediately post a formal statement that the 
IETF is a-political and will not do anything but standardize 
technology.  Also that ONLY technology drafts can be accepted since the 
IETF is part of ISOC and not registered as a political PAC or Lobbying 
Agency which it clearly has become in direct violation of the NTIA MOU 
which gave it (ISOC and its ARIN) the real power.


Todd Glassey
Please have a look at: 
http://tools.ietf.org/html/draft-morris-policy-cons-00
> Ciao
> Hannes

Hannes - this is the issue with the IETF and the gross number of flaming 
idiots inside of it. The IETF is not a Social Reform Agency, nor is it a 
freaking political action group since its financial filings prevent this.

Todd Glassey
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>


From dougb@dougbarton.us  Mon Apr 11 16:39:54 2011
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 1EF9CE066B for <ietf@ietfc.amsl.com>; Mon, 11 Apr 2011 16: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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MPK+EurW6fwI for <ietf@ietfc.amsl.com>; Mon, 11 Apr 2011 16:39:50 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfc.amsl.com (Postfix) with ESMTP id 9C679E0613 for <ietf@ietf.org>; Mon, 11 Apr 2011 16:39:50 -0700 (PDT)
Received: (qmail 32757 invoked by uid 399); 11 Apr 2011 23:39:47 -0000
Received: from unknown (HELO 65-241-43-5.globalsuite.net) (dougb@dougbarton.us@65.241.43.5) by mail2.fluidhosting.com with ESMTPAM; 11 Apr 2011 23:39:47 -0000
X-Originating-IP: 65.241.43.5
X-Sender: dougb@dougbarton.us
Message-ID: <4DA3913B.1030902@dougbarton.us>
Date: Mon, 11 Apr 2011 16:39:39 -0700
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110319 Thunderbird/3.1.9
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Adventures in IPv6
References: <725F5094-D5D6-4731-B0EE-9ABD99752317@sabahattin-gucukoglu.com>
In-Reply-To: <725F5094-D5D6-4731-B0EE-9ABD99752317@sabahattin-gucukoglu.com>
X-Enigmail-Version: 1.1.2
OpenPGP: id=1A1ABC84
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, 11 Apr 2011 23:39:54 -0000

On 04/11/2011 13:41, Sabahattin Gucukoglu wrote:
> This is just a blog posting, but I think it has valid illustrative
> points of the general frustration in it:
> http://bens.me.uk/2011/adventures-in-ipv6
>
> Of course, I think the conclusion is basically wrong, *not* doing
> IPv6 is much worse than breaking the finger-pointing circle, and
> making it work by whatever means necessary.

"Much worse" for who? Just because we (may) believe that IPv6 is the way 
forward doesn't mean that the providers or consumers of Internet 
services will agree with us. The consumers just want to watch their 
videos and read their mail. The providers just want to sell them that 
capability. IPv6 needs to solve more problems than it creates, or else 
it's not the right answer.


Doug

-- 

	Nothin' ever doesn't change, but nothin' changes much.
			-- OK Go

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)  http://SupersetSolutions.com/


From mohta@necom830.hpcl.titech.ac.jp  Mon Apr 11 18:11:58 2011
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 49199E069F for <ietf@ietfc.amsl.com>; Mon, 11 Apr 2011 18:11:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.996
X-Spam-Level: 
X-Spam-Status: No, score=0.996 tagged_above=-999 required=5 tests=[AWL=1.086,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 14dJLD7XCkXM for <ietf@ietfc.amsl.com>; Mon, 11 Apr 2011 18:11:57 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfc.amsl.com (Postfix) with SMTP id 45020E0694 for <ietf@ietf.org>; Mon, 11 Apr 2011 18:11:57 -0700 (PDT)
Received: (qmail 98501 invoked from network); 12 Apr 2011 01:38:09 -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; 12 Apr 2011 01:38:09 -0000
Message-ID: <4DA3A6A0.6040607@necom830.hpcl.titech.ac.jp>
Date: Tue, 12 Apr 2011 10:10:56 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Adventures in IPv6
References: <725F5094-D5D6-4731-B0EE-9ABD99752317@sabahattin-gucukoglu.com>
In-Reply-To: <725F5094-D5D6-4731-B0EE-9ABD99752317@sabahattin-gucukoglu.com>
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, 12 Apr 2011 01:11:58 -0000

Sabahattin Gucukoglu wrote:

> Of course, I think the conclusion is basically wrong, *not* doing
> IPv6 is much worse than breaking the finger-pointing circle,
> and making it work by whatever means necessary.

The problem is that, operationally, IPv6 does not work.

> We won't make the situation better by not doing anything.

Insisting on IPv6 is worse than not doing anything, because
it gives people insisting on IPv6 false feeling of doing
something.

> And yes, I know how tired this all is, but it's starting to
> look like some people in this world just aren't going to be
> convinced until there's an actual, real crisis on top of us.

That's so true for you and other people insisting on IPv6.

						Masataka Ohta

From Even.roni@huawei.com  Sun Apr 10 01:39:51 2011
Return-Path: <Even.roni@huawei.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C2B373A69EF; Sun, 10 Apr 2011 01:39:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.494
X-Spam-Level: 
X-Spam-Status: No, score=-100.494 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  HTML_MESSAGE=0.001, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7OwiIfqB0o1R; Sun, 10 Apr 2011 01:39:48 -0700 (PDT)
Received: from szxga01-in.huawei.com (unknown [119.145.14.64]) by core3.amsl.com (Postfix) with ESMTP id 015C33A684D; Sun, 10 Apr 2011 01:39:48 -0700 (PDT)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LJF009T1HGZAO@szxga05-in.huawei.com>; Sun, 10 Apr 2011 16:41:24 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LJF00A0NHGZ4Z@szxga05-in.huawei.com>; Sun, 10 Apr 2011 16:41:23 +0800 (CST)
Received: from windows8d787f9 (bzq-79-176-31-195.red.bezeqint.net [79.176.31.195]) by szxml12-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LJF00KNUHGS9V@szxml12-in.huawei.com>; Sun, 10 Apr 2011 16:41:23 +0800 (CST)
Date: Sun, 10 Apr 2011 11:40:36 +0300
From: Roni Even <Even.roni@huawei.com>
Subject: GEn-ART last call review of draft-ietf-softwire-dual-stack-lite-07
To: draft-ietf-softwire-dual-stack-lite.all@tools.ietf.org
Message-id: <032a01cbf75a$fad3e860$f07bb920$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: multipart/alternative; boundary="Boundary_(ID_Axi3DX8ApWhu6F2FBOuOrg)"
Content-language: en-us
Thread-index: Acv3WvQ03P3V8Fi+RcK+W60Wruhj9Q==
X-Mailman-Approved-At: Mon, 11 Apr 2011 19:06:06 -0700
Cc: gen-art@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: Sun, 10 Apr 2011 08:39:51 -0000

This is a multi-part message in MIME format.


--Boundary_(ID_Axi3DX8ApWhu6F2FBOuOrg)
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-softwire-dual-stack-lite-07

Reviewer: Roni Even

Review Date:2011-4-10

IETF LC End Date: 2011-4-12

IESG Telechat date:

 

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

 

Major issues: None

 

 

Minor issues: None

 

 

Nits/editorial comments:

 

1.       In section 8.3 NAT-44 appears without any reference or terminology
expansion.

2.       In section 8.5 "liefetime" should be "lifetime"

3.       I am not sure what the recommendation in section 8.5 is. Is keep
alive required or using PCP is recommended.

 


--Boundary_(ID_Axi3DX8ApWhu6F2FBOuOrg)
Content-type: text/html; charset=us-ascii
Content-transfer-encoding: 7BIT

<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="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:785730766;
	mso-list-type:hybrid;
	mso-list-template-ids:-549430472 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="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal>I am the assigned Gen-ART reviewer for this draft. For background on Gen-ART, please see the FAQ at &lt;<a href="http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" target="_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;.<o:p></o:p></p><p class=MsoNormal>Please resolve these comments along with any other Last Call comments you may receive.<o:p></o:p></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: </span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>draft-ietf-softwire-dual-stack-lite-07<o:p></o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: Roni Even<o:p></o:p></span></p><p cl
 ass=MsoP
t-size:11.0pt;font-family:"Calibri","sans-serif"'>Review Date:2011&#8211;4&#8211;10<o:p></o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC End Date: 2011&#8211;4&#8211;12<o:p></o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG Telechat date:<o:p></o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: This draft is ready for publication as standard track&nbsp; RFC.<o:p></o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major issues: None<o:p></o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:
 "Calibri
p;</o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor issues: None<o:p></o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Nits/editorial comments:<o:p></o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=MsoPlainText style='margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><span style='mso-list:Ignore'>1.<span style='font:7.0pt "Times New R
 oman"'>&
bsp;&nbsp; </span></span></span><![endif]><span dir=LTR></span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section 8.3 NAT-44 appears without any reference or terminology expansion.<o:p></o:p></span></p><p class=MsoPlainText style='margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><span style='mso-list:Ignore'>2.<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><![endif]><span dir=LTR></span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section 8.5 &#8220;</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>liefetime&#8221; should be &#8220;lifetime&#8221;</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p></span></p><p class=MsoPlainText style='margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span
  style='
ily:"Calibri","sans-serif"'><span style='mso-list:Ignore'>3.<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><![endif]><span dir=LTR></span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>I am not sure what the recommendation in section 8.5 is. Is keep alive required or using PCP is recommended.</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p></span></p><p class=MsoNormal><o:p>&nbsp;</o:p></p></div></body></html>

--Boundary_(ID_Axi3DX8ApWhu6F2FBOuOrg)--


From chalikars@gmail.com  Mon Apr 11 22:02:24 2011
Return-Path: <chalikars@gmail.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 9CE24E065A; Mon, 11 Apr 2011 22:02:24 -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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0ZRF2+vkVAWW; Mon, 11 Apr 2011 22:02:19 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfc.amsl.com (Postfix) with ESMTP id 149C5E070E; Mon, 11 Apr 2011 22:02:18 -0700 (PDT)
Received: by fxm15 with SMTP id 15so4674918fxm.31 for <multiple recipients>; Mon, 11 Apr 2011 22:02:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=9jbBCh7Jy1BnpZ3je3ruhloAVT3nzDuxntI5JsH37F0=; b=VM6vZWYIB1T5UYMCxfiazZrixz5fcdB1GEEdhNsASIqDlSUr/lerox3id5F+sy06w6 xp2IPC5QVk4hKSyJiEUyitLjzpiGoeD52LpKG2ugKe2HHZwwLFsFIRQzJbL+R4aRyH4P KZnNwEnDPrnFrfO3GiMtjhNnSliWC3wZfKW3M=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=DBwAkKeqwq17c1Ia2gSOhISeOZRNIr0rY97bFQfjD492OYAtn24VgTgOw/QDxkCwOw IGaUguybZifVe6AGodpFvIT3kWP4w9NQZPOALISGthptS2BDZA7RmiqAYhXvER3q6op6 su2tRV8AwdOT0euZp/dXE04MSB95l7FUPA+Ys=
Received: by 10.223.23.195 with SMTP id s3mr3292995fab.83.1302584536408; Mon, 11 Apr 2011 22:02:16 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.69.141 with HTTP; Mon, 11 Apr 2011 22:01:46 -0700 (PDT)
In-Reply-To: <mailman.85.1302573967.13471.ietf@ietf.org>
References: <mailman.85.1302573967.13471.ietf@ietf.org>
From: Sanjay Chalikar <chalikars@gmail.com>
Date: Tue, 12 Apr 2011 10:31:46 +0530
Message-ID: <BANLkTik00ovOWAZ+HHwh9qXgWnKC-bPpuA@mail.gmail.com>
Subject: Re: Ietf Digest, Vol 35, Issue 13
To: ietf@ietf.org
Cc: ietf-request@ietf.org
Content-Type: multipart/alternative; boundary=001517475fe695222804a0b198a2
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 05:02:24 -0000

--001517475fe695222804a0b198a2
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

ya Sabahattin Gucukoglu is right, if we don't do anything it is much worse
than what we do. So I think we need to increase the productivity in IP v6.

best wishes,
Sanjay
+91-9920291497.




2011/4/12 <ietf-request@ietf.org>

> 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
>
> https://www.ietf.org/mailman/listinfo/ietf
>
> 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.
>
>
>
> Send Ietf mailing list submissions to
>        ietf@ietf.org
>
> 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
>
> You can reach the person managing the list at
>        ietf-owner@ietf.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Ietf digest..."
>
> Today's Topics:
>
>   1. Adventures in IPv6 (Sabahattin Gucukoglu)
>   2. Gen-ART LC review of draft-ietf-kitten-digest-to-historic-03
>      (Ben Campbell)
>   3. Test, please ignore (Glen Barney)
>   4. Re: Call for a Jasmine Revolution in the IETF: Privacy,
>      Integrity,        Obscurity (todd glassey)
>   5. Re: Adventures in IPv6 (Doug Barton)
>   6. Re: Adventures in IPv6 (Masataka Ohta)
>   7. GEn-ART last call review of
>      draft-ietf-softwire-dual-stack-lite-07 (Roni Even)
>
>
> ---------- Forwarded message ----------
> From: Sabahattin Gucukoglu <mail@sabahattin-gucukoglu.com>
> To: ietf@ietf.org
> Date: Mon, 11 Apr 2011 21:41:48 +0100
> Subject: Adventures in IPv6
> This is just a blog posting, but I think it has valid illustrative points
> of the general frustration in it:
> http://bens.me.uk/2011/adventures-in-ipv6
>
> Of course, I think the conclusion is basically wrong, *not* doing IPv6 is
> much worse than breaking the finger-pointing circle, and making it work b=
y
> whatever means necessary.  We won't make the situation better by not doin=
g
> anything.  And yes, I know how tired this all is, but it's starting to lo=
ok
> like some people in this world just aren't going to be convinced until
> there's an actual, real crisis on top of us.
>
> Cheers,
> Sabahattin
>
>
>
> ---------- Forwarded message ----------
> From: Ben Campbell <ben@estacado.net>
> To: draft-ietf-kitten-digest-to-historic.all@tools.ietf.org
> Date: Mon, 11 Apr 2011 15:56:23 -0500
> Subject: Gen-ART LC review of draft-ietf-kitten-digest-to-historic-03
> 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-kitten-digest-to-historic-03
> Reviewer: Ben Campbell
> Review Date: 2011-04-11
> IETF LC End Date: 2011-04-15
>
> Summary: This draft is essentially ready for publication as an
> informational RFC. I have a couple of editorial comments that should be
> considered prior to final publication.
>
> Major issues: None
>
> Minor issues: None
>
> Nits/editorial comments:
>
> -- Note following abstract:
>
> Will this note stay in the RFC? The note makes me unsure whether the
> resulting RFC is intended to actually execute the deprecation, recommend
> deprecation, or start a discussion about deprecation. I assume from the I=
ANA
> section, you intend the first.-
>
> -- Section 1, 7B. "Lack of hash agility."
>
> Can you elaborate on what this means? (I think I know, but I don't know i=
f
> it will be obvious to all readers)
>
>
>
>
>
> ---------- Forwarded message ----------
> From: Glen Barney <glen@amsl.com>
> To: ietf@ietf.org
> Date: Mon, 11 Apr 2011 15:45:18 -0700
> Subject: Test, please ignore
> Test, please ignore.
>
> Glen
> Glen Barney
> IT Director
> AMS (IETF Secretariat)
>
>
>
>
> ---------- Forwarded message ----------
> From: todd glassey <tglassey@earthlink.net>
> To: ietf@ietf.org
> Date: Mon, 11 Apr 2011 13:56:11 -0700
> Subject: Re: Call for a Jasmine Revolution in the IETF: Privacy, Integrit=
y,
> Obscurity
> On 3/23/2011 12:02 AM, Hannes Tschofenig wrote:
>
>> On Mar 23, 2011, at 6:52 AM, SM wrote:
>>
>>  The IETF can only address the technical problems.
>>>
>> This is an argument I often hear. I do, however, believe that you cannot
>> see technology in isolation.
>>
> Yeah - sure you can... if you want to be totally about the original desig=
n
> and practice of the IETF and its vision. It was built to advance protocol
> standardization and not to decide what protocols it would allow on the
> Internet and which it wouldn't.  But  lately many have forgotten this and
> are using the IETF as a formal lobby for technological policy advancement
> and that's a no-no.
>
> Bluntly the IETF members are becoming more and more aggressively
> politically and this statement is based on IAB and other publication on w=
hat
> the IETF does and does not allow through its frameworks. In doing so thei=
r
> statements about allowing protocols or not allowing protocols to be
> standardized based on their stated perception of "what damages the Intern=
et"
> or what they personally want to see as a "free access to all information =
and
> ideas" model, creates a real serious divergence from the Standards Practi=
ce
> this organization was set up as, and IMHO is one which is designed clearl=
y
> to destroy global Intellectual Property law and practice.
>
>> However, in many cases the technology, regulatory environment, business
>> aspects, and the social context gets mixed together.
>>
> No Hannes  - it doesn't unless the Chair allows it to - meaning that the
> Chair in this instance has allowed political materials to be fielded (fil=
ed
> in this instance) into the IETF and trust me I am already filing a formal
> complaint with the Treasury about ISOC's becoming a formal PAC and its
> locking out protocol efforts based on its own desires therein...
>
> http://tools.ietf.org/html/draft-morris-policy-cons-00
>
>
> I suggest that the Chair immediately post a formal statement that the IET=
F
> is a-political and will not do anything but standardize technology.  Also
> that ONLY technology drafts can be accepted since the IETF is part of ISO=
C
> and not registered as a political PAC or Lobbying Agency which it clearly
> has become in direct violation of the NTIA MOU which gave it (ISOC and it=
s
> ARIN) the real power.
>
>
> Todd Glassey
> Please have a look at:
> http://tools.ietf.org/html/draft-morris-policy-cons-00
>
>> Ciao
>> Hannes
>>
>
> Hannes - this is the issue with the IETF and the gross number of flaming
> idiots inside of it. The IETF is not a Social Reform Agency, nor is it a
> freaking political action group since its financial filings prevent this.
>
> Todd Glassey
>
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>>
>>
>
>
>
> ---------- Forwarded message ----------
> From: Doug Barton <dougb@dougbarton.us>
> To: ietf@ietf.org
> Date: Mon, 11 Apr 2011 16:39:39 -0700
> Subject: Re: Adventures in IPv6
> On 04/11/2011 13:41, Sabahattin Gucukoglu wrote:
>
>> This is just a blog posting, but I think it has valid illustrative
>> points of the general frustration in it:
>> http://bens.me.uk/2011/adventures-in-ipv6
>>
>> Of course, I think the conclusion is basically wrong, *not* doing
>> IPv6 is much worse than breaking the finger-pointing circle, and
>> making it work by whatever means necessary.
>>
>
> "Much worse" for who? Just because we (may) believe that IPv6 is the way
> forward doesn't mean that the providers or consumers of Internet services
> will agree with us. The consumers just want to watch their videos and rea=
d
> their mail. The providers just want to sell them that capability. IPv6 ne=
eds
> to solve more problems than it creates, or else it's not the right answer=
.
>
>
> Doug
>
> --
>
>        Nothin' ever doesn't change, but nothin' changes much.
>                        -- OK Go
>
>        Breadth of IT experience, and depth of knowledge in the DNS.
>        Yours for the right price.  :)  http://SupersetSolutions.com/
>
>
>
>
> ---------- Forwarded message ----------
> From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
> To: ietf@ietf.org
> Date: Tue, 12 Apr 2011 10:10:56 +0900
> Subject: Re: Adventures in IPv6
> Sabahattin Gucukoglu wrote:
>
> > Of course, I think the conclusion is basically wrong, *not* doing
> > IPv6 is much worse than breaking the finger-pointing circle,
> > and making it work by whatever means necessary.
>
> The problem is that, operationally, IPv6 does not work.
>
> > We won't make the situation better by not doing anything.
>
> Insisting on IPv6 is worse than not doing anything, because
> it gives people insisting on IPv6 false feeling of doing
> something.
>
> > And yes, I know how tired this all is, but it's starting to
> > look like some people in this world just aren't going to be
> > convinced until there's an actual, real crisis on top of us.
>
> That's so true for you and other people insisting on IPv6.
>
>                                                Masataka Ohta
>
>
>
> ---------- Forwarded message ----------
> From: Roni Even <Even.roni@huawei.com>
> To: draft-ietf-softwire-dual-stack-lite.all@tools.ietf.org
> Date: Sun, 10 Apr 2011 11:40:36 +0300
> Subject: GEn-ART last call review of draft-ietf-softwire-dual-stack-lite-=
07
>
> 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-softwire-dual-stack-lite-07
>
> Reviewer: Roni Even
>
> Review Date:2011=964=9610
>
> IETF LC End Date: 2011=964=9612
>
> IESG Telechat date:
>
>
>
> Summary: This draft is ready for publication as standard track  RFC.
>
>
>
> Major issues: None
>
>
>
> Minor issues: None
>
>
>
>
>
> Nits/editorial comments:
>
>
>
> 1.& bsp;  In section 8.3 NAT-44 appears without any reference or
> terminology expansion.
>
> 2.       In section 8.5 =93liefetime=94 should be =93lifetime=94
>
> 3.       I am not sure what the recommendation in section 8.5 is. Is keep
> alive required or using PCP is recommended.
>
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>
>

--001517475fe695222804a0b198a2
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><span style=3D"color: rgb(0, 0, 153);">ya Sabahattin Gucuk=
oglu is right, if we don&#39;t do anything it is much worse than what we do=
. So I think we need to increase the productivity in IP v6.</span><br style=
=3D"color: rgb(0, 0, 153);">

<br><div dir=3D"ltr"><div><font color=3D"#330099"><span style=3D"color: rgb=
(0, 0, 0); font-family: &#39;Times New Roman&#39;; font-size: medium;"><spa=
n style=3D"font-family: verdana,helvetica,sans-serif; font-weight: bold; co=
lor: rgb(64, 64, 255);"><span style=3D"color: rgb(0, 0, 0); font-family: ar=
ial; font-weight: normal; font-size: small;"><div style=3D"color: rgb(51, 5=
1, 255);">

<font face=3D"verdana, helvetica, sans-serif">best wishes,</font></div><div=
 style=3D"color: rgb(51, 51, 255);"><font face=3D"verdana, helvetica, sans-=
serif">Sanjay</font></div><div style=3D"color: rgb(51, 51, 255);"><font fac=
e=3D"verdana, helvetica, sans-serif">+91-9920291497.</font></div>

<br></span></span></span><span style=3D"font-family: &#39;Times New Roman&#=
39;; font-size: medium;"></span></font></div></div><br>
<br><br><div class=3D"gmail_quote">2011/4/12  <span dir=3D"ltr">&lt;<a href=
=3D"mailto:ietf-request@ietf.org">ietf-request@ietf.org</a>&gt;</span><br><=
blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, 2=
04, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">

If you have received this digest without all the individual message<br>
attachments you will need to update your digest options in your list<br>
subscription. =A0To do so, go to<br>
<br>
<a href=3D"https://www.ietf.org/mailman/listinfo/ietf" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/ietf</a><br>
<br>
Click the &#39;Unsubscribe or edit options&#39; button, log in, and set &qu=
ot;Get<br>
MIME or Plain Text Digests?&quot; to MIME. =A0You can set this option<br>
globally for all the list digests you receive at this point.<br>
<br>
<br>
<br>
Send Ietf mailing list submissions to<br>
 =A0 =A0 =A0 =A0<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
 =A0 =A0 =A0 =A0<a href=3D"https://www.ietf.org/mailman/listinfo/ietf" targ=
et=3D"_blank">https://www.ietf.org/mailman/listinfo/ietf</a><br>
or, via email, send a message with subject or body &#39;help&#39; to<br>
 =A0 =A0 =A0 =A0<a href=3D"mailto:ietf-request@ietf.org">ietf-request@ietf.=
org</a><br>
<br>
You can reach the person managing the list at<br>
 =A0 =A0 =A0 =A0<a href=3D"mailto:ietf-owner@ietf.org">ietf-owner@ietf.org<=
/a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than &quot;Re: Contents of Ietf digest...&quot;<br>
<br>Today&#39;s Topics:<br>
<br>
 =A0 1. Adventures in IPv6 (Sabahattin Gucukoglu)<br>
 =A0 2. Gen-ART LC review of draft-ietf-kitten-digest-to-historic-03<br>
 =A0 =A0 =A0(Ben Campbell)<br>
 =A0 3. Test, please ignore (Glen Barney)<br>
 =A0 4. Re: Call for a Jasmine Revolution in the IETF: Privacy,<br>
 =A0 =A0 =A0Integrity, =A0 =A0 =A0 =A0Obscurity (todd glassey)<br>
 =A0 5. Re: Adventures in IPv6 (Doug Barton)<br>
 =A0 6. Re: Adventures in IPv6 (Masataka Ohta)<br>
 =A0 7. GEn-ART last call review of<br>
 =A0 =A0 =A0draft-ietf-softwire-dual-stack-lite-07 (Roni Even)<br>
<br><br>---------- Forwarded message ----------<br>From:=A0Sabahattin Gucuk=
oglu &lt;<a href=3D"mailto:mail@sabahattin-gucukoglu.com">mail@sabahattin-g=
ucukoglu.com</a>&gt;<br>To:=A0<a href=3D"mailto:ietf@ietf.org">ietf@ietf.or=
g</a><br>

Date:=A0Mon, 11 Apr 2011 21:41:48 +0100<br>Subject:=A0Adventures in IPv6<br=
>This is just a blog posting, but I think it has valid illustrative points =
of the general frustration in it:<br>
<a href=3D"http://bens.me.uk/2011/adventures-in-ipv6" target=3D"_blank">htt=
p://bens.me.uk/2011/adventures-in-ipv6</a><br>
<br>
Of course, I think the conclusion is basically wrong, *not* doing IPv6 is m=
uch worse than breaking the finger-pointing circle, and making it work by w=
hatever means necessary. =A0We won&#39;t make the situation better by not d=
oing anything. =A0And yes, I know how tired this all is, but it&#39;s start=
ing to look like some people in this world just aren&#39;t going to be conv=
inced until there&#39;s an actual, real crisis on top of us.<br>


<br>
Cheers,<br>
Sabahattin<br>
<br>
<br><br>---------- Forwarded message ----------<br>From:=A0Ben Campbell &lt=
;<a href=3D"mailto:ben@estacado.net">ben@estacado.net</a>&gt;<br>To:=A0<a h=
ref=3D"mailto:draft-ietf-kitten-digest-to-historic.all@tools.ietf.org">draf=
t-ietf-kitten-digest-to-historic.all@tools.ietf.org</a><br>

Date:=A0Mon, 11 Apr 2011 15:56:23 -0500<br>Subject:=A0Gen-ART LC review of =
draft-ietf-kitten-digest-to-historic-03<br>I am the assigned Gen-ART review=
er 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;.<br=
>


<br>
Please resolve these comments along with any other Last Call comments you m=
ay receive.<br>
<br>
Document: draft-ietf-kitten-digest-to-historic-03<br>
Reviewer: Ben Campbell<br>
Review Date: 2011-04-11<br>
IETF LC End Date: 2011-04-15<br>
<br>
Summary: This draft is essentially ready for publication as an informationa=
l RFC. I have a couple of editorial comments that should be considered prio=
r to final publication.<br>
<br>
Major issues: None<br>
<br>
Minor issues: None<br>
<br>
Nits/editorial comments:<br>
<br>
-- Note following abstract:<br>
<br>
Will this note stay in the RFC? The note makes me unsure whether the result=
ing RFC is intended to actually execute the deprecation, recommend deprecat=
ion, or start a discussion about deprecation. I assume from the IANA sectio=
n, you intend the first.-<br>


<br>
-- Section 1, 7B. &quot;Lack of hash agility.&quot;<br>
<br>
Can you elaborate on what this means? (I think I know, but I don&#39;t know=
 if it will be obvious to all readers)<br>
<br>
<br>
<br>
<br><br>---------- Forwarded message ----------<br>From:=A0Glen Barney &lt;=
<a href=3D"mailto:glen@amsl.com">glen@amsl.com</a>&gt;<br>To:=A0<a href=3D"=
mailto:ietf@ietf.org">ietf@ietf.org</a><br>Date:=A0Mon, 11 Apr 2011 15:45:1=
8 -0700<br>

Subject:=A0Test, please ignore<br>Test, please ignore.<br>
<br>
Glen<br>
Glen Barney<br>
IT Director<br>
AMS (IETF Secretariat)<br>
<br>
<br>
<br><br>---------- Forwarded message ----------<br>From:=A0todd glassey &lt=
;<a href=3D"mailto:tglassey@earthlink.net">tglassey@earthlink.net</a>&gt;<b=
r>To:=A0<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a><br>Date:=A0Mon, =
11 Apr 2011 13:56:11 -0700<br>

Subject:=A0Re: Call for a Jasmine Revolution in the IETF: Privacy, Integrit=
y, Obscurity<br>On 3/23/2011 12:02 AM, Hannes Tschofenig wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Mar 23, 2011, at 6:52 AM, SM wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The IETF can only address the technical problems.<br>
</blockquote>
This is an argument I often hear. I do, however, believe that you cannot se=
e technology in isolation.<br>
</blockquote>
Yeah - sure you can... if you want to be totally about the original design =
and practice of the IETF and its vision. It was built to advance protocol s=
tandardization and not to decide what protocols it would allow on the Inter=
net and which it wouldn&#39;t. =A0But =A0lately many have forgotten this an=
d are using the IETF as a formal lobby for technological policy advancement=
 and that&#39;s a no-no.<br>


<br>
Bluntly the IETF members are becoming more and more aggressively politicall=
y and this statement is based on IAB and other publication on what the IETF=
 does and does not allow through its frameworks. In doing so their statemen=
ts about allowing protocols or not allowing protocols to be standardized ba=
sed on their stated perception of &quot;what damages the Internet&quot; or =
what they personally want to see as a &quot;free access to all information =
and ideas&quot; model, creates a real serious divergence from the Standards=
 Practice this organization was set up as, and IMHO is one which is designe=
d clearly to destroy global Intellectual Property law and practice.<br>


<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
However, in many cases the technology, regulatory environment, business asp=
ects, and the social context gets mixed together.<br>
</blockquote>
No Hannes =A0- it doesn&#39;t unless the Chair allows it to - meaning that =
the Chair in this instance has allowed political materials to be fielded (f=
iled in this instance) into the IETF and trust me I am already filing a for=
mal complaint with the Treasury about ISOC&#39;s becoming a formal PAC and =
its locking out protocol efforts based on its own desires therein...<br>


<br>
<a href=3D"http://tools.ietf.org/html/draft-morris-policy-cons-00" target=
=3D"_blank">http://tools.ietf.org/html/draft-morris-policy-cons-00</a><br>
<br>
<br>
I suggest that the Chair immediately post a formal statement that the IETF =
is a-political and will not do anything but standardize technology. =A0Also=
 that ONLY technology drafts can be accepted since the IETF is part of ISOC=
 and not registered as a political PAC or Lobbying Agency which it clearly =
has become in direct violation of the NTIA MOU which gave it (ISOC and its =
ARIN) the real power.<br>


<br>
<br>
Todd Glassey<br>
Please have a look at: <a href=3D"http://tools.ietf.org/html/draft-morris-p=
olicy-cons-00" target=3D"_blank">http://tools.ietf.org/html/draft-morris-po=
licy-cons-00</a><br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Ciao<br>
Hannes<br>
</blockquote>
<br>
Hannes - this is the issue with the IETF and the gross number of flaming id=
iots inside of it. The IETF is not a Social Reform Agency, nor is it a frea=
king political action group since its financial filings prevent this.<br>


<br>
Todd Glassey<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
_______________________________________________<br>
Ietf mailing list<br>
<a href=3D"mailto:Ietf@ietf.org" target=3D"_blank">Ietf@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/ietf" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/ietf</a><br>
<br>
</blockquote>
<br>
<br>
<br><br>---------- Forwarded message ----------<br>From:=A0Doug Barton &lt;=
<a href=3D"mailto:dougb@dougbarton.us">dougb@dougbarton.us</a>&gt;<br>To:=
=A0<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a><br>Date:=A0Mon, 11 Ap=
r 2011 16:39:39 -0700<br>

Subject:=A0Re: Adventures in IPv6<br>On 04/11/2011 13:41, Sabahattin Gucuko=
glu wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
This is just a blog posting, but I think it has valid illustrative<br>
points of the general frustration in it:<br>
<a href=3D"http://bens.me.uk/2011/adventures-in-ipv6" target=3D"_blank">htt=
p://bens.me.uk/2011/adventures-in-ipv6</a><br>
<br>
Of course, I think the conclusion is basically wrong, *not* doing<br>
IPv6 is much worse than breaking the finger-pointing circle, and<br>
making it work by whatever means necessary.<br>
</blockquote>
<br>
&quot;Much worse&quot; for who? Just because we (may) believe that IPv6 is =
the way forward doesn&#39;t mean that the providers or consumers of Interne=
t services will agree with us. The consumers just want to watch their video=
s and read their mail. The providers just want to sell them that capability=
. IPv6 needs to solve more problems than it creates, or else it&#39;s not t=
he right answer.<br>


<br>
<br>
Doug<br>
<br>
-- <br>
<br>
 =A0 =A0 =A0 =A0Nothin&#39; ever doesn&#39;t change, but nothin&#39; change=
s much.<br>
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0-- OK Go<br>
<br>
 =A0 =A0 =A0 =A0Breadth of IT experience, and depth of knowledge in the DNS=
.<br>
 =A0 =A0 =A0 =A0Yours for the right price. =A0:) =A0<a href=3D"http://Super=
setSolutions.com/" target=3D"_blank">http://SupersetSolutions.com/</a><br>
<br>
<br>
<br><br>---------- Forwarded message ----------<br>From:=A0Masataka Ohta &l=
t;<a href=3D"mailto:mohta@necom830.hpcl.titech.ac.jp">mohta@necom830.hpcl.t=
itech.ac.jp</a>&gt;<br>To:=A0<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org=
</a><br>

Date:=A0Tue, 12 Apr 2011 10:10:56 +0900<br>Subject:=A0Re: Adventures in IPv=
6<br>Sabahattin Gucukoglu wrote:<br>
<br>
&gt; Of course, I think the conclusion is basically wrong, *not* doing<br>
&gt; IPv6 is much worse than breaking the finger-pointing circle,<br>
&gt; and making it work by whatever means necessary.<br>
<br>
The problem is that, operationally, IPv6 does not work.<br>
<br>
&gt; We won&#39;t make the situation better by not doing anything.<br>
<br>
Insisting on IPv6 is worse than not doing anything, because<br>
it gives people insisting on IPv6 false feeling of doing<br>
something.<br>
<br>
&gt; And yes, I know how tired this all is, but it&#39;s starting to<br>
&gt; look like some people in this world just aren&#39;t going to be<br>
&gt; convinced until there&#39;s an actual, real crisis on top of us.<br>
<br>
That&#39;s so true for you and other people insisting on IPv6.<br>
<br>
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0Masataka Ohta<br>
<br>
<br><br>---------- Forwarded message ----------<br>From:=A0Roni Even &lt;<a=
 href=3D"mailto:Even.roni@huawei.com">Even.roni@huawei.com</a>&gt;<br>To:=
=A0<a href=3D"mailto:draft-ietf-softwire-dual-stack-lite.all@tools.ietf.org=
">draft-ietf-softwire-dual-stack-lite.all@tools.ietf.org</a><br>

Date:=A0Sun, 10 Apr 2011 11:40:36 +0300<br>Subject:=A0GEn-ART last call rev=
iew of draft-ietf-softwire-dual-stack-lite-07<br><div link=3D"blue" vlink=
=3D"purple" lang=3D"EN-US"><div><p class=3D"MsoNormal">I am the assigned Ge=
n-ART reviewer for this draft. For background on Gen-ART, please see the FA=
Q 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;.</p>

<p class=3D"MsoNormal">Please resolve these comments along with any other L=
ast Call comments you may receive.</p><p><span style=3D"font-size: 11pt;">=
=A0</span></p><p><span style=3D"font-size: 11pt;">Document: </span><span st=
yle=3D"font-size: 11pt;">draft-ietf-softwire-dual-stack-lite-07</span></p>

<p><span style=3D"font-size: 11pt;">Reviewer: Roni Even</span></p><p>Review=
 Date:2011=964=9610</p><p><span style=3D"font-size: 11pt;">IETF LC End Date=
: 2011=964=9612</span></p><p><span style=3D"font-size: 11pt;">IESG Telechat=
 date:</span></p>

<p><span style=3D"font-size: 11pt;">=A0</span></p><p><span style=3D"font-si=
ze: 11pt;">Summary: This draft is ready for publication as standard track=
=A0 RFC.</span></p><p><span style=3D"font-size: 11pt;">=A0</span></p><p><sp=
an style=3D"font-size: 11pt;">Major issues: None</span></p>

<p><span style=3D"font-size: 11pt;">=A0</span></p><p><span style=3D"font-si=
ze: 11pt;">Minor issues: None</span></p><p><span style=3D"font-size: 11pt;"=
>=A0</span></p><p><span style=3D"font-size: 11pt;">=A0</span></p><p><span s=
tyle=3D"font-size: 11pt;">Nits/editorial comments:</span></p>

<p><span style=3D"font-size: 11pt;">=A0</span></p><p style=3D"margin-left: =
0.5in;"><span style=3D"font-size: 11pt;"><span>1.<span style=3D"font-family=
: &quot;Times New R oman&quot;; font-style: normal; font-variant: normal; f=
ont-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: =
none; font-stretch: normal;">&amp;
bsp;=A0 </span></span></span><span dir=3D"LTR"></span><span style=3D"font-s=
ize: 11pt;">In section 8.3 NAT-44 appears without any reference or terminol=
ogy expansion.</span></p><p style=3D"margin-left: 0.5in;"><span style=3D"fo=
nt-size: 11pt;"><span>2.<span style=3D"font-family: &quot;Times New Roman&q=
uot;; font-style: normal; font-variant: normal; font-weight: normal; font-s=
ize: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal=
;">=A0=A0=A0=A0=A0=A0 </span></span></span><span dir=3D"LTR"></span><span s=
tyle=3D"font-size: 11pt;">In section 8.5 =93</span><span style=3D"font-size=
: 11pt;">liefetime=94 should be =93lifetime=94</span><span style=3D"font-si=
ze: 11pt;"></span></p>

<p style=3D"margin-left: 0.5in;"><span><span>3.<span style=3D"font-family: =
&quot;Times New Roman&quot;; font-style: normal; font-variant: normal; font=
-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: non=
e; font-stretch: normal;">=A0=A0=A0=A0=A0=A0 </span></span></span><span dir=
=3D"LTR"></span><span style=3D"font-size: 11pt;">I am not sure what the rec=
ommendation in section 8.5 is. Is keep alive required or using PCP is recom=
mended.</span><span style=3D"font-size: 11pt;"></span></p>

<p class=3D"MsoNormal">=A0</p></div></div>
<br>_______________________________________________<br>
Ietf mailing list<br>
<a href=3D"mailto:Ietf@ietf.org">Ietf@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/ietf" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/ietf</a><br>
<br></blockquote></div><br></div>

--001517475fe695222804a0b198a2--

From iljitsch@muada.com  Tue Apr 12 02:57:22 2011
Return-Path: <iljitsch@muada.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 190F9E06F2 for <ietf@ietfc.amsl.com>; Tue, 12 Apr 2011 02:57:22 -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=[AWL=-0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xxc7oJmdBB1G for <ietf@ietfc.amsl.com>; Tue, 12 Apr 2011 02:57:12 -0700 (PDT)
Received: from sequoia.muada.com (sequoia.muada.com [IPv6:2001:1af8:3100:a006:1::]) by ietfc.amsl.com (Postfix) with ESMTP id A34DEE0682 for <ietf@ietf.org>; Tue, 12 Apr 2011 02:57:12 -0700 (PDT)
Received: from claw.it.uc3m.es ([163.117.139.50]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id p3C9wbuA034030 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 12 Apr 2011 11:58:38 +0200 (CEST) (envelope-from iljitsch@muada.com)
Subject: Re: Adventures in IPv6
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <4DA3913B.1030902@dougbarton.us>
Date: Tue, 12 Apr 2011 11:56:28 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <3996F5AD-10FC-4927-B900-9D8BA24C08C3@muada.com>
References: <725F5094-D5D6-4731-B0EE-9ABD99752317@sabahattin-gucukoglu.com> <4DA3913B.1030902@dougbarton.us>
To: Doug Barton <dougb@dougbarton.us>
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: Tue, 12 Apr 2011 09:57:22 -0000

On 12 apr 2011, at 1:39, Doug Barton wrote:

>> http://bens.me.uk/2011/adventures-in-ipv6

What a bunch of whining.

When I first started doing IPv4 it was much harder than this.

>> Of course, I think the conclusion is basically wrong, *not* doing
>> IPv6 is much worse than breaking the finger-pointing circle, and
>> making it work by whatever means necessary.

> "Much worse" for who? Just because we (may) believe that IPv6 is the =
way forward doesn't mean that the providers or consumers of Internet =
services will agree with us.

I'm sure most airline passengers have few opinions on the merits of =
wingtips, either. The engineers can tell you they are a good thing. We =
don't let the public's ignorance override that judgement.

> The consumers just want to watch their videos and read their mail. The =
providers just want to sell them that capability. IPv6 needs to solve =
more problems than it creates, or else it's not the right answer.

It's too late for that discussion now.

If there is some aspect to IPv6 that is broken, we need to fix it as =
soon as possible. But IPv6 is been around for 15 years with ONE WEEK to =
go before APNIC runs dry of addresses it can give out through the =
regular process, so debating the merits of design choices now is =
pointless.

If you read that whiney blogpost you'll see that none of it is about =
problems that the IETF can fix.

It's also important that we show a little understanding and compassion =
when people whine (unlike what I've been doing here) but only a little, =
mostly we have to convey that IPv6 is ready for prime time and no =
negotiation is possible at this point. It's strange, but people actually =
get angrier when you agree with them when they complain. They want and =
expect you to hold your ground while they vent and afterwards they are =
usually ready to face reality.=

From fanf2@hermes.cam.ac.uk  Tue Apr 12 05:47:12 2011
Return-Path: <fanf2@hermes.cam.ac.uk>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id DE191E06BD for <ietf@ietfc.amsl.com>; Tue, 12 Apr 2011 05:47:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.516
X-Spam-Level: 
X-Spam-Status: No, score=-4.516 tagged_above=-999 required=5 tests=[AWL=2.083,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TSNc718LCNxx for <ietf@ietfc.amsl.com>; Tue, 12 Apr 2011 05:47:12 -0700 (PDT)
Received: from ppsw-41.csi.cam.ac.uk (ppsw-41.csi.cam.ac.uk [131.111.8.141]) by ietfc.amsl.com (Postfix) with ESMTP id 0BF95E0699 for <ietf@ietf.org>; Tue, 12 Apr 2011 05:47:11 -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-1.csi.cam.ac.uk ([131.111.8.51]:34138) by ppsw-41.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.156]:25) with esmtpa (EXTERNAL:fanf2) id 1Q9czu-00010p-Rh (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Tue, 12 Apr 2011 13:47:10 +0100
Received: from fanf2 (helo=localhost) by hermes-1.csi.cam.ac.uk (hermes.cam.ac.uk) with local-esmtp id 1Q9czu-0001nj-IZ (Exim 4.67) (return-path <fanf2@hermes.cam.ac.uk>); Tue, 12 Apr 2011 13:47:10 +0100
Date: Tue, 12 Apr 2011 13:47:10 +0100
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-1.csi.cam.ac.uk
To: ietf@ietf.org, lear@cisco.com, lear@cisco.com
Subject: Last Call: draft-lear-iana-timezone-database
Message-ID: <alpine.LSU.2.00.1104121309180.3124@hermes-1.csi.cam.ac.uk>
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>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 12:47:13 -0000

I support this document. I have a few suggestions:

Section 1: Is it worth mentioning that the reference code includes an
implementation of the ISO/IEC 9899 C and IEEE 1003.1 POSIX time functions?

Section 3: The term "TZ name" should be used instead of "key" in the
update criteria, to avoid confusion with the cryptographic key mentioned
earlier in the section.

Criterion 1 could perhaps be clearer. Do I understand correctly that the
intent is something like "New keys are only to be created when it is found
that the region a TZ name was envisioned to cover does not all follow the
same set of timezone rules between 1970 and the present day." That is, the
thing that must be "accurately reflected" is the scope of the TZ rule, not
its name or anything else.

Is it worth documenting the naming scheme here, or would that be unhelpful?

Typo: "policy policy".

Section 5: Should the document explicitly mention that rough consensus of
the TZ list should also be used when considering an appeal to the IESG?

Section 6 and 8: The term "identity" appears whereas section 3 used "well
known key". Is "identity" supposed to imply something more complicated
than a key, such as an x.509 certificate?

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Viking, North Utsire: Northwest backing southwest 4 or 5, occasionally 6.
Moderate or rough. Mainly fair. Good.

From tt@smartcomsoftware.com  Mon Apr 11 11:06:28 2011
Return-Path: <tt@smartcomsoftware.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EADFB3A6AF4 for <ietf@core3.amsl.com>; Mon, 11 Apr 2011 11:06:27 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4R9kgFwJHrPd for <ietf@core3.amsl.com>; Mon, 11 Apr 2011 11:06:26 -0700 (PDT)
Received: from smtp6.freeserve.com (smtp5.freeserve.com [193.252.22.151]) by core3.amsl.com (Postfix) with ESMTP id 2C82B3A6A7F for <ietf@ietf.org>; Mon, 11 Apr 2011 11:06:25 -0700 (PDT)
Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf3527.me.freeserve.com (SMTP Server) with ESMTP id E13F21C04190 for <ietf@ietf.org>; Mon, 11 Apr 2011 20:06:15 +0200 (CEST)
Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf3527.me.freeserve.com (SMTP Server) with ESMTP id D30D61C04199 for <ietf@ietf.org>; Mon, 11 Apr 2011 20:06:15 +0200 (CEST)
Received: from Deskttop2 (unknown [95.145.11.109]) by mwinf3527.me.freeserve.com (SMTP Server) with ESMTP id 98ABA1C04190 for <ietf@ietf.org>; Mon, 11 Apr 2011 20:06:15 +0200 (CEST)
X-ME-UUID: 20110411180615625.98ABA1C04190@mwinf3527.me.freeserve.com
From: "Tim Thornton" <tt@smartcomsoftware.com>
To: <ietf@ietf.org>
Subject: FW: last call for draft-lear-iana-timezone-database-03
Date: Mon, 11 Apr 2011 19:06:13 +0100
Organization: Smartcom Software
Message-ID: <016c01cbf873$25209190$6f61b4b0$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acv4Xm7R0+FP/5G4Qq+kPRzKtDwyXQAFJ0TQ
Content-Language: en-gb
X-Mailman-Approved-At: Tue, 12 Apr 2011 08:26:01 -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, 11 Apr 2011 18:23:45 -0000

I'm happy with the proposals



Smartcom Software Ltd
Portsmouth Technopole
Kingston Crescent
Portsmouth PO2 8FA
United Kingdom

www.smartcomsoftware.com

Smartcom Software is a limited company registered in England and Wales, =
registered number 05641521.


-----Original Message-----
From: Eliot Lear [mailto:lear@cisco.com]=20
Sent: 11 April 2011 16:36
To: tz@lecserver.nci.nih.gov
Subject: FW: last call for draft-lear-iana-timezone-database-03

Hi everyone,

We need your help.

We have made substantial progress in seeing to a permanent home for the
TZ database and mailing list after Arthur David Olson's retirement.  The
announcement below indicates that the Internet Engineering Steering
Group (IESG) is now asking for feedback on the proposal, which is for
the function to be homed by the IANA (Internet Assigned Numbers
Authority).  The intent, again, is to document existing practice, and to
establish a succession process.

Now is the time for you to signify your agreement or disagreement with
this proposal.  Please send your comments to ietf@ietf.org, perhaps
copying this mailing list.  The IESG needs to hear from you as the most
impacted community.  Please do let them know what you think.

Eliot

On 4/11/2011 8:31 AM, The IESG wrote:
>
> The IESG has received a request from an individual submitter to =
consider
> the following document:
> - 'IANA Procedures for Maintaining the Timezone Database'
>    <draft-lear-iana-timezone-database-03.txt>  as a BCP
>
> 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 2011-05-09. 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.
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-lear-iana-timezone-database/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-lear-iana-timezone-database/
>
>
>
> No IPR declarations have been submitted directly on this I-D.
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce
>





From dworley@avaya.com  Tue Apr 12 09:03:20 2011
Return-Path: <dworley@avaya.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id E463BE0800 for <ietf@ietfc.amsl.com>; Tue, 12 Apr 2011 09:03:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.943
X-Spam-Level: 
X-Spam-Status: No, score=-102.943 tagged_above=-999 required=5 tests=[AWL=0.656, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vYqw+0t7bNtn for <ietf@ietfc.amsl.com>; Tue, 12 Apr 2011 09:03:20 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfc.amsl.com (Postfix) with ESMTP id E3873E07AE for <ietf@ietf.org>; Tue, 12 Apr 2011 09:03:19 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAFMtcU2HCzI1/2dsb2JhbACmZXSkeQKZFoVhBJAM
X-IronPort-AV: E=Sophos;i="4.64,197,1301889600"; d="scan'208";a="241361473"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 12 Apr 2011 12:03:18 -0400
X-IronPort-AV: E=Sophos;i="4.64,197,1301889600"; d="scan'208";a="638159363"
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; 12 Apr 2011 12:03:13 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.201]) by DC-US1HCEX1.global.avaya.com ([2002:870b:3414::870b:3414]) with mapi; Tue, 12 Apr 2011 12:03:13 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Sabahattin Gucukoglu <mail-dated-1305146510.84e3c2@sabahattin-gucukoglu.com>, "ietf@ietf.org" <ietf@ietf.org>
Date: Tue, 12 Apr 2011 12:00:07 -0400
Subject: RE: Adventures in IPv6
Thread-Topic: Adventures in IPv6
Thread-Index: Acv4lp8PRuaJJlUzTqGQ8hv7ArteDwAlBJki
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B22246BD3A2@DC-US1MBEX4.global.avaya.com>
References: <725F5094-D5D6-4731-B0EE-9ABD99752317@sabahattin-gucukoglu.com>
In-Reply-To: <725F5094-D5D6-4731-B0EE-9ABD99752317@sabahattin-gucukoglu.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 Apr 2011 16:03:21 -0000

________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Sabahattin=
 Gucukoglu [mail@sabahattin-gucukoglu.com]

This is just a blog posting, but I think it has valid illustrative points o=
f the general frustration in it:
http://bens.me.uk/2011/adventures-in-ipv6
_______________________________________________

I don't see anything remarkable about this -- it's fairly standard frustrat=
ion when one is attempting to be a leading-edge
user of a new technological infrastructure.  And his conclusion isn't parti=
cularly surprising, either, it's just "Don't be the earliest
adopters -- wait until the service/equipment providers have ironed out the =
bugs."

Of course, this leads back to the original problem:  Essentially none of th=
e users who will gain the long-term benefits from the
transition to IPv6 want to be the early adopters who will force the bugs to=
 be ironed out.

Dale

From hallam@gmail.com  Tue Apr 12 09:31:32 2011
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 1BEF2E07D2 for <ietf@ietfc.amsl.com>; Tue, 12 Apr 2011 09:31:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.682
X-Spam-Level: 
X-Spam-Status: No, score=-2.682 tagged_above=-999 required=5 tests=[AWL=-0.084, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CPh3D8Kp5Iur for <ietf@ietfc.amsl.com>; Tue, 12 Apr 2011 09:31:30 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfc.amsl.com (Postfix) with ESMTP id B7C39E072E for <ietf@ietf.org>; Tue, 12 Apr 2011 09:31:30 -0700 (PDT)
Received: by vxg33 with SMTP id 33so6219415vxg.31 for <ietf@ietf.org>; Tue, 12 Apr 2011 09:31:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=4Ep8F47k6XjT0Hh9lz7glhGfRJ++t34SRjt9B7lJUO8=; b=ADvUIv7BFlog+ovWZXf30UaZOJyspbGJiQgylko0KLcmjuSX4H6i0l8lOiGB1/QyS3 wQFXdspOmyPtNwBrTfEk1zooMXAzFsy8Re2zTioILsr55NMVzo5YbxDsBFF4HtXUZFyF Cu1wxYchBJms+9/BTxhlUVHF36SMEagzbnl24=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=DS1fSAAbcoC8O2bwC3G7AdEA9Ce6GofoU0RoPXb/XGx+V66lzDRvcGqiTpQTtfTXpw yaRKCGvwcxQPfHAs6aIdKz/nkcrKh1KVua/OMLr102Ep9sSXD8d3RjUquWwM517c1PyS /WPhjmla0JqLBgMPUdUvTy5FFz6GQdb2hdo+s=
MIME-Version: 1.0
Received: by 10.52.175.5 with SMTP id bw5mr4239203vdc.69.1302625890250; Tue, 12 Apr 2011 09:31:30 -0700 (PDT)
Received: by 10.52.166.230 with HTTP; Tue, 12 Apr 2011 09:31:30 -0700 (PDT)
In-Reply-To: <4DA36AEB.5010600@earthlink.net>
References: <69C307E5-8B96-4604-960B-3270B8D01D8D@softarmor.com> <4CA7D36B-B8DE-431F-AEEB-57675B6951AD@mnot.net> <877B733B-F1CB-4087-BE82-0A1B07623D24@softarmor.com> <DEC3D7BB-0EDE-4584-B5A0-35C6F54CD2CC@mnot.net> <D44303D5-288B-4A44-BD07-8D5A3059BE45@softarmor.com> <4D88BEE2.90504@tana.it> <6.2.5.6.2.20110322211644.0db72cf8@resistor.net> <D85C5068-0F54-40D3-9A94-058C07894CFB@gmx.net> <4DA36AEB.5010600@earthlink.net>
Date: Tue, 12 Apr 2011 12:31:30 -0400
Message-ID: <BANLkTikyw+CvFHxM3RFpjmvoc7+b+h1YHQ@mail.gmail.com>
Subject: Re: Call for a Jasmine Revolution in the IETF: Privacy, Integrity, Obscurity
From: Phillip Hallam-Baker <hallam@gmail.com>
To: todd glassey <tglassey@earthlink.net>
Content-Type: multipart/alternative; boundary=20cf3071cebc76af1004a0bb392c
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 Apr 2011 16:31:32 -0000

--20cf3071cebc76af1004a0bb392c
Content-Type: text/plain; charset=ISO-8859-1

Todd,

This is totally confused and you are completely wrong.

Under the Federal Election Campaign
Act<http://en.wikipedia.org/wiki/Federal_Election_Campaign_Act>,
an organization becomes a "political committee" by receiving contributions
or making expenditures in excess of $1,000 for the purpose of influencing a
federal election
[Source Wikipedia]

Since neither the IETF nor ISOC has any interest in influencing a federal
election, nor does it engage in any activity intended to do so, it is not a
political committee under the terms of the act.



On Mon, Apr 11, 2011 at 4:56 PM, todd glassey <tglassey@earthlink.net>wrote:

> On 3/23/2011 12:02 AM, Hannes Tschofenig wrote:
>
>> On Mar 23, 2011, at 6:52 AM, SM wrote:
>>
>>  The IETF can only address the technical problems.
>>>
>> This is an argument I often hear. I do, however, believe that you cannot
>> see technology in isolation.
>>
> Yeah - sure you can... if you want to be totally about the original design
> and practice of the IETF and its vision. It was built to advance protocol
> standardization and not to decide what protocols it would allow on the
> Internet and which it wouldn't.  But  lately many have forgotten this and
> are using the IETF as a formal lobby for technological policy advancement
> and that's a no-no.
>
> Bluntly the IETF members are becoming more and more aggressively
> politically and this statement is based on IAB and other publication on what
> the IETF does and does not allow through its frameworks. In doing so their
> statements about allowing protocols or not allowing protocols to be
> standardized based on their stated perception of "what damages the Internet"
> or what they personally want to see as a "free access to all information and
> ideas" model, creates a real serious divergence from the Standards Practice
> this organization was set up as, and IMHO is one which is designed clearly
> to destroy global Intellectual Property law and practice.
>
>  However, in many cases the technology, regulatory environment, business
>> aspects, and the social context gets mixed together.
>>
> No Hannes  - it doesn't unless the Chair allows it to - meaning that the
> Chair in this instance has allowed political materials to be fielded (filed
> in this instance) into the IETF and trust me I am already filing a formal
> complaint with the Treasury about ISOC's becoming a formal PAC and its
> locking out protocol efforts based on its own desires therein...
>
>
> http://tools.ietf.org/html/draft-morris-policy-cons-00
>
>
> I suggest that the Chair immediately post a formal statement that the IETF
> is a-political and will not do anything but standardize technology.  Also
> that ONLY technology drafts can be accepted since the IETF is part of ISOC
> and not registered as a political PAC or Lobbying Agency which it clearly
> has become in direct violation of the NTIA MOU which gave it (ISOC and its
> ARIN) the real power.
>
>
> Todd Glassey
>
> Please have a look at:
> http://tools.ietf.org/html/draft-morris-policy-cons-00
>
>> Ciao
>> Hannes
>>
>
> Hannes - this is the issue with the IETF and the gross number of flaming
> idiots inside of it. The IETF is not a Social Reform Agency, nor is it a
> freaking political action group since its financial filings prevent this.
>
> Todd Glassey
>
>  _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>>
>>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>



-- 
Website: http://hallambaker.com/

--20cf3071cebc76af1004a0bb392c
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Todd,=A0<div><br></div><div>This is totally confused and you are completely=
 wrong.</div><div><br></div><div><meta charset=3D"utf-8"><span class=3D"App=
le-style-span" style=3D"font-size: 13px; line-height: 20px; font-family: sa=
ns-serif; ">Under the=A0<a href=3D"http://en.wikipedia.org/wiki/Federal_Ele=
ction_Campaign_Act" style=3D"text-decoration: none; color: rgb(6, 69, 173);=
 background-image: none; background-attachment: initial; background-origin:=
 initial; background-clip: initial; background-color: initial; background-p=
osition: initial initial; background-repeat: initial initial; ">Federal Ele=
ction Campaign Act</a>, an organization becomes a &quot;political committee=
&quot; by receiving contributions or making expenditures in excess of $1,00=
0 for the purpose of influencing a federal election</span></div>
<div><font class=3D"Apple-style-span" face=3D"sans-serif"><span class=3D"Ap=
ple-style-span" style=3D"line-height: 20px;">[Source Wikipedia]</span></fon=
t></div><div><font class=3D"Apple-style-span" face=3D"sans-serif"><span cla=
ss=3D"Apple-style-span" style=3D"line-height: 20px;"><br>
</span></font></div><div><font class=3D"Apple-style-span" face=3D"sans-seri=
f"><span class=3D"Apple-style-span" style=3D"line-height: 20px;">Since neit=
her the IETF nor ISOC has any interest in influencing a federal election, n=
or does it engage in any activity intended to do so, it is not a political =
committee under the terms of the act.</span></font></div>
<div><font class=3D"Apple-style-span" face=3D"sans-serif"><span class=3D"Ap=
ple-style-span" style=3D"line-height: 20px;"><br></span></font></div><div><=
font class=3D"Apple-style-span" face=3D"sans-serif"><span class=3D"Apple-st=
yle-span" style=3D"line-height: 20px;"><br>
</span></font><br><div class=3D"gmail_quote">On Mon, Apr 11, 2011 at 4:56 P=
M, todd glassey <span dir=3D"ltr">&lt;<a href=3D"mailto:tglassey@earthlink.=
net">tglassey@earthlink.net</a>&gt;</span> wrote:<br><blockquote class=3D"g=
mail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-l=
eft:1ex;">
<div class=3D"im">On 3/23/2011 12:02 AM, Hannes Tschofenig wrote:<br>
</div><div class=3D"im"><blockquote class=3D"gmail_quote" style=3D"margin:0=
 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Mar 23, 2011, at 6:52 AM, SM wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
The IETF can only address the technical problems.<br>
</blockquote>
This is an argument I often hear. I do, however, believe that you cannot se=
e technology in isolation.<br>
</blockquote></div>
Yeah - sure you can... if you want to be totally about the original design =
and practice of the IETF and its vision. It was built to advance protocol s=
tandardization and not to decide what protocols it would allow on the Inter=
net and which it wouldn&#39;t. =A0But =A0lately many have forgotten this an=
d are using the IETF as a formal lobby for technological policy advancement=
 and that&#39;s a no-no.<br>

<br>
Bluntly the IETF members are becoming more and more aggressively politicall=
y and this statement is based on IAB and other publication on what the IETF=
 does and does not allow through its frameworks. In doing so their statemen=
ts about allowing protocols or not allowing protocols to be standardized ba=
sed on their stated perception of &quot;what damages the Internet&quot; or =
what they personally want to see as a &quot;free access to all information =
and ideas&quot; model, creates a real serious divergence from the Standards=
 Practice this organization was set up as, and IMHO is one which is designe=
d clearly to destroy global Intellectual Property law and practice.<div cla=
ss=3D"im">
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
However, in many cases the technology, regulatory environment, business asp=
ects, and the social context gets mixed together.<br>
</blockquote></div>
No Hannes =A0- it doesn&#39;t unless the Chair allows it to - meaning that =
the Chair in this instance has allowed political materials to be fielded (f=
iled in this instance) into the IETF and trust me I am already filing a for=
mal complaint with the Treasury about ISOC&#39;s becoming a formal PAC and =
its locking out protocol efforts based on its own desires therein...<div cl=
ass=3D"im">
<br>
<br>
<a href=3D"http://tools.ietf.org/html/draft-morris-policy-cons-00" target=
=3D"_blank">http://tools.ietf.org/html/draft-morris-policy-cons-00</a><br>
<br>
<br></div>
I suggest that the Chair immediately post a formal statement that the IETF =
is a-political and will not do anything but standardize technology. =A0Also=
 that ONLY technology drafts can be accepted since the IETF is part of ISOC=
 and not registered as a political PAC or Lobbying Agency which it clearly =
has become in direct violation of the NTIA MOU which gave it (ISOC and its =
ARIN) the real power.<br>

<br>
<br>
Todd Glassey<div class=3D"im"><br>
Please have a look at: <a href=3D"http://tools.ietf.org/html/draft-morris-p=
olicy-cons-00" target=3D"_blank">http://tools.ietf.org/html/draft-morris-po=
licy-cons-00</a><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Ciao<br>
Hannes<br>
</blockquote>
<br></div>
Hannes - this is the issue with the IETF and the gross number of flaming id=
iots inside of it. The IETF is not a Social Reform Agency, nor is it a frea=
king political action group since its financial filings prevent this.<br>
<font color=3D"#888888">
<br>
Todd Glassey</font><div><div></div><div class=3D"h5"><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
_______________________________________________<br>
Ietf mailing list<br>
<a href=3D"mailto:Ietf@ietf.org" target=3D"_blank">Ietf@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/ietf" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/ietf</a><br>
<br>
</blockquote>
<br>
_______________________________________________<br>
Ietf mailing list<br>
<a href=3D"mailto:Ietf@ietf.org" target=3D"_blank">Ietf@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/ietf" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/ietf</a><br>
</div></div></blockquote></div><br><br clear=3D"all"><br>-- <br>Website: <a=
 href=3D"http://hallambaker.com/">http://hallambaker.com/</a><br><br>
</div>

--20cf3071cebc76af1004a0bb392c--

From chair@ietf.org  Tue Apr 12 11:43:17 2011
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id AABA0E081C; Tue, 12 Apr 2011 11:43: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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1pAQo-u12t8L; Tue, 12 Apr 2011 11:43:16 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [64.170.98.20]) by ietfc.amsl.com (Postfix) with ESMTP id 8E628E067F; Tue, 12 Apr 2011 11:43:16 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c1a.amsl.com (Postfix) with ESMTP id 47239E08C3; Tue, 12 Apr 2011 11:43:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c1a.amsl.com ([127.0.0.1]) by localhost (c1a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TVdMKK4HKZ5r; Tue, 12 Apr 2011 11:43:16 -0700 (PDT)
Received: from [192.168.2.100] (pool-71-178-218-117.washdc.fios.verizon.net [71.178.218.117]) by c1a.amsl.com (Postfix) with ESMTPSA id E2065E08B3; Tue, 12 Apr 2011 11:43:15 -0700 (PDT)
From: IETF Chair <chair@ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: New I-D Submission Tool Installed
Date: Tue, 12 Apr 2011 14:43:14 -0400
Message-Id: <5217938C-A4F0-4EBA-ADC1-6F0CC8D5FA6D@ietf.org>
To: IETF Announce <ietf-announce@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1084)
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: Tue, 12 Apr 2011 18:43:17 -0000

A major update to the Internet-Draft Submission Tool has just been =
installed.  For those of you that have experienced trouble in the past, =
we expect this update to solve your problems.  All of the I-Ds that have =
required manual processing by the Secretariat over the past few months =
were used for testing, and they were all processed properly.

This update integrates the Internet-Draft upload functionality with the =
datatracker.  It improves I-D submission handling and security, and it =
fixes  database inconsistencies caused by the older implementation.  =
Yaco did this work under a contract managed by the IAOC.  In addition, =
major improvements in author extraction from I-D text was provided by =
Henrik.

If you encounter any problems with the upgraded Internet-Draft =
Submission Tool, please write to ietf-action@ietf.org to let us know.

Thanks to all of the people that worked to make this happen.
  Russ=

From sm@resistor.net  Tue Apr 12 13:12:11 2011
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 35D41E08A8 for <ietf@ietfc.amsl.com>; Tue, 12 Apr 2011 13:12:11 -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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qHlUU4iDTW8p for <ietf@ietfc.amsl.com>; Tue, 12 Apr 2011 13:12:09 -0700 (PDT)
Received: from mx.elandsys.com (eland-1-pt.tunnel.tserv15.lax1.ipv6.he.net [IPv6:2001:470:c:d43::2]) by ietfc.amsl.com (Postfix) with ESMTP id D7E88E06BC for <ietf@ietf.org>; Tue, 12 Apr 2011 13:12:07 -0700 (PDT)
Received: from subman.resistor.net (IDENT:sm@localhost [127.0.0.1]) by mx.elandsys.com (8.14.4/8.14.5.Beta0) with ESMTP id p3CKBf0k009143;  Tue, 12 Apr 2011 13:11:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1302639109; bh=mUTPHmJtVxEJu0RCGj+FkmXZQu55T/8aKiMW8NbBC6Q=; h=Message-Id:X-Mailer:Date:To:From:Subject:Cc:In-Reply-To: References:Mime-Version:Content-Type; b=sxV3+uCZ67uf/EtCCkKHbWQdxZl0YqH/D7el40MPNp61Sln53/3gBhDWd1tujydT3 yyZ3O7vgy5KUHWuZV+vLrqP6JxOzH211+7ClXw8/D9k9UU8mDBfBS7JYp+JtdCrPqF xyNUjoD7nY6spWK2Zz0YtHxuECorEFjXGT08IL6Y=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1302639109; bh=mUTPHmJtVxEJu0RCGj+FkmXZQu55T/8aKiMW8NbBC6Q=; h=Message-Id:X-Mailer:Date:To:From:Subject:Cc:In-Reply-To: References:Mime-Version:Content-Type; b=iF515HQDQ1U8dwbKXrlT1EhUwGfsbwtM6N57+deY1p2nrHdtEYm2HT88iSBTyWjfE U1MQhSYyzagHH2Mh3CShjI+BjylOD0qb6jQvP3tSEIFMW/bMFJPIJz75/O0okfnxaR MJ35iS1fZe+eyjgXCDas29CfdelC5jyDKzG7k2/I=
Message-Id: <6.2.5.6.2.20110412110629.0295d168@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 12 Apr 2011 12:49:22 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-lear-iana-timezone-database-03.txt> (IANA Procedures for Maintaining the Timezone Database) to BCP
In-Reply-To: <20110411123156.2886.38916.idtracker@localhost>
References: <20110411123156.2886.38916.idtracker@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: Paul Eggert <eggert@cs.ucla.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: Tue, 12 Apr 2011 20:12:11 -0000

At 05:31 11-04-2011, The IESG wrote:
>The IESG has received a request from an individual submitter to consider
>the following document:
>- 'IANA Procedures for Maintaining the Timezone Database'
>   <draft-lear-iana-timezone-database-03.txt> as a BCP
>
>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

I support the publication of this document.

The Introduction Section mentions "National Institutes of Health".  I 
suggest add "U.S." in brackets.

Tony Finch already commented [1] on using "TZ name" instead of 
"key".  I don't think that naming schemes should be documented in this draft.

Regards,
-sm

1. http://www.ietf.org/mail-archive/web/ietf/current/msg66133.html 


From barryleiba.mailing.lists@gmail.com  Tue Apr 12 16:30:23 2011
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 48532E0950 for <ietf@ietfc.amsl.com>; Tue, 12 Apr 2011 16:30:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.246
X-Spam-Level: 
X-Spam-Status: No, score=-103.246 tagged_above=-999 required=5 tests=[AWL=-0.269, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oVYYQlPpWKM4 for <ietf@ietfc.amsl.com>; Tue, 12 Apr 2011 16:30:22 -0700 (PDT)
Received: from mail-ww0-f42.google.com (mail-ww0-f42.google.com [74.125.82.42]) by ietfc.amsl.com (Postfix) with ESMTP id 5BCFFE0945 for <ietf@ietf.org>; Tue, 12 Apr 2011 16:30:22 -0700 (PDT)
Received: by wwk4 with SMTP id 4so4308856wwk.1 for <ietf@ietf.org>; Tue, 12 Apr 2011 16:30:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=Xjg8M3o1jLohNeqn90DGBUDBA42QhZpUelBn3hdsTKA=; b=kRQajXnvs66GiyvWfqMyjpQRhqJDvFAKgRdJp/oa3+oTGra0NQgqXntoRQgjl1SWd7 gwFgs1x+FxJa+l/QAL7FDDuyKPeu6scDVHvXKSvkgnYCLMNwwSegFuDuUY1sZJOet8wJ bHwabVqjK3nVF4VC4W6kh9+hlOmnGy/58YwEo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=BiqOKfF3265CSdkl9EppvGYwY6+GSOX/k3rFtfiA6gT9/Cwag4G6sD6GZW7xhvGiNM ulKprgQFU/9TfsvH8eBnaHJn0bSRKP/kxd7ZyRuAQButwl795dATSpYtm6D7kPnqr5SI mv/isVikc5bfToj7T8BgfbReQleh340jVivJU=
MIME-Version: 1.0
Received: by 10.227.208.73 with SMTP id gb9mr1702201wbb.194.1302651021620; Tue, 12 Apr 2011 16:30:21 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.227.160.129 with HTTP; Tue, 12 Apr 2011 16:30:19 -0700 (PDT)
In-Reply-To: <20110411123156.2886.38916.idtracker@localhost>
References: <20110411123156.2886.38916.idtracker@localhost>
Date: Tue, 12 Apr 2011 19:30:19 -0400
X-Google-Sender-Auth: hvIDO1uV1LcUfD-WT_WRWoXrP3I
Message-ID: <BANLkTi=qemoumqG4=r+5n7mJVSF_K8hCJQ@mail.gmail.com>
Subject: Re: Last Call: <draft-lear-iana-timezone-database-03.txt> (IANA Procedures for Maintaining the Timezone Database) to BCP
From: Barry Leiba <barryleiba@computer.org>
To: ietf@ietf.org, draft-lear-iana-timezone-database.all@tools.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 Apr 2011 23:30:23 -0000

This document is ready to go, modulo some nits.

Herein, my list of nits:



General
Because you define the terms, you should use them consistently.
Please check for "Coordinator" (replace with "TZ Coordinator") and "TZ
list" (replace with "TZ mailing list").

Sec 1.0
OLD
   The TZ mailing list would fit nicely just as such a list.
NEW
   The TZ mailing list would fit nicely as just such a list.

Sec 1.1
OLD
   The TZ Coordinator also has responsibility
   for maintaining the TZ mailing list.
NEW
   The TZ Coordinator also has responsibility
   for managing the TZ mailing list.

OLD
   2.  Procedures for selecting a technical expert for the technical
       expert who will play the role of TZ Coordinator and release
       manager for the TZ database;
NEW
   2.  Procedures for selecting a technical expert who will play the
       role of TZ Coordinator and release manager for the TZ database;

Sec 2
OLD
   The list will be used just as it has been, to learn of, discuss, and
   confirm TZ definition changes, as well as an announcement list for
   new versions of the database.
NEW
   The list will be used just as it has been: to learn of, discuss, and
   confirm TZ definition changes, as well to serve as an announcement
   list for new versions of the database.

Sec 3
OLD
   Moving forward, the TZ database and supporting code SHOULD be signed
   prior to release using a well known key, along with any appropriate
   supporting information and distributed from a well known location
   that is advertised by IANA in a manner of its choosing.
NEW
   Moving forward, the TZ database, supporting code, and any appropriate
   supporting information SHOULD be signed prior to release using a well
   known key and distributed from a well known location that is
   advertised by IANA in a manner of its choosing.

OLD
   1.  New keys are only to be created when the region a key was
       envisioned to cover is not accurately reflected by an existing
       key.
COMMENT
Because you just mentioned "key", meaning "cryptographic key", in the
previous paragraph, it needs to be clear that these are not those.

OLD
   To be clear, the TZ Coordinator SHALL NOT set timezone policy policy
   for a region
NEW
   To be clear, the TZ Coordinator SHALL NOT set timezone policy
   for a region

OLD
   actually is, or in case of historical corrections, was.
NEW
   actually is (or, in case of historical corrections, was).

Sec 4
OLD
   The IESG will
   use rough consensus of the TZ mailing list as their primary guide to
   further action, when it exists, and whatever other means they have at
   their disposal, when rough consensus cannot be found.
NEW
   The IESG will
   use rough consensus of the TZ mailing list, when such consensus exists,
   as their primary guide to further action.  When rough consensus cannot
   be found, they will use whatever other means they have at their disposal.

Sec 5
OLD
   apellants MUST show material harm from the decision
NEW
   appellants MUST show material harm from the decision

Sec 8
OLD
   The IANA SHALL assist the IESG, as required, in filling of the TZ
   Coordinator, based on the procedures set forth above.
NEW
   The IANA SHALL assist the IESG, as required, in selection of the TZ
   Coordinator, based on the procedures set forth above.

--
Barry

From fred@cisco.com  Tue Apr 12 22:18:12 2011
Return-Path: <fred@cisco.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id CD5F4E0687; Tue, 12 Apr 2011 22:18:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.303
X-Spam-Level: 
X-Spam-Status: No, score=-110.303 tagged_above=-999 required=5 tests=[AWL=0.296, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wkdp-3VLvIA2; Tue, 12 Apr 2011 22:18:12 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by ietfc.amsl.com (Postfix) with ESMTP id EB5B7E06AA; Tue, 12 Apr 2011 22:18:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=1169; q=dns/txt; s=iport; t=1302671892; x=1303881492; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to:content-transfer-encoding; bh=UHO5+9gjTve/vBNf5DSmq/H0MSD2EFqHaNe50U6UCZo=; b=Qt7WSN4+GZei8SczY2juXionvDsB78frNCDA/64TNICMisCQY/4a5ezU 7alWqjDvdE/E8sVTxd7wW4LFd5jmlOhGwf4H26qyBPwlsklT3AEK8hDh8 d0K20hYGafIXOvLc/BKjjL6N3djaA8RScMTRKBBrBzf/HAm+jUl1FpKg6 A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAO0wpU2rRDoH/2dsb2JhbACmCHeIep5hnQWFbgSFXogOg28
X-IronPort-AV: E=Sophos;i="4.64,202,1301875200"; d="scan'208";a="335984598"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by sj-iport-2.cisco.com with ESMTP; 13 Apr 2011 05:18:11 +0000
Received: from stealth-10-32-244-218.cisco.com (stealth-10-32-244-218.cisco.com [10.32.244.218]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p3D5I4Fa012900; Wed, 13 Apr 2011 05:18:10 GMT
Received: from [127.0.0.1] by stealth-10-32-244-218.cisco.com (PGP Universal service); Tue, 12 Apr 2011 22:18:10 -0700
X-PGP-Universal: processed; by stealth-10-32-244-218.cisco.com on Tue, 12 Apr 2011 22:18:10 -0700
Subject: Re: New I-D Submission Tool Installed
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <5217938C-A4F0-4EBA-ADC1-6F0CC8D5FA6D@ietf.org>
Date: Tue, 12 Apr 2011 22:17:48 -0700
Message-Id: <AFCF16FC-3566-4AAE-ABCD-9F831E8CC5E5@cisco.com>
References: <5217938C-A4F0-4EBA-ADC1-6F0CC8D5FA6D@ietf.org>
To: IETF Chair <chair@ietf.org>
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: IETF <ietf@ietf.org>, tools-discuss@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 Apr 2011 05:18:12 -0000

On Apr 12, 2011, at 11:43 AM, IETF Chair wrote:

> A major update to the Internet-Draft Submission Tool has just been =
installed.  For those of you that have experienced trouble in the past, =
we expect this update to solve your problems.  All of the I-Ds that have =
required manual processing by the Secretariat over the past few months =
were used for testing, and they were all processed properly.
>=20
> This update integrates the Internet-Draft upload functionality with =
the datatracker.  It improves I-D submission handling and security, and =
it fixes  database inconsistencies caused by the older implementation.  =
Yaco did this work under a contract managed by the IAOC.  In addition, =
major improvements in author extraction from I-D text was provided by =
Henrik.
>=20
> If you encounter any problems with the upgraded Internet-Draft =
Submission Tool, please write to ietf-action@ietf.org to let us know.
>=20
> Thanks to all of the people that worked to make this happen.

indeed.

>  Russ
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From lear@cisco.com  Wed Apr 13 02:46:21 2011
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 1B94EE073E for <ietf@ietfc.amsl.com>; Wed, 13 Apr 2011 02:46:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.866
X-Spam-Level: 
X-Spam-Status: No, score=-109.866 tagged_above=-999 required=5 tests=[AWL=0.733, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VRE0CpDt+VD1 for <ietf@ietfc.amsl.com>; Wed, 13 Apr 2011 02:46:20 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfc.amsl.com (Postfix) with ESMTP id 246D3E0739 for <ietf@ietf.org>; Wed, 13 Apr 2011 02:46:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=lear@cisco.com; l=1880; q=dns/txt; s=iport; t=1302687980; x=1303897580; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=3TLqOg7iMuQL3Vp7/ae60jysuEfW/OBL8aFcn2hVIhw=; b=GBI9dXl2jB5UxpuIX/SLUwe9V44ibV5E34uwuINYdteBicS2GW0na4NS nuQ2dmp5/hSayNWpwBux4Fo3dLuMKTGDlWV+lulUxN9xubISeRNcAPxGV Y3sHFDEjp/QoYftpEUPjQrWGAkRWqZfqpxLJiufcapSvMwDUZJyX76vnS U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtAEAEFwpU2Q/khLgWdsb2JhbACES6E/FAEBFiYliHqdS4tQkS6BKYFWgXd4BI1s
X-IronPort-AV: E=Sophos;i="4.64,203,1301875200"; d="scan'208";a="25525289"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-2.cisco.com with ESMTP; 13 Apr 2011 09:45:48 +0000
Received: from dhcp-10-55-87-86.cisco.com (dhcp-10-55-87-86.cisco.com [10.55.87.86]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p3D9jmnd028922; Wed, 13 Apr 2011 09:45:48 GMT
Message-ID: <4DA570A6.2080809@cisco.com>
Date: Wed, 13 Apr 2011 11:45:10 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.15) Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: Tony Finch <dot@dotat.at>
Subject: Re: Last Call: draft-lear-iana-timezone-database
References: <alpine.LSU.2.00.1104121309180.3124@hermes-1.csi.cam.ac.uk>
In-Reply-To: <alpine.LSU.2.00.1104121309180.3124@hermes-1.csi.cam.ac.uk>
X-Enigmail-Version: 1.1.1
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: Wed, 13 Apr 2011 09:46:21 -0000

Hi Tony,

Thank you for your comments.

On 4/12/11 2:47 PM, Tony Finch wrote:
> I support this document. I have a few suggestions:
>
> Section 1: Is it worth mentioning that the reference code includes an
> implementation of the ISO/IEC 9899 C and IEEE 1003.1 POSIX time functions?

Added.

> Section 3: The term "TZ name" should be used instead of "key" in the
> update criteria, to avoid confusion with the cryptographic key mentioned
> earlier in the section.

Changed.

> Criterion 1 could perhaps be clearer. Do I understand correctly that the
> intent is something like "New keys are only to be created when it is found
> that the region a TZ name was envisioned to cover does not all follow the
> same set of timezone rules between 1970 and the present day." That is, the
> thing that must be "accurately reflected" is the scope of the TZ rule, not
> its name or anything else.

Thank you.  That term "scope" does make things considerably clearer. 
I've adjusted the text as follows:
> New TZ names (e.g. locations) are only to be created when the
> scope of the region a name was envisioned to cover is no longer accurate.

> Is it worth documenting the naming scheme here, or would that be unhelpful?

I think that probably goes too far, but could be convinced otherwise.
> Typo: "policy policy".
>
> Section 5: Should the document explicitly mention that rough consensus of
> the TZ list should also be used when considering an appeal to the IESG?

I believe the rules are clear, but others should comment.
> Section 6 and 8: The term "identity" appears whereas section 3 used "well
> known key". Is "identity" supposed to imply something more complicated
> than a key, such as an x.509 certificate?

I am leaving that for IANA to decide.  Right now there's nothing, so
anything would be better ;-)

Thanks again,

Eliot

From lear@cisco.com  Wed Apr 13 02:46:23 2011
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 7DA21E074F for <ietf@ietfc.amsl.com>; Wed, 13 Apr 2011 02:46:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.922
X-Spam-Level: 
X-Spam-Status: No, score=-109.922 tagged_above=-999 required=5 tests=[AWL=0.677, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I2J9nQvtaUOn for <ietf@ietfc.amsl.com>; Wed, 13 Apr 2011 02:46:23 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfc.amsl.com (Postfix) with ESMTP id C59AFE0739 for <ietf@ietf.org>; Wed, 13 Apr 2011 02:46:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=lear@cisco.com; l=692; q=dns/txt; s=iport; t=1302687981; x=1303897581; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=lZBmrBNxOcjzpVG89HZIeMgDO1HVyZs0qB/grVRT8W4=; b=Z1o43eGPs31uBIVCKLkR6ASQJP6fkgrULyeEKlKMeTbljUQQGm6TPjVz FPa/NVIexXB22lJ10wLppS+voSwx244cYWG8ZKgZQZWyX1s+RIPczKHRT dP1Dy4DmKrjN2cssKEH3hc6+cVVhPgy2M3XYnW6Cbd7UeF9xQLZ+KbSkT E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAEFwpU2Q/khR/2dsb2JhbACES6E/d4h6nUuLUJEugSmDTXgEjWw
X-IronPort-AV: E=Sophos;i="4.64,203,1301875200"; d="scan'208";a="25525339"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-2.cisco.com with ESMTP; 13 Apr 2011 09:46:05 +0000
Received: from dhcp-10-55-87-86.cisco.com (dhcp-10-55-87-86.cisco.com [10.55.87.86]) by ams-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p3D9k5Fp013410; Wed, 13 Apr 2011 09:46:05 GMT
Message-ID: <4DA570B8.20706@cisco.com>
Date: Wed, 13 Apr 2011 11:45:28 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.15) Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: Last Call: <draft-lear-iana-timezone-database-03.txt> (IANA Procedures for Maintaining the Timezone Database) to BCP
References: <20110411123156.2886.38916.idtracker@localhost> <BANLkTi=qemoumqG4=r+5n7mJVSF_K8hCJQ@mail.gmail.com>
In-Reply-To: <BANLkTi=qemoumqG4=r+5n7mJVSF_K8hCJQ@mail.gmail.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: draft-lear-iana-timezone-database.all@tools.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 Apr 2011 09:46:23 -0000

Hi Barry,

Thanks VERY VERY much for your detailed review.  I have accepted ALL of
your changes modulo one.  And to your comment:

On 4/13/11 1:30 AM, Barry Leiba wrote:
> COMMENT
> Because you just mentioned "key", meaning "cryptographic key", in the
> previous paragraph, it needs to be clear that these are not those.
>
I've changed the term key to TZ name, as suggested by Tony Finch.

> OLD
>    actually is, or in case of historical corrections, was.
> NEW
>    actually is (or, in case of historical corrections, was).
>
This is the one I would prefer to leave alone.  I try my best to avoid
parentheticals in formal work.

Again, thanks for your review!

Eliot

From msk@cloudmark.com  Wed Apr 13 09:29:00 2011
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 35B00E077C for <ietf@ietfc.amsl.com>; Wed, 13 Apr 2011 09:29:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.078
X-Spam-Level: 
X-Spam-Status: No, score=-104.078 tagged_above=-999 required=5 tests=[AWL=-1.479, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EY3XdIfLmqvj for <ietf@ietfc.amsl.com>; Wed, 13 Apr 2011 09:28:59 -0700 (PDT)
Received: from ht2-outbound.cloudmark.com (ht2-outbound.cloudmark.com [72.5.239.36]) by ietfc.amsl.com (Postfix) with ESMTP id 8E588E0716 for <ietf@ietf.org>; Wed, 13 Apr 2011 09:28:59 -0700 (PDT)
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by spite.corp.cloudmark.com ([172.22.10.72]) with mapi; Wed, 13 Apr 2011 09:28:58 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Wed, 13 Apr 2011 09:28:56 -0700
Subject: RE: Last Call: <draft-lear-iana-timezone-database-03.txt> (IANA Procedures for Maintaining the Timezone Database) to BCP
Thread-Topic: Last Call: <draft-lear-iana-timezone-database-03.txt> (IANA Procedures for Maintaining the Timezone Database) to BCP
Thread-Index: Acv4RHs6l07kR+dhTBuwtCbFrZEQFgBs0vzw
Message-ID: <F5833273385BB34F99288B3648C4F06F1343319DD2@EXCH-C2.corp.cloudmark.com>
References: <20110411123156.2886.38916.idtracker@localhost>
In-Reply-To: <20110411123156.2886.38916.idtracker@localhost>
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: Wed, 13 Apr 2011 16:29:00 -0000

> -----Original Message-----
> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-bounces@ietf.o=
rg] On Behalf Of The IESG
> Sent: Monday, April 11, 2011 5:32 AM
> To: IETF-Announce
> Subject: Last Call: <draft-lear-iana-timezone-database-03.txt> (IANA
> Procedures for Maintaining the Timezone Database) to BCP
>=20
> The IESG has received a request from an individual submitter to
> consider
> the following document:
> - 'IANA Procedures for Maintaining the Timezone Database'
>   <draft-lear-iana-timezone-database-03.txt> as a BCP
>=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 2011-05-09. 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.
> [...]

I've read this and seen the presentations about it at IETF 80.  Looks good,=
 especially with the edits Barry and others have proposed.

Good work, folks.

-MSK

From cyrus@daboo.name  Wed Apr 13 09:38:36 2011
Return-Path: <cyrus@daboo.name>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id EC6BDE07CF for <ietf@ietfc.amsl.com>; Wed, 13 Apr 2011 09:38:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.574
X-Spam-Level: 
X-Spam-Status: No, score=-102.574 tagged_above=-999 required=5 tests=[AWL=0.025, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jBrFJXs-60fW for <ietf@ietfc.amsl.com>; Wed, 13 Apr 2011 09:38:36 -0700 (PDT)
Received: from daboo.name (daboo.name [151.201.22.177]) by ietfc.amsl.com (Postfix) with ESMTP id 2363BE07C5 for <ietf@ietf.org>; Wed, 13 Apr 2011 09:38:36 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 5B2B91C7119B1 for <ietf@ietf.org>; Wed, 13 Apr 2011 12:38:35 -0400 (EDT)
X-Virus-Scanned: amavisd-new at daboo.name
Received: from daboo.name ([127.0.0.1]) by localhost (chewy.mulberrymail.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JZlJH9u1LW4f for <ietf@ietf.org>; Wed, 13 Apr 2011 12:38:35 -0400 (EDT)
Received: from caldav.corp.apple.com (unknown [17.101.32.44]) by daboo.name (Postfix) with ESMTPSA id 78E251C7119A5 for <ietf@ietf.org>; Wed, 13 Apr 2011 12:38:34 -0400 (EDT)
Date: Wed, 13 Apr 2011 12:38:31 -0400
From: Cyrus Daboo <cyrus@daboo.name>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-lear-iana-timezone-database-03.txt> (IANA	Procedures for Maintaining the Timezone Database) to BCP
Message-ID: <E6EFDEA5F62F6F4E9FE4379F@caldav.corp.apple.com>
In-Reply-To: <12695_1302525122_p3BCW0BX014387_20110411123156.2886.38916.idtracker@localhost>
References: <12695_1302525122_p3BCW0BX014387_20110411123156.2886.38916.idtracker@localhost>
X-Mailer: Mulberry/4.1.0a1 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; size=414
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 16:38:37 -0000

Hi,

--On April 11, 2011 5:31:56 AM -0700 The IESG <iesg-secretary@ietf.org> 
wrote:

> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'IANA Procedures for Maintaining the Timezone Database'
>   <draft-lear-iana-timezone-database-03.txt> as a BCP

I support publication of this document (with changes already provided by 
others' feedback).

-- 
Cyrus Daboo


From bob.hinden@gmail.com  Wed Apr 13 10:18:44 2011
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id E2BFDE0704 for <ietf@ietfc.amsl.com>; Wed, 13 Apr 2011 10:18: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=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d2QMmdcSJ26t for <ietf@ietfc.amsl.com>; Wed, 13 Apr 2011 10:18:44 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfc.amsl.com (Postfix) with ESMTP id 4D5A4E0690 for <ietf@ietf.org>; Wed, 13 Apr 2011 10:18:44 -0700 (PDT)
Received: by iye19 with SMTP id 19so981710iye.31 for <ietf@ietf.org>; Wed, 13 Apr 2011 10:18:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=pUczFK1wVAe7Ji7xmbWB6z+QgMOi/u/bULv1vyZW1cg=; b=utw6+GelguD+tmvs51b2F589EYepwa1dfHQJ0i5PKk9Etl1iEhBCxQ8c6ZSp8xobxS T6sl29YnDOY1zDlNVNSESoMg19UwIo8s/6AFglXILeOrWmyRrXggeIhGH6L1mjRJabzW aswDshvd5nngruh0wcJ2IXVT/jz9r+rCd+wIA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=hTQOQ51T39AKR8k1XBonp0mSi91UiahNFqAcfrGrMg8KdU36EYuyzMifyQPOo7hJmy tcvtExB38gepZKwr2lEt/2cPd4apI9HqnP98qZ/Tc5TGazgRs/n1cG3u/Sov9P9JDMUw XcawFJFewfRbD+Ro0gHxA/bmuN4npV7OR6uzo=
Received: by 10.231.3.130 with SMTP id 2mr8325361ibn.92.1302715123851; Wed, 13 Apr 2011 10:18:43 -0700 (PDT)
Received: from [10.0.0.37] (c-24-130-226-27.hsd1.ca.comcast.net [24.130.226.27]) by mx.google.com with ESMTPS id d9sm554776ibb.53.2011.04.13.10.18.42 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 13 Apr 2011 10:18:43 -0700 (PDT)
Subject: Re: Last Call: <draft-lear-iana-timezone-database-03.txt> (IANA	Procedures for Maintaining the Timezone Database) to BCP
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <E6EFDEA5F62F6F4E9FE4379F@caldav.corp.apple.com>
Date: Wed, 13 Apr 2011 10:18:41 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <12335AE7-0166-4525-89A0-40C15083E94C@gmail.com>
References: <12695_1302525122_p3BCW0BX014387_20110411123156.2886.38916.idtracker@localhost> <E6EFDEA5F62F6F4E9FE4379F@caldav.corp.apple.com>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1082)
Cc: Cyrus Daboo <cyrus@daboo.name>, Bob Hinden <bob.hinden@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: Wed, 13 Apr 2011 17:18:45 -0000

On Apr 13, 2011, at 9:38 AM, Cyrus Daboo wrote:

> Hi,
>=20
> --On April 11, 2011 5:31:56 AM -0700 The IESG =
<iesg-secretary@ietf.org> wrote:
>=20
>> The IESG has received a request from an individual submitter to =
consider
>> the following document:
>> - 'IANA Procedures for Maintaining the Timezone Database'
>>  <draft-lear-iana-timezone-database-03.txt> as a BCP
>=20
> I support publication of this document (with changes already provided =
by others' feedback).

+1

Bob



From bob.hinden@gmail.com  Wed Apr 13 11:19:40 2011
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 1B0C1E0724 for <ietf@ietfc.amsl.com>; Wed, 13 Apr 2011 11:19:40 -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=1.000, BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5TYSqfM2gIDg for <ietf@ietfc.amsl.com>; Wed, 13 Apr 2011 11:19:39 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfc.amsl.com (Postfix) with ESMTP id 41CC1E0660 for <ietf@ietf.org>; Wed, 13 Apr 2011 11:19:39 -0700 (PDT)
Received: by iye19 with SMTP id 19so1032991iye.31 for <ietf@ietf.org>; Wed, 13 Apr 2011 11:19:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=3elKTGDJEWKVRZ3K2+H435s2sLXAVVHSUrtkdCdTXtc=; b=rvJAMPosFRpLX79N1dIu8lr24A0OJilAUXKtN8LezJ9LoAO7ZQgjoILIOTGGdLbgZm qCTET+fX9ClEktPe8ALI2Y6L0EkkcJw+CQwm12PrCHb8QTU6oArNvHyI4l/5qNumzJdo 7v8FbzurB8HtfbThzJSXiSsNMp/dhYAfn6hpY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=kBIMkT8SUCZF0pQKKgHh69fEggSrCvg/DUFmGPcqFkb1MNhXDQQV3maqrwT4O0VB3d oxuzLoNT1o3FthDi88dsl+fD1cg0szTXz0bgIbczimDWRPekwmXEplreiAYfM5Zonqfl aFacyDhKJOV2hjrcR2RUlJ+WyG1xKAjAdQovk=
Received: by 10.42.220.72 with SMTP id hx8mr11361787icb.239.1302718778844; Wed, 13 Apr 2011 11:19:38 -0700 (PDT)
Received: from [10.0.0.37] (c-24-130-226-27.hsd1.ca.comcast.net [24.130.226.27]) by mx.google.com with ESMTPS id 13sm590895ibo.8.2011.04.13.11.19.35 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 13 Apr 2011 11:19:38 -0700 (PDT)
Subject: Re: IAOC: delegating ex-officio responsibility
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <82A347CC-BB19-4A73-8E8A-924FBAA92A5F@NLnetLabs.nl>
Date: Wed, 13 Apr 2011 11:19:33 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <84D6568B-18C9-47B2-A457-C51C2FB3351F@gmail.com>
References: <2BE582FA-2682-4232-9D83-23A03F01A0DB@NLnetLabs.nl> <6.2.5.6.2.20110330073936.0e1899d0@resistor.net> <E2E41FDE-3818-4513-9933-CB1E0326B43E@nlnetlabs.nl> <6.2.5.6.2.20110330113947.0c948bc0@resistor.net> <4D942843.4060804@gmail.com> <6.2.5.6.2.20110331120351.09488990@resistor.net> <4D955661.8050502@gmail.com> <9C81C0F6-3ABE-4479-8C5E-C20C486D052A@gmail.com> <82A347CC-BB19-4A73-8E8A-924FBAA92A5F@NLnetLabs.nl>
To: Olaf Kolkman <olaf@NLnetLabs.nl>
X-Mailer: Apple Mail (2.1082)
Cc: Bob Hinden <bob.hinden@gmail.com>, 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, 13 Apr 2011 18:19:40 -0000

Olaf,

On Apr 2, 2011, at 1:28 AM, Olaf Kolkman wrote:

>=20
> [as editor:]
>=20
> It seems that the high order bit of this discussion circles around the =
question on whether it a requirement for the IETF Chair to have a voting =
position in order to effectively perform oversight. Once we figured out =
where we want to go with that we can think about delegation by the chair =
vs appointment by the bodies and the implementation details with respect =
to the trust.

For the record, I don't agree with this summary.  That is, I still =
question the basic assumption in the proposal.  We have "running code" =
in the IASA model and it appears to work reasonable well.  Not perfect, =
of course.  In particular I think that having the IETF chair, IAB chair, =
and ISOC president as voting members of the IAOC (and IETF Trust) has =
worked very well.  It makes them an active part of decisions the IAOC =
and IETF Trust are making and helps keep the IAOC from getting =
disconnected from the community.  It also makes them share the =
responsibility for decisions by having their vote be publicly recorded. =20=


I also don't understand what the effect of the proposal is on the IETF =
Trust.  Currently all IAOC members are members of the IETF Trust.  They =
have to sign a letter accepting this role.  I don't think it can then be =
delegated. =20

Your draft focuses on one area (that is, reducing the burden of these =
positions), but does not discuss any other aspects of making this =
change.  What might the negative aspects of delegating this =
responsibility be?  How will this be dealt with?

Each of the positions (IETF Chair, IAB chair, ISOC President) are =
different in the way they are selected and this effects their ability to =
delegate their responsibility and who they might delegate it to.  For =
example, the IETF chair is selected by the NOMCOM and one of his/her =
responsibilities is to sit on the IAB, IAOC, and IETF Trust.  The IAB =
chair is selected by the IAB.  The ISOC president is hired by the ISOC =
Board of Trustees.  Consequently, I think the authority to delegate =
differs and they should be considered separately. =20

>=20
> [as olaf:]
>=20
> I agree that the IETF chair needs to have a good oversight about what =
goes on in the IETF, to a lesser extend it is good that the IAB has that =
oversight too (specifically with respect to its chartered =
responsibilities) but I wonder if a voting membership is the appropriate =
instrument.

Why not?  It does appear to work.

> I believe effective oversight depends on having the appropriate high =
level information and having the opportunity to timely inject =
information that is needed to steer an outcome. An alternative method =
for sharing and injecting is having regular meetings between the I* =
chairs and the ISOC President/CEO. I believe that such meetings are much =
more effective for the parties involved than being exposed to all =
details.

Do we really need to have another regular meeting?  Would this give the =
I* chairs more authority than they have now?  Sort of an executive =
committee.  Would these meetings be public, have votes, have public =
minutes? =20

> This only an illustration of an instrument, there may be other =
instruments for oversight as well. But I do not think the ex-officio =
membership is the only method.

It's not perfect but it is the one we have now and it is working.   We =
should only change it if we are sure that it will improve the overall =
IASA operation.  I am seriously concerned about the current proposal.

Bob



From stpeter@stpeter.im  Wed Apr 13 19:30:35 2011
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 744E3E07AA for <ietf@ietfc.amsl.com>; Wed, 13 Apr 2011 19:30:35 -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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lDLS2b5QvVze for <ietf@ietfc.amsl.com>; Wed, 13 Apr 2011 19:30:34 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by ietfc.amsl.com (Postfix) with ESMTP id B7D41E0707 for <ietf@ietf.org>; Wed, 13 Apr 2011 19:30:34 -0700 (PDT)
Received: from squire.local (dsl-251-69.dynamic-dsl.frii.net [216.17.251.69]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id C4A5740D20 for <ietf@ietf.org>; Wed, 13 Apr 2011 20:33:37 -0600 (MDT)
Message-ID: <4DA65C47.9040009@stpeter.im>
Date: Wed, 13 Apr 2011 20:30:31 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: audio streaming archive...
References: <4D91954F.7080007@bogus.com>
In-Reply-To: <4D91954F.7080007@bogus.com>
X-Enigmail-Version: 1.1.1
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms090205050700020002030006"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 02:30:35 -0000

This is a cryptographically signed message in MIME format.

--------------ms090205050700020002030006
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 3/29/11 2:16 AM, Joel Jaeggli wrote:

> the long term home as with all other recordings is:
>=20
> http://www.ietf.org/audio/

I receive a 403 Forbidden error there.

Peter

--=20
Peter Saint-Andre
https://stpeter.im/




--------------ms090205050700020002030006
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIITzjCC
BjQwggQcoAMCAQICASMwDQYJKoZIhvcNAQELBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoT
DVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNp
Z25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3
MTAyNDIxMDMzM1oXDTE3MTAyNDIxMDMzM1owgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1T
dGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu
aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAzIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBALmjSW4SPiDKlAinvVeL
ZOVfItiuP1aRHL530E7QUc9icCwL33+PH+Js1HAh8CgWFl34sOxx1FJyS/C4VLPRsqDfP72j
tzCVUAL0DAxZ7wgzQvFz7x61jGxfhYhqYb1+PPOLkYBbkRIrPMg3dLEdKmXIYJYXDH+mB/V/
jLo73/Kb7h/rNoNg/oHHSv5Jolyvp5IY2btfcTBfW/telEFj5rDTX2juTvZ3Qhf3XQX5ca3Q
7A10zrUV/cWJOJ7F5RltbEIaboZmX5JBUb3FhUiAdBotehAX6DbDOuYoJtVxmGof6GuVGcPo
98K4TJf8FHo+UA9EOVDp/W7fCqKT4sXk/XkCAwEAAaOCAa0wggGpMA8GA1UdEwEB/wQFMAMB
Af8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBR7iZySlyShhEcCy3T8LvSs3DLl8zAfBgNV
HSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRaMFgwJwYIKwYBBQUH
MAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYhaHR0cDovL3d3
dy5zdGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6Ly93d3cu
c3RhcnRzc2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5jb20v
c2ZzY2EuY3JsMIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQELBQADggIBAGpd
SbdLFMhirxK37V4gE00+uW74UdAXtDgQI3AsRZWtaRtKHgAxFBSteqz4kDkeAjH/1b+K8tQR
6cxSI2nho7qOaPW/UpzOfSS/MeKK/9vfM2lfs+uItXH7LWtvS9wD1erfH1a+BXHCrCp4LA1l
fADDhRIiGTSS3i0Zu5xV3INNRHrCCCl6patltQ8RZTqzDMri7ombgIxjN51Zo7xV77EZcThV
0GA8iIN+7T53uHhUJpjfLIztHs/69OclRvHux9hCflfOm7GY5Sc4nqjfES+5XPArGGWiQSEk
ez37QfXqsxO3oCHK4b3DFZysG4uyOuC/WL80ab3muQ3tgwjBhq0D3JZN5kvu5gSuNZPa1WrV
hEgXkd6C7s5stqB6/htVpshG08jRz9DEutGM9oKQ1ncTivbfPNx7pILoHWvvT7N5i/puVoNu
bPUmLXh/2wA6wzAzuuoONiIL14Xpw6jLSnqpaLWElo2yTIFZ/CU/nCvvpW1Dj1457P3Ci9bD
0RPkWSR+CuucpgxrEmaw4UOLxflzuYYaq1RJwygOO5K0s2bAWOcXpgteyUOnQ3d/EjJAWRri
2v0ubiq+4H3KUOMlbznlPAY/1T8YyyJPM88+Ueahe/AW1zoUwZayNcTnuM7cq6yBV8Wr3GOI
LFXhtT0UVuJLChPMJKVKVsa7qNorlLkMMIIGxzCCBa+gAwIBAgICAIswDQYJKoZIhvcNAQEF
BQAwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJT
ZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBD
bGFzcyAzIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTAeFw0xMDEwMTQwMTM2MzRa
Fw0xMjEwMTQxMjAxMDdaMIHAMSAwHgYDVQQNExcyNzQ1ODEtOU5YMDRxeExEYjBvNDY5VDEL
MAkGA1UEBhMCVVMxETAPBgNVBAgTCENvbG9yYWRvMQ8wDQYDVQQHEwZEZW52ZXIxLDAqBgNV
BAsTI1N0YXJ0Q29tIFRydXN0ZWQgQ2VydGlmaWNhdGUgTWVtYmVyMRowGAYDVQQDExFQZXRl
ciBTYWludC1BbmRyZTEhMB8GCSqGSIb3DQEJARYSc3RwZXRlckBzdHBldGVyLmltMIIBIjAN
BgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAuERvnrkpQTx9wbJfgxbNKEYvt0IilecZRUM6
wrbCzIUPCocuYhaAJcQoqIyHaKybPQ7f+DIGIAolAa3dHnNdlsXP2smTft/ZNpj10PIG5bil
NAqLUYwmLJaEaqY7BMW8423U3blW43/luLJk/Pq4OsWcw7AK3LeVh1U/HOgqhin26N3h72X1
nbLEpZFrgcp8egmWtXLCbLBDMqUK3j6wjLldni79muzYEVqU0A5GqSeb8Wc4kIx8VI5yL24J
KzinG2iVRP5ZDEbOZETzBXJabUsV56XSxqPG9DK6ke+ybCiL/wKV1HFqdtFB1y25lfvHgOP2
gyEApBKEDNjgLmKyyQIDAQABo4IC+zCCAvcwCQYDVR0TBAIwADALBgNVHQ8EBAMCBLAwHQYD
VR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMB0GA1UdDgQWBBS2EW2iNB+g0EibKJLBdv8I
eLovVDAfBgNVHSMEGDAWgBR7iZySlyShhEcCy3T8LvSs3DLl8zAdBgNVHREEFjAUgRJzdHBl
dGVyQHN0cGV0ZXIuaW0wggFCBgNVHSAEggE5MIIBNTCCATEGCysGAQQBgbU3AQICMIIBIDAu
BggrBgEFBQcCARYiaHR0cDovL3d3dy5zdGFydHNzbC5jb20vcG9saWN5LnBkZjA0BggrBgEF
BQcCARYoaHR0cDovL3d3dy5zdGFydHNzbC5jb20vaW50ZXJtZWRpYXRlLnBkZjCBtwYIKwYB
BQUHAgIwgaowFBYNU3RhcnRDb20gTHRkLjADAgEBGoGRTGltaXRlZCBMaWFiaWxpdHksIHNl
ZSBzZWN0aW9uICpMZWdhbCBMaW1pdGF0aW9ucyogb2YgdGhlIFN0YXJ0Q29tIENlcnRpZmlj
YXRpb24gQXV0aG9yaXR5IFBvbGljeSBhdmFpbGFibGUgYXQgaHR0cDovL3d3dy5zdGFydHNz
bC5jb20vcG9saWN5LnBkZjBjBgNVHR8EXDBaMCugKaAnhiVodHRwOi8vd3d3LnN0YXJ0c3Ns
LmNvbS9jcnR1My1jcmwuY3JsMCugKaAnhiVodHRwOi8vY3JsLnN0YXJ0c3NsLmNvbS9jcnR1
My1jcmwuY3JsMIGOBggrBgEFBQcBAQSBgTB/MDkGCCsGAQUFBzABhi1odHRwOi8vb2NzcC5z
dGFydHNzbC5jb20vc3ViL2NsYXNzMy9jbGllbnQvY2EwQgYIKwYBBQUHMAKGNmh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2NlcnRzL3N1Yi5jbGFzczMuY2xpZW50LmNhLmNydDAjBgNVHRIE
HDAahhhodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS8wDQYJKoZIhvcNAQEFBQADggEBADVtbXJG
tKAr55xc/OUM546gXUybI72Bank0w739Mv+9BBNtq9rMEvCnLmSKhBi76c1mdXh6zXs8RQDo
6nR/aPabE3llF2T4z80smi9jfnl3y9dpu9TcgDoqDLZ7a2lBlW656XAAQzHjvLp2MC7/mxlg
PYH2axa+q40mAYM20GbNsAEGbWQT1IqIh0BcLLsgbaMJHbyG/57zd9JLyMX3Vry1L1fJRQr3
GeLxMV5RtxN+mBgxrwFz/cOc09COiFExlsHgekpB5O43gqsAU16MXypyoSt4MrSfKTMHIGx6
2RF/M6vqUlvhi28gk2ZUvQ/+OX5+gjcZyooEzAAn4RuOKNswggbHMIIFr6ADAgECAgIAizAN
BgkqhkiG9w0BAQUFADCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4x
KzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMT
L1N0YXJ0Q29tIENsYXNzIDMgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBMB4XDTEw
MTAxNDAxMzYzNFoXDTEyMTAxNDEyMDEwN1owgcAxIDAeBgNVBA0TFzI3NDU4MS05TlgwNHF4
TERiMG80NjlUMQswCQYDVQQGEwJVUzERMA8GA1UECBMIQ29sb3JhZG8xDzANBgNVBAcTBkRl
bnZlcjEsMCoGA1UECxMjU3RhcnRDb20gVHJ1c3RlZCBDZXJ0aWZpY2F0ZSBNZW1iZXIxGjAY
BgNVBAMTEVBldGVyIFNhaW50LUFuZHJlMSEwHwYJKoZIhvcNAQkBFhJzdHBldGVyQHN0cGV0
ZXIuaW0wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC4RG+euSlBPH3Bsl+DFs0o
Ri+3QiKV5xlFQzrCtsLMhQ8Khy5iFoAlxCiojIdorJs9Dt/4MgYgCiUBrd0ec12Wxc/ayZN+
39k2mPXQ8gbluKU0CotRjCYsloRqpjsExbzjbdTduVbjf+W4smT8+rg6xZzDsArct5WHVT8c
6CqGKfbo3eHvZfWdssSlkWuBynx6CZa1csJssEMypQrePrCMuV2eLv2a7NgRWpTQDkapJ5vx
ZziQjHxUjnIvbgkrOKcbaJVE/lkMRs5kRPMFclptSxXnpdLGo8b0MrqR77JsKIv/ApXUcWp2
0UHXLbmV+8eA4/aDIQCkEoQM2OAuYrLJAgMBAAGjggL7MIIC9zAJBgNVHRMEAjAAMAsGA1Ud
DwQEAwIEsDAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwHQYDVR0OBBYEFLYRbaI0
H6DQSJsoksF2/wh4ui9UMB8GA1UdIwQYMBaAFHuJnJKXJKGERwLLdPwu9KzcMuXzMB0GA1Ud
EQQWMBSBEnN0cGV0ZXJAc3RwZXRlci5pbTCCAUIGA1UdIASCATkwggE1MIIBMQYLKwYBBAGB
tTcBAgIwggEgMC4GCCsGAQUFBwIBFiJodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9wb2xpY3ku
cGRmMDQGCCsGAQUFBwIBFihodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9pbnRlcm1lZGlhdGUu
cGRmMIG3BggrBgEFBQcCAjCBqjAUFg1TdGFydENvbSBMdGQuMAMCAQEagZFMaW1pdGVkIExp
YWJpbGl0eSwgc2VlIHNlY3Rpb24gKkxlZ2FsIExpbWl0YXRpb25zKiBvZiB0aGUgU3RhcnRD
b20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgUG9saWN5IGF2YWlsYWJsZSBhdCBodHRwOi8v
d3d3LnN0YXJ0c3NsLmNvbS9wb2xpY3kucGRmMGMGA1UdHwRcMFowK6ApoCeGJWh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2NydHUzLWNybC5jcmwwK6ApoCeGJWh0dHA6Ly9jcmwuc3RhcnRz
c2wuY29tL2NydHUzLWNybC5jcmwwgY4GCCsGAQUFBwEBBIGBMH8wOQYIKwYBBQUHMAGGLWh0
dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9zdWIvY2xhc3MzL2NsaWVudC9jYTBCBggrBgEFBQcw
AoY2aHR0cDovL3d3dy5zdGFydHNzbC5jb20vY2VydHMvc3ViLmNsYXNzMy5jbGllbnQuY2Eu
Y3J0MCMGA1UdEgQcMBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tLzANBgkqhkiG9w0BAQUF
AAOCAQEANW1tcka0oCvnnFz85QznjqBdTJsjvYFqeTTDvf0y/70EE22r2swS8KcuZIqEGLvp
zWZ1eHrNezxFAOjqdH9o9psTeWUXZPjPzSyaL2N+eXfL12m71NyAOioMtntraUGVbrnpcABD
MeO8unYwLv+bGWA9gfZrFr6rjSYBgzbQZs2wAQZtZBPUioiHQFwsuyBtowkdvIb/nvN30kvI
xfdWvLUvV8lFCvcZ4vExXlG3E36YGDGvAXP9w5zT0I6IUTGWweB6SkHk7jeCqwBTXoxfKnKh
K3gytJ8pMwcgbHrZEX8zq+pSW+GLbyCTZlS9D/45fn6CNxnKigTMACfhG44o2zGCA80wggPJ
AgEBMIGTMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UE
CxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRD
b20gQ2xhc3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAgCLMAkGBSsOAwIa
BQCgggIOMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDQx
NDAyMzAzMVowIwYJKoZIhvcNAQkEMRYEFE5+UKgW2ExK6i5wHa+urSOccdJ3MF8GCSqGSIb3
DQEJDzFSMFAwCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggq
hkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBpAYJKwYBBAGCNxAEMYGWMIGT
MIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2Vj
dXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xh
c3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAgCLMIGmBgsqhkiG9w0BCRAC
CzGBlqCBkzCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNV
BAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMTL1N0YXJ0
Q29tIENsYXNzIDMgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBAgIAizANBgkqhkiG
9w0BAQEFAASCAQBJAdSO6zmNnh5huhoP3+YSPx2McmoGiM9aebn3xC2VI/cwKgxwieAM5sVX
j1OtjU7m1nW5sCl6ZXwjr55lae6sdSAC8mEjVenAe05vSk5HRTsqz682pL788KjNAXJBdM6Q
sBjLONDZtFJnCPuJM21yu2VDez0oDMMEW2Chqsm5k8TiJ4qYyuOiQRwznotHpuUBftmAoKvI
N6gC0pSLOZY8A+I7fC1FGiCNIMPjHx8/nydIoslD3g/ZuEKuj19zou4rlzaeMkOybrtF5AlY
Ulzs3Fv6/ZS9+mUSKkYSUDXV8Npih5gEmPw3ZorGVUaW3yk4RDS/S1cgUBu7Bqy+noJuAAAA
AAAA
--------------ms090205050700020002030006--

From mrex@sap.com  Wed Apr 13 19:54:25 2011
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 6D9A0E066C for <ietf@ietfc.amsl.com>; Wed, 13 Apr 2011 19:54:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.688
X-Spam-Level: 
X-Spam-Status: No, score=-9.688 tagged_above=-999 required=5 tests=[AWL=-0.039, BAYES_00=-2.599, HELO_EQ_DE=0.35, J_CHICKENPOX_25=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OR2x-xEKuUsO for <ietf@ietfc.amsl.com>; Wed, 13 Apr 2011 19:54:24 -0700 (PDT)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfc.amsl.com (Postfix) with ESMTP id 8A243E07C7 for <ietf@ietf.org>; Wed, 13 Apr 2011 19:54:24 -0700 (PDT)
Received: from mail.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id p3E2sMK3003357 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 14 Apr 2011 04:54:22 +0200 (MEST)
From: Martin Rex <mrex@sap.com>
Message-Id: <201104140254.p3E2sMjk014471@fs4113.wdf.sap.corp>
Subject: Re: audio streaming archive...
To: stpeter@stpeter.im (Peter Saint-Andre)
Date: Thu, 14 Apr 2011 04:54:22 +0200 (MEST)
In-Reply-To: <4DA65C47.9040009@stpeter.im> from "Peter Saint-Andre" at Apr 13, 11 08:30:31 pm
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
Cc: 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: Thu, 14 Apr 2011 02:54:25 -0000

Peter Saint-Andre wrote:
> 
> On 3/29/11 2:16 AM, Joel Jaeggli wrote:
> 
> > the long term home as with all other recordings is:
> > 
> > http://www.ietf.org/audio/
> 
> I receive a 403 Forbidden error there.

There seems to be an(other?) archive here:
http://ietf80streaming.dnsalias.net/ietf80/

I tried to listen to the DANE session from Wednesday morning
(should have been channel 8 according to the agenda),
but the ch8 wed-am file seems to be a copy of ch5 wed-am instead. :-(

-Martin

From amorris@amsl.com  Wed Apr 13 20:17:36 2011
Return-Path: <amorris@amsl.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 23703E07AA for <ietf@ietfc.amsl.com>; Wed, 13 Apr 2011 20:17: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=[AWL=0.001,  BAYES_00=-2.599]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2KFfhAV+z5rl for <ietf@ietfc.amsl.com>; Wed, 13 Apr 2011 20:17:35 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [64.170.98.20]) by ietfc.amsl.com (Postfix) with ESMTP id E656DE0668 for <ietf@ietf.org>; Wed, 13 Apr 2011 20:17:34 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c1a.amsl.com (Postfix) with ESMTP id 94726E08CD; Wed, 13 Apr 2011 20:17:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c1a.amsl.com ([127.0.0.1]) by localhost (c1a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1zQJMAxZmsaK; Wed, 13 Apr 2011 20:17:34 -0700 (PDT)
Received: from [192.168.0.198] (c-76-102-55-37.hsd1.ca.comcast.net [76.102.55.37]) by c1a.amsl.com (Postfix) with ESMTPSA id 2AAC7E08BB; Wed, 13 Apr 2011 20:17:33 -0700 (PDT)
Message-Id: <27F52A21-A14E-4AFD-9823-33519885ED6F@amsl.com>
From: Alexa Morris <amorris@amsl.com>
To: Peter Saint-Andre <stpeter@stpeter.im>
In-Reply-To: <4DA65C47.9040009@stpeter.im>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Subject: Re: audio streaming archive...
Date: Wed, 13 Apr 2011 20:17:33 -0700
References: <4D91954F.7080007@bogus.com> <4DA65C47.9040009@stpeter.im>
X-Mailer: Apple Mail (2.936)
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, 14 Apr 2011 03:17:36 -0000

Peter,

Apologies for the error; this has been fixed.

Alexa

On Apr 13, 2011, at 7:30 PM, Peter Saint-Andre wrote:

> On 3/29/11 2:16 AM, Joel Jaeggli wrote:
>
>> the long term home as with all other recordings is:
>>
>> http://www.ietf.org/audio/
>
> I receive a 403 Forbidden error there.
>
> Peter
>
> -- 
> Peter Saint-Andre
> https://stpeter.im/
>
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

-----------
Alexa Morris / Executive Director / IETF
48377 Fremont Blvd., Suite 117, Fremont, CA  94538
Phone: +1.510.492.4089 / Fax: +1.510.492.4001
Email: amorris@amsl.com

Managed by Association Management Solutions (AMS)
Forum Management, Meeting and Event Planning
www.amsl.com <http://www.amsl.com/>


From joelja@bogus.com  Wed Apr 13 21:58:31 2011
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 266F5E080B for <ietf@ietfc.amsl.com>; Wed, 13 Apr 2011 21:58:31 -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=[BAYES_00=-2.599, J_CHICKENPOX_25=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U6pwPGUZ-2Qz for <ietf@ietfc.amsl.com>; Wed, 13 Apr 2011 21:58:30 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfc.amsl.com (Postfix) with ESMTP id 289BFE07FF for <ietf@ietf.org>; Wed, 13 Apr 2011 21:58:29 -0700 (PDT)
Received: from 23173jjaeggli.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 p3E4wO35002142 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Thu, 14 Apr 2011 04:58:26 GMT (envelope-from joelja@bogus.com)
Message-ID: <4DA67EF0.4050209@bogus.com>
Date: Wed, 13 Apr 2011 21:58:24 -0700
From: Joel Jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.15) Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: mrex@sap.com
Subject: Re: audio streaming archive...
References: <201104140254.p3E2sMjk014471@fs4113.wdf.sap.corp>
In-Reply-To: <201104140254.p3E2sMjk014471@fs4113.wdf.sap.corp>
X-Enigmail-Version: 1.1.1
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.2 (nagasaki.bogus.com [147.28.0.81]); Thu, 14 Apr 2011 04:58:27 +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: Thu, 14 Apr 2011 04:58:31 -0000

there was a naming convention issue on the channel5 recorder which I
thought that we caught all of those by I could be wrong...

The contractor has the channel8 recorder and should be able toretrive
the file.

joel

On 4/13/11 7:54 PM, Martin Rex wrote:
> Peter Saint-Andre wrote:
>>
>> On 3/29/11 2:16 AM, Joel Jaeggli wrote:
>>
>>> the long term home as with all other recordings is:
>>>
>>> http://www.ietf.org/audio/
>>
>> I receive a 403 Forbidden error there.
> 
> There seems to be an(other?) archive here:
> http://ietf80streaming.dnsalias.net/ietf80/
> 
> I tried to listen to the DANE session from Wednesday morning
> (should have been channel 8 according to the agenda),
> but the ch8 wed-am file seems to be a copy of ch5 wed-am instead. :-(
> 
> -Martin
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> 


From mperumal@cisco.com  Wed Apr 13 23:34:29 2011
Return-Path: <mperumal@cisco.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 79DD0E0687; Wed, 13 Apr 2011 23:34:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.068
X-Spam-Level: 
X-Spam-Status: No, score=-10.068 tagged_above=-999 required=5 tests=[AWL=0.531, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PBD78QsooeIz; Wed, 13 Apr 2011 23:34:28 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfc.amsl.com (Postfix) with ESMTP id 482E4E0670; Wed, 13 Apr 2011 23:34:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=mperumal@cisco.com; l=2375; q=dns/txt; s=iport; t=1302762868; x=1303972468; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=nYGt6pXqQhgnqBoSSIhO6ygEYDPvYQJ3kuEAVQ2jlXc=; b=FG68sgfzFHG+Tyr4enz3iel3b+J4CyZ64/bDvPdMTYImre7rwdbEAr5P Ap3Xpb183eUVdWP5TNdACqKT1DVI3mbvXSC/zts0YdJmXERGwnVoRqqH3 EjsQjmeNR+C1+lPsOb6hendZNVVrIHoneLMMBqZdAfq74vgV1HdN2MpZs Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqMCADmVpk2Q/khMgWdsb2JhbACYMj+NMhQBARYmJaQNnHSFbgSFWIwR
X-IronPort-AV: E=Sophos;i="4.64,209,1301875200"; d="scan'208";a="25647458"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-2.cisco.com with ESMTP; 14 Apr 2011 06:34:10 +0000
Received: from xbh-bgl-411.cisco.com (xbh-bgl-411.cisco.com [72.163.129.201]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p3E6XL4D029502; Thu, 14 Apr 2011 06:34:10 GMT
Received: from xmb-bgl-414.cisco.com ([72.163.129.210]) by xbh-bgl-411.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 14 Apr 2011 12:03:27 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [siprec] Last Call: <draft-ietf-siprec-req-09.txt> (Use Cases andRequirements	for SIP-based Media Recording (SIPREC)) toInformational RFC
Date: Thu, 14 Apr 2011 12:03:31 +0530
Message-ID: <1D062974A4845E4D8A343C65380492020533BB70@XMB-BGL-414.cisco.com>
In-Reply-To: <20110406125020.17538.70016.idtracker@localhost>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] Last Call: <draft-ietf-siprec-req-09.txt> (Use Cases andRequirements	for SIP-based Media Recording (SIPREC)) toInformational RFC
Thread-Index: Acv0WYBeRuGjGNBtTZSHeqn78QP5xwGEv6Yw
References: <20110406125020.17538.70016.idtracker@localhost>
From: "Muthu ArulMozhi Perumal (mperumal)" <mperumal@cisco.com>
To: <ietf@ietf.org>
X-OriginalArrivalTime: 14 Apr 2011 06:33:27.0782 (UTC) FILETIME=[DD16A860:01CBFA6D]
Cc: siprec@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 Apr 2011 06:34:29 -0000

I've one major comment. It draft discusses synchronization between the
recorded media streams and synchronized playback, which seem important
for certain applications:

<snip>
Some applications require the recording of more than one media stream,
possibly of different types. Media are synchronized, either at storage
or at playback.
</snip>

However, in the requirements section it doesn't seem REQ-022 and REQ-023
are all that are need and sufficient to achieve this with needed
precision. So, I would suggest adding another requirement as follows:
The mechanism MUST provide means for facilitating synchronization of the
recorded media streams and metadata either at storage or at playback.
This includes, but not limited to, the information needed as per REQ-022
and REQ-023.

A nitpick:
Use Case 8
In cases where calls inside or between branches must be recorded, a
centralized recording system in data centers together with telephony
infrastructure (e.g. PBX) me deployed.

s/me/may be

Muthu

|-----Original Message-----
|From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
Behalf Of The IESG
|Sent: Wednesday, April 06, 2011 6:20 PM
|To: IETF-Announce
|Cc: siprec@ietf.org
|Subject: [siprec] Last Call: <draft-ietf-siprec-req-09.txt> (Use Cases
andRequirements for SIP-based
|Media Recording (SIPREC)) toInformational RFC
|
|
|The IESG has received a request from the SIP Recording WG (siprec) to
|consider the following document:
|- 'Use Cases and Requirements for SIP-based Media Recording (SIPREC)'
|  <draft-ietf-siprec-req-09.txt> as an 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 2011-04-20. 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.
|
|The file can be obtained via
|http://datatracker.ietf.org/doc/draft-ietf-siprec-req/
|
|IESG discussion can be tracked via
|http://datatracker.ietf.org/doc/draft-ietf-siprec-req/
|
|
|
|No IPR declarations have been submitted directly on this I-D.
|_______________________________________________
|siprec mailing list
|siprec@ietf.org
|https://www.ietf.org/mailman/listinfo/siprec

From brian.e.carpenter@gmail.com  Thu Apr 14 00:17:19 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 40761E06D1 for <ietf@ietfc.amsl.com>; Thu, 14 Apr 2011 00:17:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.71
X-Spam-Level: 
X-Spam-Status: No, score=-104.71 tagged_above=-999 required=5 tests=[AWL=0.889, BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fs2MW6DxisZY for <ietf@ietfc.amsl.com>; Thu, 14 Apr 2011 00:17:18 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfc.amsl.com (Postfix) with ESMTP id CDA2AE06E3 for <ietf@ietf.org>; Thu, 14 Apr 2011 00:17:17 -0700 (PDT)
Received: by wyb29 with SMTP id 29so1260537wyb.31 for <ietf@ietf.org>; Thu, 14 Apr 2011 00:17:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=qqA8CaBNUZWOVxT+825Hx4qkebcVT4TTUQv7sEdQbuk=; b=hOoXeNcWPQROp/7lLBZwU5G0gO7sYIKBihJwuZM376iW+oHyhrqhOFD4lzCK+3+kKO ywdsLk2GN8Ay+Y2wG67lsTMlmZCMxtmhsVE1RQwAPL+dsLlNi4XWF2AREbo0mNLXivle vssiKv3geg9dMESwRKqB7eE/X/OErjskwEVE8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=RVKze6Vz8CFG4W7uJDk9+EY9ug8FhYZ6tDBriM6JXvOdy19KlWvalmvrBw3GZpRc57 ENoBuiRWqT15EYleFnF/ImJ1QBdDDC/b0D2ZceOcsHKBzKnvEubmlE0iwUQp1neXqQ+H WPjn/iGSlhh4Lnp0IzWrlRPkX3QEtjBfrjtRw=
Received: by 10.216.237.159 with SMTP id y31mr434568weq.41.1302765436350; Thu, 14 Apr 2011 00:17:16 -0700 (PDT)
Received: from [192.168.1.65] (host81-159-213-38.range81-159.btcentralplus.com [81.159.213.38]) by mx.google.com with ESMTPS id c54sm632235wer.30.2011.04.14.00.17.14 (version=SSLv3 cipher=OTHER); Thu, 14 Apr 2011 00:17:15 -0700 (PDT)
Message-ID: <4DA69F79.6030700@gmail.com>
Date: Thu, 14 Apr 2011 19:17:13 +1200
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: Bob Hinden <bob.hinden@gmail.com>
Subject: Re: IAOC: delegating ex-officio responsibility
References: <2BE582FA-2682-4232-9D83-23A03F01A0DB@NLnetLabs.nl>	<6.2.5.6.2.20110330073936.0e1899d0@resistor.net>	<E2E41FDE-3818-4513-9933-CB1E0326B43E@nlnetlabs.nl>	<6.2.5.6.2.20110330113947.0c948bc0@resistor.net>	<4D942843.4060804@gmail.com>	<6.2.5.6.2.20110331120351.09488990@resistor.net>	<4D955661.8050502@gmail.com>	<9C81C0F6-3ABE-4479-8C5E-C20C486D052A@gmail.com>	<82A347CC-BB19-4A73-8E8A-924FBAA92A5F@NLnetLabs.nl> <84D6568B-18C9-47B2-A457-C51C2FB3351F@gmail.com>
In-Reply-To: <84D6568B-18C9-47B2-A457-C51C2FB3351F@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
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: Thu, 14 Apr 2011 07:17:19 -0000

On 2011-04-14 06:19, Bob Hinden wrote:
> Olaf,
> 
> On Apr 2, 2011, at 1:28 AM, Olaf Kolkman wrote:
> 
>> [as editor:]
>> 
>> It seems that the high order bit of this discussion circles
>> around the question on whether it a requirement for the
>> IETF Chair to have a voting position in order to
>> effectively perform oversight. Once we figured out where we
>> want to go with that we can think about delegation by the
>> chair vs appointment by the bodies and the implementation
>> details with respect to the trust.
> 
> For the record, I don't agree with this summary.  That is, I
> still question the basic assumption in the proposal.  We have
> "running code" in the IASA model and it appears to work
> reasonable well.  Not perfect, of course.  In particular I
> think that having the IETF chair, IAB chair, and ISOC
> president as voting members of the IAOC (and IETF Trust) has
> worked very well.  It makes them an active part of decisions
> the IAOC and IETF Trust are making and helps keep the IAOC
> from getting disconnected from the community.  It also makes
> them share the responsibility for decisions by having their
> vote be publicly recorded.

I agree. I think this responsibility should not be delegated.
It's fundamental to the success of the IETF (and the ISOC for
that matter - the IETF is a major source of ISOC's legitimacy).
The IAOC delegates execution to the IAD etc. - maybe the real
bug is that the IAOC itself needs to delegate more?

> I also don't understand what the effect of the proposal is on
> the IETF Trust.  Currently all IAOC members are members of
> the IETF Trust.  They have to sign a letter accepting this
> role.  I don't think it can then be delegated.

It can't be delegated. However, a duly approved update to BCP101
can change the definition of the formal membership of the
IAOC, and that would automatically change the membership of
the Trust. An alternative would be a formal change to the Trust
Agreement, but since IANAL, I don't know whether a change to
allow delegation or proxies would be possible under the law of
the Commonwealth of Virginia, where the Trust was established.

    Brian
> 
> Your draft focuses on one area (that is, reducing the burden
> of these positions), but does not discuss any other aspects
> of making this change.  What might the negative aspects of
> delegating this responsibility be?  How will this be dealt
> with?
> 
> Each of the positions (IETF Chair, IAB chair, ISOC President)
> are different in the way they are selected and this effects
> their ability to delegate their responsibility and who they
> might delegate it to.  For example, the IETF chair is
> selected by the NOMCOM and one of his/her responsibilities is
> to sit on the IAB, IAOC, and IETF Trust.  The IAB chair is
> selected by the IAB.  The ISOC president is hired by the ISOC
> Board of Trustees.  Consequently, I think the authority to
> delegate differs and they should be considered separately.
> 
>> [as olaf:]
>> 
>> I agree that the IETF chair needs to have a good oversight
>> about what goes on in the IETF, to a lesser extend it is
>> good that the IAB has that oversight too (specifically with
>> respect to its chartered responsibilities) but I wonder if
>> a voting membership is the appropriate instrument.
> 
> Why not?  It does appear to work.
> 
>> I believe effective oversight depends on having the
>> appropriate high level information and having the
>> opportunity to timely inject information that is needed to
>> steer an outcome. An alternative method for sharing and
>> injecting is having regular meetings between the I* chairs
>> and the ISOC President/CEO. I believe that such meetings
>> are much more effective for the parties involved than being
>> exposed to all details.
> 
> Do we really need to have another regular meeting?  Would
> this give the I* chairs more authority than they have now?
> Sort of an executive committee.  Would these meetings be
> public, have votes, have public minutes?
> 
>> This only an illustration of an instrument, there may be
>> other instruments for oversight as well. But I do not think
>> the ex-officio membership is the only method.
> 
> It's not perfect but it is the one we have now and it is
> working.   We should only change it if we are sure that it
> will improve the overall IASA operation.  I am seriously
> concerned about the current proposal.
> 
> Bob
> 
> 
> _______________________________________________ Ietf mailing
> list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf
> 
> 

From olaf@nlnetlabs.nl  Thu Apr 14 02:02:12 2011
Return-Path: <olaf@nlnetlabs.nl>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 2C122E066F for <ietf@ietfc.amsl.com>; Thu, 14 Apr 2011 02:02: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=[AWL=1.000, BAYES_00=-2.599, GB_I_LETTER=-2, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ItjajFBVBOMM for <ietf@ietfc.amsl.com>; Thu, 14 Apr 2011 02:02:02 -0700 (PDT)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by ietfc.amsl.com (Postfix) with ESMTP id 965C1E0664 for <ietf@ietf.org>; Thu, 14 Apr 2011 02:02:02 -0700 (PDT)
Received: from dhcp-95.nlnetlabs.nl (dhcp-95.nlnetlabs.nl [213.154.224.95]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.4/8.14.4) with ESMTP id p3E91wlv049417 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 14 Apr 2011 11:01:58 +0200 (CEST) (envelope-from olaf@nlnetlabs.nl)
Subject: Re: IAOC: delegating ex-officio responsibility
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Olaf Kolkman <olaf@NLnetLabs.nl>
In-Reply-To: <4DA69F79.6030700@gmail.com>
Date: Thu, 14 Apr 2011 11:01:48 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <E19E3F13-90E4-48B0-9A6C-951DAA97D24E@nlnetlabs.nl>
References: <2BE582FA-2682-4232-9D83-23A03F01A0DB@NLnetLabs.nl>	<6.2.5.6.2.20110330073936.0e1899d0@resistor.net>	<E2E41FDE-3818-4513-9933-CB1E0326B43E@nlnetlabs.nl>	<6.2.5.6.2.20110330113947.0c948bc0@resistor.net>	<4D942843.4060804@gmail.com>	<6.2.5.6.2.20110331120351.09488990@resistor.net>	<4D955661.8050502@gmail.com>	<9C81C0F6-3ABE-4479-8C5E-C20C486D052A@gmail.com>	<82A347CC-BB19-4A73-8E8A-924FBAA92A5F@NLnetLabs.nl> <84D6568B-18C9-47B2-A457-C51C2FB3351F@gmail.com> <4DA69F79.6030700@gmail.com>
To: IETF Discussion <ietf@ietf.org>
X-Pgp-Agent: GPGMail 1.3.3
X-Mailer: Apple Mail (2.1084)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (open.nlnetlabs.nl [213.154.224.1]); Thu, 14 Apr 2011 11:01:58 +0200 (CEST)
Cc: Bob Hinden <bob.hinden@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: Thu, 14 Apr 2011 09:02:12 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On Apr 14, 2011, at 9:17 AM, Brian E Carpenter wrote:

> On 2011-04-14 06:19, Bob Hinden wrote:
>> Olaf,
>>=20
>> On Apr 2, 2011, at 1:28 AM, Olaf Kolkman wrote:
>>=20
>>> [as editor:]
>>>=20
>>> It seems that the high order bit of this discussion circles
>>> around the question on whether it a requirement for the
>>> IETF Chair to have a voting position in order to
>>> effectively perform oversight. Once we figured out where we
>>> want to go with that we can think about delegation by the
>>> chair vs appointment by the bodies and the implementation
>>> details with respect to the trust.
>>=20
>> For the record, I don't agree with this summary.  That is, I
>> still question the basic assumption in the proposal.  We have
>> "running code" in the IASA model and it appears to work
>> reasonable well.  Not perfect, of course.  In particular I
>> think that having the IETF chair, IAB chair, and ISOC
>> president as voting members of the IAOC (and IETF Trust) has
>> worked very well.  It makes them an active part of decisions
>> the IAOC and IETF Trust are making and helps keep the IAOC
>> from getting disconnected from the community.  It also makes
>> them share the responsibility for decisions by having their
>> vote be publicly recorded.
>=20
> I agree. I think this responsibility should not be delegated.
> It's fundamental to the success of the IETF (and the ISOC for
> that matter - the IETF is a major source of ISOC's legitimacy).
> The IAOC delegates execution to the IAD etc. - maybe the real
> bug is that the IAOC itself needs to delegate more?
>=20



I agree the IASA model is working well and I also agree that the chairs =
have played an important role.=20

But I am not convinced that it is the only way to keep the IAOC from =
getting disconnected from the community. To turn that argument around: =
If it is the case that we need the IAB chair, IETF chair and ISOC =
president [iChiefs] to keep the IAOC on track then why do we have NOMCOM =
appointments? One could easily argue that the NOMCOM appointments are =
made to keep the IAOC connected to the community.

I also do not see why it 'it's fundamental to the success of the IETF'. =
I do agree that the iChiefs need to understand what is going on, there =
is no dispute about, but I question whether IAOC membership is best and =
most efficient instrument.



>> I also don't understand what the effect of the proposal is on
>> the IETF Trust.  Currently all IAOC members are members of
>> the IETF Trust.  They have to sign a letter accepting this
>> role.  I don't think it can then be delegated.
>=20
> It can't be delegated. However, a duly approved update to BCP101
> can change the definition of the formal membership of the
> IAOC, and that would automatically change the membership of
> the Trust. An alternative would be a formal change to the Trust
> Agreement, but since IANAL, I don't know whether a change to
> allow delegation or proxies would be possible under the law of
> the Commonwealth of Virginia, where the Trust was established.
>=20

I do not want to brush over this important detail. But, let us first =
figure out what we want with the IAOC. If there is no consensus on =
having the iChiefs play a less involved role then fine tuning the =
details doesn't make sense. If we gain consensus then fixing the Trust =
is doable.

>>=20
>> Your draft focuses on one area (that is, reducing the burden
>> of these positions), but does not discuss any other aspects
>> of making this change.  What might the negative aspects of
>> delegating this responsibility be?  How will this be dealt
>> with?

Help me out.

The main _potential_ negative aspect is a drop of iChiefs' awareness of =
what is going on; and the ability to directly influence decisions.


>>=20
>> Each of the positions (IETF Chair, IAB chair, ISOC President)
>> are different in the way they are selected and this effects
>> their ability to delegate their responsibility and who they
>> might delegate it to.  For example, the IETF chair is
>> selected by the NOMCOM and one of his/her responsibilities is
>> to sit on the IAB, IAOC, and IETF Trust.  The IAB chair is
>> selected by the IAB.  The ISOC president is hired by the ISOC
>> Board of Trustees.  Consequently, I think the authority to
>> delegate differs and they should be considered separately.

I agree, this needs discussion. But lets first see if there is any =
consensus on going down the path of getting the iChiefs out day-to-day =
IAOC business.


>>=20
>>> [as olaf:]
>>>=20
>>> I agree that the IETF chair needs to have a good oversight
>>> about what goes on in the IETF, to a lesser extend it is
>>> good that the IAB has that oversight too (specifically with
>>> respect to its chartered responsibilities) but I wonder if
>>> a voting membership is the appropriate instrument.
>>=20
>> Why not?  It does appear to work.



Yes it works. But it consumes a lot of time too. IAOC retreat, meetings =
at the IETF, regular tele-chats, participation in sub committees, etc, =
etc...=20

We have a responsibility to our leadership to make their jobs scalable =
and manageable. We need to have our leadership positions accessible to =
our peers, who may not have the support of their company for more than a =
half time job, or, not to forget, may not have the support of their =
families for the travel and the long evenings with telechats. Being =
effective in what committees and meetings one participates in is part of =
making the job scalable.=20

The Best Current Practice is that the iChiefs _must_ participate in the =
IAOC, I like that _must_ being removed.


>>=20
>>> I believe effective oversight depends on having the
>>> appropriate high level information and having the
>>> opportunity to timely inject information that is needed to
>>> steer an outcome. An alternative method for sharing and
>>> injecting is having regular meetings between the I* chairs
>>> and the ISOC President/CEO. I believe that such meetings
>>> are much more effective for the parties involved than being
>>> exposed to all details.
>>=20
>> Do we really need to have another regular meeting?  Would
>> this give the I* chairs more authority than they have now?
>> Sort of an executive committee.  Would these meetings be
>> public, have votes, have public minutes?


It is not another meeting, it is replacing a lot of other meetings by =
one regular meeting that talks about issues at the right level of =
detail. Also, sharing information is not decision making. Russ and I had =
weekly calls planned (we didn't have them weekly, but that aside) to =
share information and brainstorm about potential issues.=20

I don't see the 'more authority' argument, not in the context where one =
argues for direct votes in order to get effective oversight. I think =
that having a weekly iChiefs meeting gives less formal authority and =
(yes) a bit more informal authority.


>>> This only an illustration of an instrument, there may be
>>> other instruments for oversight as well. But I do not think
>>> the ex-officio membership is the only method.
>>=20
>> It's not perfect but it is the one we have now and it is
>> working.   We should only change it if we are sure that it
>> will improve the overall IASA operation.  I am seriously
>> concerned about the current proposal.


My question is whether there is any will to pursue a change to the BCP =
to work towards removing the _must_. (The Best Current Practice is that =
the iChiefs _must_ participate in the IAOC, I like that _must_ being =
removed.)

I have seen Brian and Bob argue against. And not very many people argue =
'for'

- --Olaf


________________________________________________________=20

Olaf M. Kolkman                        NLnet Labs
http://www.nlnetlabs.nl/           =20
I will start to use a new PGP key (ID 0x3B6AAA64) at the beginning
of May 2011.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: This message is locally signed.
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAk2muAIACgkQtN/ca3YJIocKGwCggV3Z5um2cmWrUdXcba19SLNr
cH4AoI0vilyFYRIa5Bx1j6i7T45klrYs
=3DF6bJ
-----END PGP SIGNATURE-----

From john.elwell@siemens-enterprise.com  Thu Apr 14 03:54:26 2011
Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 7B1D4E0684; Thu, 14 Apr 2011 03:54:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.81
X-Spam-Level: 
X-Spam-Status: No, score=-104.81 tagged_above=-999 required=5 tests=[AWL=1.789, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tFFAPrG7pm4j; Thu, 14 Apr 2011 03:54:25 -0700 (PDT)
Received: from mail174.messagelabs.com (mail174.messagelabs.com [85.158.138.51]) by ietfc.amsl.com (Postfix) with SMTP id 506D0E066A; Thu, 14 Apr 2011 03:54:25 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: john.elwell@siemens-enterprise.com
X-Msg-Ref: server-15.tower-174.messagelabs.com!1302778464!10667763!1
X-StarScan-Version: 6.2.9; banners=-,-,-
X-Originating-IP: [62.134.46.9]
Received: (qmail 25602 invoked from network); 14 Apr 2011 10:54:24 -0000
Received: from unknown (HELO senmx11-mx) (62.134.46.9) by server-15.tower-174.messagelabs.com with SMTP; 14 Apr 2011 10:54:24 -0000
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx11-mx (Server) with ESMTP id 71FEC1EB83E3; Thu, 14 Apr 2011 12:54:24 +0200 (CEST)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Thu, 14 Apr 2011 12:54:24 +0200
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: "Muthu ArulMozhi Perumal (mperumal)" <mperumal@cisco.com>, "ietf@ietf.org" <ietf@ietf.org>
Date: Thu, 14 Apr 2011 12:54:23 +0200
Subject: RE: [siprec] Last Call: <draft-ietf-siprec-req-09.txt> (Use Cases andRequirements	for SIP-based Media Recording (SIPREC))	toInformational RFC
Thread-Topic: [siprec] Last Call: <draft-ietf-siprec-req-09.txt> (Use Cases andRequirements	for SIP-based Media Recording (SIPREC))	toInformational RFC
Thread-Index: Acv0WYBeRuGjGNBtTZSHeqn78QP5xwGEv6YwAAlHtwA=
Message-ID: <A444A0F8084434499206E78C106220CA0875EB5A4E@MCHP058A.global-ad.net>
References: <20110406125020.17538.70016.idtracker@localhost> <1D062974A4845E4D8A343C65380492020533BB70@XMB-BGL-414.cisco.com>
In-Reply-To: <1D062974A4845E4D8A343C65380492020533BB70@XMB-BGL-414.cisco.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
Cc: "siprec@ietf.org" <siprec@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 Apr 2011 10:54:26 -0000

=20

> -----Original Message-----
> From: siprec-bounces@ietf.org=20
> [mailto:siprec-bounces@ietf.org] On Behalf Of Muthu ArulMozhi=20
> Perumal (mperumal)
> Sent: 14 April 2011 07:34
> To: ietf@ietf.org
> Cc: siprec@ietf.org
> Subject: Re: [siprec] Last Call:=20
> <draft-ietf-siprec-req-09.txt> (Use Cases andRequirements for=20
> SIP-based Media Recording (SIPREC)) toInformational RFC
>=20
> I've one major comment. It draft discusses synchronization between the
> recorded media streams and synchronized playback, which seem important
> for certain applications:
>=20
> <snip>
> Some applications require the recording of more than one media stream,
> possibly of different types. Media are synchronized, either at storage
> or at playback.
> </snip>
>=20
> However, in the requirements section it doesn't seem REQ-022=20
> and REQ-023
> are all that are need and sufficient to achieve this with needed
> precision. So, I would suggest adding another requirement as follows:
> The mechanism MUST provide means for facilitating=20
> synchronization of the
> recorded media streams and metadata either at storage or at playback.
> This includes, but not limited to, the information needed as=20
> per REQ-022
> and REQ-023.
[JRE] This seems a reasonable addition. I wonder if the new requirement (fi=
rst sentence only) is sufficient as a **replacement** for REQ-022 and REQ-0=
23. On reading REQ-022 and REQ-023 again, it is not so clear what their pur=
pose was, and they seem to be more like a solution than a requirement. One =
purpose would certainly be that covered by Muthu's new requirement. Was the=
re any other purpose?

John

>=20
> A nitpick:
> Use Case 8
> In cases where calls inside or between branches must be recorded, a
> centralized recording system in data centers together with telephony
> infrastructure (e.g. PBX) me deployed.
>=20
> s/me/may be
>=20
> Muthu
>=20
> |-----Original Message-----
> |From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> Behalf Of The IESG
> |Sent: Wednesday, April 06, 2011 6:20 PM
> |To: IETF-Announce
> |Cc: siprec@ietf.org
> |Subject: [siprec] Last Call: <draft-ietf-siprec-req-09.txt>=20
> (Use Cases
> andRequirements for SIP-based
> |Media Recording (SIPREC)) toInformational RFC
> |
> |
> |The IESG has received a request from the SIP Recording WG (siprec) to
> |consider the following document:
> |- 'Use Cases and Requirements for SIP-based Media Recording (SIPREC)'
> |  <draft-ietf-siprec-req-09.txt> as an Informational RFC
> |
> |The IESG plans to make a decision in the next few weeks, and solicits
> |final comments on this action. Please send substantive=20
> comments to the
> |ietf@ietf.org mailing lists by 2011-04-20. 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.
> |
> |The file can be obtained via
> |http://datatracker.ietf.org/doc/draft-ietf-siprec-req/
> |
> |IESG discussion can be tracked via
> |http://datatracker.ietf.org/doc/draft-ietf-siprec-req/
> |
> |
> |
> |No IPR declarations have been submitted directly on this I-D.
> |_______________________________________________
> |siprec mailing list
> |siprec@ietf.org
> |https://www.ietf.org/mailman/listinfo/siprec
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec
> =

From housley@vigilsec.com  Thu Apr 14 05:14:46 2011
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 8A33AE0700 for <ietf@ietfc.amsl.com>; Thu, 14 Apr 2011 05:14:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.743
X-Spam-Level: 
X-Spam-Status: No, score=-103.743 tagged_above=-999 required=5 tests=[AWL=0.744, BAYES_00=-2.599, GB_I_INVITATION=-2, SARE_NETPROD=0.111, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pNOf8VGFTgqn for <ietf@ietfc.amsl.com>; Thu, 14 Apr 2011 05:14:45 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfc.amsl.com (Postfix) with ESMTP id A9915E06FA for <ietf@ietf.org>; Thu, 14 Apr 2011 05:14:45 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 8D38EF2407C for <ietf@ietf.org>; Thu, 14 Apr 2011 08:14: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 EUK7nkrSXA11 for <ietf@ietf.org>; Thu, 14 Apr 2011 08:14:44 -0400 (EDT)
Received: from [192.168.9.212] (unknown [12.54.159.133]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id DA704F24075 for <ietf@ietf.org>; Thu, 14 Apr 2011 08:14:45 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Applied Networking Research Prize
Date: Thu, 14 Apr 2011 08:14:43 -0400
Message-Id: <D8770D9A-C1CE-442A-AAF1-8F3C9E3F5D72@vigilsec.com>
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: Thu, 14 Apr 2011 12:14:46 -0000

I wanted to make sure you were all aware of this opportunity to =
recognize contributions to networking.

Russ


------


                 CALL FOR NOMINATIONS:

        APPLIED NETWORKING RESEARCH PRIZE (ANRP)


*** Apply until May 8, 2011 for the ANR Prize for IETF-81,
*** July 24-29, 2011 in Quebec City, Canada!

The Applied Networking Research Prize (ANRP) is awarded for
recent results in applied networking research that are relevant
for transitioning into shipping Internet products and related
standardization efforts. Researchers with relevant, recently
published results are encouraged to apply for this prize, which
will offer them the opportunity to present and discuss their work
with the engineers, network operators, policy makers and
scientists that participate in the Internet Engineering Task
Force (IETF) and its research arm, the Internet Research Task
Force (IRTF). Third-party nominations for this prize are also
encouraged. The goal of the Applied Networking Research Prize
(ANRP) is to recognize the best new ideas in networking, and
bring them to the IETF and IRTF especially in cases where they
would not otherwise see much exposure or discussion.

The Applied Networking Research Prize (ANRP) consists of:

* cash prize of $500 (USD)

* invited talk at the IRTF Open Meeting

* travel grant to attend the week-long IETF meeting
  (airfare, hotel, registration, stipend)

* recognition at the IETF plenary

* invitation to related social activities

* potential for additional travel grants to future IETF
  meetings, based on community feedback

The Applied Networking Research Prize (ANRP) will be awarded
three times per year, in conjunction with the three annual IETF
meetings.


HOW TO APPLY

Applicants must nominate a peer-reviewed, recently-published,
original journal, conference or workshop paper. Both self
nominations (nominating one's own paper) and third-party
nominations (nominating someone else's paper) are encouraged. The
nominee must be one of the main authors of the nominated paper.

The nominated paper should provide a scientific foundation for
possible future IETF engineering work or IRTF experimentation,
analyze the behavior of Internet protocols in operational
deployments or realistic testbeds, make an important contribution
to the understanding of Internet scalability, performance,
reliability, security or capability, or otherwise be of relevance
to ongoing or future IETF or IRTF activities.

Applicants must briefly describe how the nominated paper relates
to these goals, and are encouraged to describe how presentation
of these research results will foster their transition into new
IETF engineering or IRTF experimentation, or otherwise seed new
activities that will have an impact on the real-world Internet.

The goal of the Applied Networking Research Prize (ANRP) is to
foster the transitioning of research results into real-world
benefits for the Internet. Therefore, applicants must indicate
that they (or the nominee, in case of third-party applications)
are available to attend the respective IETF meeting in person and
in its entirety.

Applications must include:

* the name and email address of the nominee

* a reference to the published nominated paper

* a PDF copy of the nominated paper

* a statement that describes how the nominated paper
  fulfills the goals of the award

* a statement that the nominee is available to attend the
  respective IETF meeting in person and in its entirety

* a brief biography or CV of the nominee

* optionally, any other supporting information (link to
  nominee's web site, etc.)

*** Applications are submitted by email to anrp@isoc.org. ***


SELECTION PROCESS

A small selection committee comprised of individuals
knowledgeable about the IRTF, IETF and the broader networking
research community will evaluate the submissions against these
selection criteria. The goal is to select 1-2 submissions for the
Applied Networking Research Prize (ANRP) during each application
period. All applicants will be notified by email.


IMPORTANT DATES

Applications open:      April 11, 2011
Applications close:     May 8, 2011
Notifications:          May 31, 2011
IETF-81 Meeting:        July 24-29, 2011


SPONSORS

The Applied Networking Research Prize (ANRP) is supported by the
Internet Society (ISOC), as part of its Internet Research Award
Programme, in coordination with the Internet Research Task Force
(IRTF).


From Leon.Portman@nice.com  Thu Apr 14 05:18:41 2011
Return-Path: <Leon.Portman@nice.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id A3225E0735; Thu, 14 Apr 2011 05:18:41 -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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cjQgQ1fMi75e; Thu, 14 Apr 2011 05:18:40 -0700 (PDT)
Received: from mailil.nice.com (tlvexc07.nice.com [192.114.148.38]) by ietfc.amsl.com (Postfix) with ESMTP id E6534E06E5; Thu, 14 Apr 2011 05:18:38 -0700 (PDT)
Received: from TLVMBX01.nice.com ([192.168.253.242]) by tlvcas01.nice.com ([192.168.253.111]) with mapi; Thu, 14 Apr 2011 15:18:37 +0300
From: Leon Portman <Leon.Portman@nice.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>, "Muthu ArulMozhi Perumal (mperumal)" <mperumal@cisco.com>, "ietf@ietf.org" <ietf@ietf.org>
Date: Thu, 14 Apr 2011 15:18:36 +0300
Subject: RE: [siprec] Last Call: <draft-ietf-siprec-req-09.txt> (Use	Cases andRequirements	for SIP-based Media Recording	(SIPREC))	toInformational RFC
Thread-Topic: [siprec] Last Call: <draft-ietf-siprec-req-09.txt> (Use	Cases andRequirements	for SIP-based Media Recording	(SIPREC))	toInformational RFC
Thread-Index: Acv0WYBeRuGjGNBtTZSHeqn78QP5xwGEv6YwAAlHtwAAAvtH0A==
Message-ID: <07465C1D981ABC41A344374066AE1A2C38AB73D00B@TLVMBX01.nice.com>
References: <20110406125020.17538.70016.idtracker@localhost> <1D062974A4845E4D8A343C65380492020533BB70@XMB-BGL-414.cisco.com> <A444A0F8084434499206E78C106220CA0875EB5A4E@MCHP058A.global-ad.net>
In-Reply-To: <A444A0F8084434499206E78C106220CA0875EB5A4E@MCHP058A.global-ad.net>
Accept-Language: en-US, he-IL
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, he-IL
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "siprec@ietf.org" <siprec@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 Apr 2011 12:18:41 -0000

Actually REQ-022 and REQ-023 describing not only requirement to synchronize=
 between different media streams but more importantly ability to relate the=
m to real world (wall) clock. It is not only important to playback them cor=
rectly but also to know when it was said.
One example is continue trading after closing hour (even for one second is =
not allowed)

And if these media are synchronized to wall clock then they are also synchr=
onized between them thus I am not sure if we need this additional requireme=
nt.

Thanks

Leon

-----Original Message-----
From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf Of=
 Elwell, John
Sent: Thursday, April 14, 2011 1:54 PM
To: Muthu ArulMozhi Perumal (mperumal); ietf@ietf.org
Cc: siprec@ietf.org
Subject: Re: [siprec] Last Call: <draft-ietf-siprec-req-09.txt> (Use Cases =
andRequirements for SIP-based Media Recording (SIPREC)) toInformational RFC


=20

> -----Original Message-----
> From: siprec-bounces@ietf.org
> [mailto:siprec-bounces@ietf.org] On Behalf Of Muthu ArulMozhi Perumal=20
> (mperumal)
> Sent: 14 April 2011 07:34
> To: ietf@ietf.org
> Cc: siprec@ietf.org
> Subject: Re: [siprec] Last Call:=20
> <draft-ietf-siprec-req-09.txt> (Use Cases andRequirements for=20
> SIP-based Media Recording (SIPREC)) toInformational RFC
>=20
> I've one major comment. It draft discusses synchronization between the=20
> recorded media streams and synchronized playback, which seem important=20
> for certain applications:
>=20
> <snip>
> Some applications require the recording of more than one media stream,=20
> possibly of different types. Media are synchronized, either at storage=20
> or at playback.
> </snip>
>=20
> However, in the requirements section it doesn't seem REQ-022 and=20
> REQ-023 are all that are need and sufficient to achieve this with=20
> needed precision. So, I would suggest adding another requirement as=20
> follows:
> The mechanism MUST provide means for facilitating synchronization of=20
> the recorded media streams and metadata either at storage or at=20
> playback.
> This includes, but not limited to, the information needed as per=20
> REQ-022 and REQ-023.
[JRE] This seems a reasonable addition. I wonder if the new requirement (fi=
rst sentence only) is sufficient as a **replacement** for REQ-022 and REQ-0=
23. On reading REQ-022 and REQ-023 again, it is not so clear what their pur=
pose was, and they seem to be more like a solution than a requirement. One =
purpose would certainly be that covered by Muthu's new requirement. Was the=
re any other purpose?

John

>=20
> A nitpick:
> Use Case 8
> In cases where calls inside or between branches must be recorded, a=20
> centralized recording system in data centers together with telephony=20
> infrastructure (e.g. PBX) me deployed.
>=20
> s/me/may be
>=20
> Muthu
>=20
> |-----Original Message-----
> |From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> Behalf Of The IESG
> |Sent: Wednesday, April 06, 2011 6:20 PM
> |To: IETF-Announce
> |Cc: siprec@ietf.org
> |Subject: [siprec] Last Call: <draft-ietf-siprec-req-09.txt>
> (Use Cases
> andRequirements for SIP-based
> |Media Recording (SIPREC)) toInformational RFC
> |
> |
> |The IESG has received a request from the SIP Recording WG (siprec) to=20
> |consider the following document:
> |- 'Use Cases and Requirements for SIP-based Media Recording (SIPREC)'
> |  <draft-ietf-siprec-req-09.txt> as an Informational RFC
> |
> |The IESG plans to make a decision in the next few weeks, and solicits=20
> |final comments on this action. Please send substantive
> comments to the
> |ietf@ietf.org mailing lists by 2011-04-20. Exceptionally,
> comments may
> be
> |sent to iesg@ietf.org instead. In either case, please retain the=20
> |beginning of the Subject line to allow automated sorting.
> |
> |The file can be obtained via
> |http://datatracker.ietf.org/doc/draft-ietf-siprec-req/
> |
> |IESG discussion can be tracked via
> |http://datatracker.ietf.org/doc/draft-ietf-siprec-req/
> |
> |
> |
> |No IPR declarations have been submitted directly on this I-D.
> |_______________________________________________
> |siprec mailing list
> |siprec@ietf.org
> |https://www.ietf.org/mailman/listinfo/siprec
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec
>=20
_______________________________________________
siprec mailing list
siprec@ietf.org
https://www.ietf.org/mailman/listinfo/siprec

From john.elwell@siemens-enterprise.com  Thu Apr 14 05:57:34 2011
Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id D6657E068E; Thu, 14 Apr 2011 05:57:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.869
X-Spam-Level: 
X-Spam-Status: No, score=-104.869 tagged_above=-999 required=5 tests=[AWL=1.730, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fkkQG99ZXX7J; Thu, 14 Apr 2011 05:57:33 -0700 (PDT)
Received: from mail174.messagelabs.com (mail174.messagelabs.com [85.158.138.51]) by ietfc.amsl.com (Postfix) with SMTP id 57451E065F; Thu, 14 Apr 2011 05:57:33 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: john.elwell@siemens-enterprise.com
X-Msg-Ref: server-12.tower-174.messagelabs.com!1302785852!17056843!1
X-StarScan-Version: 6.2.9; banners=-,-,-
X-Originating-IP: [62.134.46.10]
Received: (qmail 423 invoked from network); 14 Apr 2011 12:57:32 -0000
Received: from unknown (HELO senmx12-mx) (62.134.46.10) by server-12.tower-174.messagelabs.com with SMTP; 14 Apr 2011 12:57:32 -0000
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx12-mx (Server) with ESMTP id 4D7B023F03DB; Thu, 14 Apr 2011 14:57:32 +0200 (CEST)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Thu, 14 Apr 2011 14:57:32 +0200
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: Leon Portman <Leon.Portman@nice.com>, "Muthu ArulMozhi Perumal (mperumal)" <mperumal@cisco.com>, "ietf@ietf.org" <ietf@ietf.org>
Date: Thu, 14 Apr 2011 14:57:30 +0200
Subject: RE: [siprec] Last Call: <draft-ietf-siprec-req-09.txt> (Use	Cases andRequirements	for SIP-based Media Recording	(SIPREC))	toInformational RFC
Thread-Topic: [siprec] Last Call: <draft-ietf-siprec-req-09.txt> (Use	Cases andRequirements	for SIP-based Media Recording	(SIPREC))	toInformational RFC
Thread-Index: Acv0WYBeRuGjGNBtTZSHeqn78QP5xwGEv6YwAAlHtwAAAvtH0AABcMXA
Message-ID: <A444A0F8084434499206E78C106220CA0875EB5B28@MCHP058A.global-ad.net>
References: <20110406125020.17538.70016.idtracker@localhost> <1D062974A4845E4D8A343C65380492020533BB70@XMB-BGL-414.cisco.com> <A444A0F8084434499206E78C106220CA0875EB5A4E@MCHP058A.global-ad.net> <07465C1D981ABC41A344374066AE1A2C38AB73D00B@TLVMBX01.nice.com>
In-Reply-To: <07465C1D981ABC41A344374066AE1A2C38AB73D00B@TLVMBX01.nice.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
Cc: "siprec@ietf.org" <siprec@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 Apr 2011 12:57:35 -0000

Understood, but if we have wall clock time for the start of a CS, wouldn't =
that be sufficient? The new requirement would cover synchronization of all =
media start/stops relative to that time.

John (as individual)
=20

> -----Original Message-----
> From: Leon Portman [mailto:Leon.Portman@nice.com]=20
> Sent: 14 April 2011 13:19
> To: Elwell, John; Muthu ArulMozhi Perumal (mperumal); ietf@ietf.org
> Cc: siprec@ietf.org
> Subject: RE: [siprec] Last Call:=20
> <draft-ietf-siprec-req-09.txt> (Use Cases andRequirements for=20
> SIP-based Media Recording (SIPREC)) toInformational RFC
>=20
> Actually REQ-022 and REQ-023 describing not only requirement=20
> to synchronize between different media streams but more=20
> importantly ability to relate them to real world (wall)=20
> clock. It is not only important to playback them correctly=20
> but also to know when it was said.
> One example is continue trading after closing hour (even for=20
> one second is not allowed)
>=20
> And if these media are synchronized to wall clock then they=20
> are also synchronized between them thus I am not sure if we=20
> need this additional requirement.
>=20
> Thanks
>=20
> Leon
>=20
> -----Original Message-----
> From: siprec-bounces@ietf.org=20
> [mailto:siprec-bounces@ietf.org] On Behalf Of Elwell, John
> Sent: Thursday, April 14, 2011 1:54 PM
> To: Muthu ArulMozhi Perumal (mperumal); ietf@ietf.org
> Cc: siprec@ietf.org
> Subject: Re: [siprec] Last Call:=20
> <draft-ietf-siprec-req-09.txt> (Use Cases andRequirements for=20
> SIP-based Media Recording (SIPREC)) toInformational RFC
>=20
>=20
> =20
>=20
> > -----Original Message-----
> > From: siprec-bounces@ietf.org
> > [mailto:siprec-bounces@ietf.org] On Behalf Of Muthu=20
> ArulMozhi Perumal=20
> > (mperumal)
> > Sent: 14 April 2011 07:34
> > To: ietf@ietf.org
> > Cc: siprec@ietf.org
> > Subject: Re: [siprec] Last Call:=20
> > <draft-ietf-siprec-req-09.txt> (Use Cases andRequirements for=20
> > SIP-based Media Recording (SIPREC)) toInformational RFC
> >=20
> > I've one major comment. It draft discusses synchronization=20
> between the=20
> > recorded media streams and synchronized playback, which=20
> seem important=20
> > for certain applications:
> >=20
> > <snip>
> > Some applications require the recording of more than one=20
> media stream,=20
> > possibly of different types. Media are synchronized, either=20
> at storage=20
> > or at playback.
> > </snip>
> >=20
> > However, in the requirements section it doesn't seem REQ-022 and=20
> > REQ-023 are all that are need and sufficient to achieve this with=20
> > needed precision. So, I would suggest adding another requirement as=20
> > follows:
> > The mechanism MUST provide means for facilitating=20
> synchronization of=20
> > the recorded media streams and metadata either at storage or at=20
> > playback.
> > This includes, but not limited to, the information needed as per=20
> > REQ-022 and REQ-023.
> [JRE] This seems a reasonable addition. I wonder if the new=20
> requirement (first sentence only) is sufficient as a=20
> **replacement** for REQ-022 and REQ-023. On reading REQ-022=20
> and REQ-023 again, it is not so clear what their purpose was,=20
> and they seem to be more like a solution than a requirement.=20
> One purpose would certainly be that covered by Muthu's new=20
> requirement. Was there any other purpose?
>=20
> John
>=20
> >=20
> > A nitpick:
> > Use Case 8
> > In cases where calls inside or between branches must be recorded, a=20
> > centralized recording system in data centers together with=20
> telephony=20
> > infrastructure (e.g. PBX) me deployed.
> >=20
> > s/me/may be
> >=20
> > Muthu
> >=20
> > |-----Original Message-----
> > |From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> > Behalf Of The IESG
> > |Sent: Wednesday, April 06, 2011 6:20 PM
> > |To: IETF-Announce
> > |Cc: siprec@ietf.org
> > |Subject: [siprec] Last Call: <draft-ietf-siprec-req-09.txt>
> > (Use Cases
> > andRequirements for SIP-based
> > |Media Recording (SIPREC)) toInformational RFC
> > |
> > |
> > |The IESG has received a request from the SIP Recording WG=20
> (siprec) to=20
> > |consider the following document:
> > |- 'Use Cases and Requirements for SIP-based Media=20
> Recording (SIPREC)'
> > |  <draft-ietf-siprec-req-09.txt> as an Informational RFC
> > |
> > |The IESG plans to make a decision in the next few weeks,=20
> and solicits=20
> > |final comments on this action. Please send substantive
> > comments to the
> > |ietf@ietf.org mailing lists by 2011-04-20. Exceptionally,
> > comments may
> > be
> > |sent to iesg@ietf.org instead. In either case, please retain the=20
> > |beginning of the Subject line to allow automated sorting.
> > |
> > |The file can be obtained via
> > |http://datatracker.ietf.org/doc/draft-ietf-siprec-req/
> > |
> > |IESG discussion can be tracked via
> > |http://datatracker.ietf.org/doc/draft-ietf-siprec-req/
> > |
> > |
> > |
> > |No IPR declarations have been submitted directly on this I-D.
> > |_______________________________________________
> > |siprec mailing list
> > |siprec@ietf.org
> > |https://www.ietf.org/mailman/listinfo/siprec
> > _______________________________________________
> > siprec mailing list
> > siprec@ietf.org
> > https://www.ietf.org/mailman/listinfo/siprec
> >=20
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec
> =

From john-ietf@jck.com  Thu Apr 14 06:10:32 2011
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 42CA9E0762 for <ietf@ietfc.amsl.com>; Thu, 14 Apr 2011 06:10: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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1VY7aIsYzi4C for <ietf@ietfc.amsl.com>; Thu, 14 Apr 2011 06:10:31 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfc.amsl.com (Postfix) with ESMTP id E8926E073A for <ietf@ietf.org>; Thu, 14 Apr 2011 06:10:30 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QAMJX-000EjO-4U; Thu, 14 Apr 2011 09:10:27 -0400
Date: Thu, 14 Apr 2011 09:10:26 -0400
From: John C Klensin <john-ietf@jck.com>
To: Bob Hinden <bob.hinden@gmail.com>, Olaf Kolkman <olaf@NLnetLabs.nl>
Subject: Re: IAOC: delegating ex-officio responsibility
Message-ID: <5419FA805EF52E79D7822966@PST.JCK.COM>
In-Reply-To: <84D6568B-18C9-47B2-A457-C51C2FB3351F@gmail.com>
References: <2BE582FA-2682-4232-9D83-23A03F01A0DB@NLnetLabs.nl> <6.2.5.6.2.20110330073936.0e1899d0@resistor.net> <E2E41FDE-3818-4513-9933-CB1E0326B43E@nlnetlabs.nl> <6.2.5.6.2.20110330113947.0c948bc0@resistor.net> <4D942843.4060804@gmail.com> <6.2.5.6.2.20110331120351.09488990@resistor.net> <4D955661.8050502@gmail.com> <9C81C0F6-3ABE-4479-8C5E-C20C486D052A@gmail.com> <82A347CC-BB19-4A73-8E8A-924FBAA92A5F@NLnetLabs.nl> <84D6568B-18C9-47B2-A457-C51C2FB3351F@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 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: Thu, 14 Apr 2011 13:10:32 -0000

--On Wednesday, April 13, 2011 11:19 -0700 Bob Hinden
<bob.hinden@gmail.com> wrote:

> Olaf,
> 
> On Apr 2, 2011, at 1:28 AM, Olaf Kolkman wrote:
> 
>> 
>> [as editor:]
>> 
>> It seems that the high order bit of this discussion circles
>> around the question on whether it a requirement for the IETF
>> Chair to have a voting position in order to effectively
>> perform oversight. Once we figured out where we want to go
>> with that we can think about delegation by the chair vs
>> appointment by the bodies and the implementation details with
>> respect to the trust.
> 
> For the record, I don't agree with this summary.  That is, I
> still question the basic assumption in the proposal.  We have
> "running code" in the IASA model and it appears to work
> reasonable well.  Not perfect, of course.  In particular I
> think that having the IETF chair, IAB chair, and ISOC
> president as voting members of the IAOC (and IETF Trust) has
> worked very well.  It makes them an active part of decisions
> the IAOC and IETF Trust are making and helps keep the IAOC
> from getting disconnected from the community.  It also makes
> them share the responsibility for decisions by having their
> vote be publicly recorded.  
>...

Bob,

I think you and Olaf (and myself and others) are addressing two
rather different questions.  Your note seems to assume the
question is "how to make the IAOC work better".  Your answer, if
I understand it correctly, is "it works fairly well today isn't
broken, let's not fix it".  If that were the question, I'd agree.

But, remembering that the IASA has only the purpose of making
the extended IETF (including the IAB) work more efficiently, I
see a somewhat different question.  The roles and resource
requirements of the IAB and IETF Chairs have expanded
dramatically over the last several years.. expanded to the point
that the appointing bodies may soon have to choose, not among
the best people for the job, but from those who have spare time
and resources on their hands or, worse, who work for
organizations who see particular value in having one of their
employees in those positions.  We have been lucky so far in
finding very good people despite those pressures, but we can't
count on its lasting.

That situation suggests to me that we should be asking the
question of how we can reduce the absolute requirements
associated with the IAB and IETF Chair positions.  If whomever
is in those positions has the time, resources, and interest to
also serve on the IAOC, I'm very much in favor of that.   But,
if an individual --or the Nomcom-- have to choose between
exclusion of the best candidate because there aren't enough
resources for him or her to do the [rest of the] Chair job _and_
the IAOC versus spreading the workload out, then I think it is
in the community's interest to have an alternative.    My
personal preference continues to be to make the decision of who
from the IAB (and potentially the IESG) serves on the IAOC be
the decision of the IAB or IESG respectively rather than using
the "delegation" model Olaf suggests but, in practice, I think
it really makes no difference because any reasonable Chair is
going to discuss those options with the relevant body.

Even if we were not worried about overall workload, we've
discovered at several recent IETF meetings that the schedule for
IAOC-related meetings keeps the IAB and IETF Chairs out of other
meetings that might, objectively, have been important for them
to attend.  So it is not clear to me that having those two
people on the IAOC in person is optimal for the community,
independent of whether or not it is desirable for IASA.

>From that point of view, the right question from the IASA/IAOC
perspective should not be "is it working well enough that there
is no internal reason to make a change" but "can this type of
change be made without serious damage".

As far as the Trust is concerned, while we couldn't change the
relationship until recently, we can now: if the linkage between
Trust and IAOC membership is interfering with the simultaneous
successful operation of the Trust and the efficient operation of
the IAB and/or IESG, let's just change it.

    john


From brian.e.carpenter@gmail.com  Thu Apr 14 08:34:42 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id A7C33E0778 for <ietf@ietfc.amsl.com>; Thu, 14 Apr 2011 08:34:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.781
X-Spam-Level: 
X-Spam-Status: No, score=-103.781 tagged_above=-999 required=5 tests=[AWL=-0.182, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D15ST6r9PUSF for <ietf@ietfc.amsl.com>; Thu, 14 Apr 2011 08:34:41 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfc.amsl.com (Postfix) with ESMTP id BCB4FE073F for <ietf@ietf.org>; Thu, 14 Apr 2011 08:34:41 -0700 (PDT)
Received: by wyb29 with SMTP id 29so1687397wyb.31 for <ietf@ietf.org>; Thu, 14 Apr 2011 08:34:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=INer0TYWbNDZi+fXeTKHw2yra9J3VTpnbL5KvG+YwxQ=; b=hfWVwMCfWcsK0d2EfZs2WrnNrA8usgAeDjRiCry83Jzqy6nSKTKnCMO7se6b6vIxbO 9wC/DqzjzsJYD4kzyC6CzGgaIeabEy33lO3kKTi3uNWq5EEM3b5yD9WL+OuDDaUL4K/+ RURnOzUK0w7y+xpOu7LnQZcbmlqBQ2FW+G8u4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=HnvUZB9pF8wmfCdzFHK6B4fLmCsvXqz/2a6jJPeHHkzexYXKbEwpCocxzQQ3G0cUBb 4H4sLzNhb/uiyC5sqxLfRQwosZEFm3UuVCwXD7NTH/lE84iwo+CZci6u6jyu8jLPHPAn 2AMyRLhV0H0a+eijQeOwhSm7YhoiQE3iJhnxU=
Received: by 10.216.221.158 with SMTP id r30mr6781046wep.50.1302795281050; Thu, 14 Apr 2011 08:34:41 -0700 (PDT)
Received: from [192.168.1.65] (host81-159-213-38.range81-159.btcentralplus.com [81.159.213.38]) by mx.google.com with ESMTPS id l24sm1069830wbc.30.2011.04.14.08.34.39 (version=SSLv3 cipher=OTHER); Thu, 14 Apr 2011 08:34:40 -0700 (PDT)
Message-ID: <4DA71408.3090704@gmail.com>
Date: Fri, 15 Apr 2011 03:34:32 +1200
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: IAOC: delegating ex-officio responsibility
References: <2BE582FA-2682-4232-9D83-23A03F01A0DB@NLnetLabs.nl>	<6.2.5.6.2.20110330073936.0e1899d0@resistor.net>	<E2E41FDE-3818-4513-9933-CB1E0326B43E@nlnetlabs.nl>	<6.2.5.6.2.20110330113947.0c948bc0@resistor.net>	<4D942843.4060804@gmail.com>	<6.2.5.6.2.20110331120351.09488990@resistor.net>	<4D955661.8050502@gmail.com>	<9C81C0F6-3ABE-4479-8C5E-C20C486D052A@gmail.com>	<82A347CC-BB19-4A73-8E8A-924FBAA92A5F@NLnetLabs.nl>	<84D6568B-18C9-47B2-A457-C51C2FB3351F@gmail.com> <5419FA805EF52E79D7822966@PST.JCK.COM>
In-Reply-To: <5419FA805EF52E79D7822966@PST.JCK.COM>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Bob Hinden <bob.hinden@gmail.com>, 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: Thu, 14 Apr 2011 15:34:42 -0000

John,

On 2011-04-15 01:10, John C Klensin wrote:
...
> But, remembering that the IASA has only the purpose of making
> the extended IETF (including the IAB) work more efficiently, I
> see a somewhat different question.  The roles and resource
> requirements of the IAB and IETF Chairs have expanded
> dramatically over the last several years.. 

We really need to understand that better, and the underlying
reasons for it, in some detail. I don't think that cherry-picking
parts of the jobs to be delegated should be the starting point.
We really need to start by reviewing all the tasks together and
then decide what should be changed. I'd really like to hear from
Olaf, Bernard and Russ what has changed in the workload in the
last few years. You are of course correct that if the workload
is constantly increasing, it will make NomCom's task very hard.

Certainly the IASA/IAD/IAOC reorganisation produced a noticeable
reduction in the IETF Chair workload, but what has changed since
http://tools.ietf.org/html/draft-carpenter-ietf-chair-tasks-00 ?
It would be good to have a similar analysis for the IAB chair role.

Regards

     Brian

From moore@network-heretics.com  Thu Apr 14 08:52:40 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id D6816E06CD for <ietf@ietfc.amsl.com>; Thu, 14 Apr 2011 08:52:40 -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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sCKDgkyHriEB for <ietf@ietfc.amsl.com>; Thu, 14 Apr 2011 08:52:39 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfc.amsl.com (Postfix) with ESMTP id 938EFE0663 for <ietf@ietf.org>; Thu, 14 Apr 2011 08:52:39 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.mail.srv.osa [10.202.2.42]) by gateway1.messagingengine.com (Postfix) with ESMTP id 840E0203C1 for <ietf@ietf.org>; Thu, 14 Apr 2011 11:52:38 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute2.internal (MEProxy); Thu, 14 Apr 2011 11:52:38 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:content-transfer-encoding:message-id:references:to; s=smtpout; bh=xDdslI/iWN/dFQKDU2iMe1LBCzg=; b=n3nWe/D7/sL9nlcwPWerUCMaSuWVS8tpRUQR9gsv1TyUyRekypmvCIXqUOt9Jq3HB+7yLW2Badr229fj3jkNimhudRRRjKqTRH3BTL5ee9ECrmFvDj9hL1B4Bs7VD7EgYH/Nhq9PHSPzaBJHNQWmYVBiPrF1tiTPi1Lh5xGFjbM=
X-Sasl-enc: hwnwJZ5z4yci0BslgQDt7X7pbwNqqbDW+Kf8yxS6rp2p 1302796358
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id E6043440B03; Thu, 14 Apr 2011 11:52:37 -0400 (EDT)
Subject: Re: Last Call: <draft-daboo-et-al-icalendar-in-xml-08.txt> (xCal: The XML format for iCalendar) to Proposed Standard
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <20110414152020.12635.714.idtracker@ietfc.amsl.com>
Date: Thu, 14 Apr 2011 11:52:37 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <9514532F-8A12-4A16-BF42-974A048BEB05@network-heretics.com>
References: <20110414152020.12635.714.idtracker@ietfc.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: Thu, 14 Apr 2011 15:52:41 -0000

I appreciate that great pains have been taken to ensure that this format =
is a dual of the standard iCalendar format, that translation can be =
performed in both directions without loss, and that at least some =
attempt has been made to specify the conversion algorithms in such a way =
that (if carefully implemented) they should continue to work with =
extensions to iCalendar.

I think it's confusing that many elements are referred to using an ICAL: =
prefix, when (a) the xml examples don't actually associate that prefix =
with a namespace, and (b) when iCal is probably a trademark of Apple.

However (and I think it's been at least 10 years since this was first =
proposed) I still find myself wondering, why is this format needed or =
even useful?    Practically speaking, I think the adoption of this =
format will only increase the burden on implementations and decrease the =
likelihood of interoperability between implementations.  It will =
increase the burden on implementations because now implementations will =
need to be able to accept, and possibly generate, two different calendar =
data formats instead of one.  =20

It will decrease interoperability because there will certainly be some =
attempts to send xCalendar data created by new implementations, to old =
implementations that only accept iCalendar data.  It will also decrease =
interoperability because, inevitably, some implementations of the =
conversion routines will fail to be sufficiently general in order to =
handle currently-undefined properties and components.   This is an =
almost inherent consequence of the likely use of XML schema description =
languages that explicitly enumerate element names, and processing =
languages that associate explicit element names with processing actions. =
  Finally it will decrease interoperability because it will no longer be =
the case that only producers and consumers of iCalendar data have to =
interoperate - it will then be necessary for producers, consumers, and =
converters to all interoperate - thus introducing more opportunities for =
both implementation bugs and version skew to create problems.

I also get the impression that the mapping of "values" or data types =
(section 3.6) between iCalendar and XML is not sufficiently general to =
permit continued interoperability across extensions.

I think that adoption of this format will in practice require that (a) =
any extensions to iCalendar to also explicitly specify how they are =
mapped into xCalendar, and (b) every, or nearly every, =
iCalendar<>xCalendar conversion product to be updated every time there =
is an extension to the iCalendar format. =20

I also suspect that converting the format to XML will encourage ad hoc =
extensions to xCalendar which might not map well to iCalendar - since =
the constraints and extension model of iCalendar will not be obvious to =
the typical XML code developer.

Use of the "XML" property in iCalendar implies that the conversion =
routine needs to know which properties are "already" defined in =
iCalendar, which either implies that iCalendar cannot be extended, or =
that different converters (knowledgable about different versions of =
iCalendar) will produce different results (some mapping unknown =
properties to the iCalendar XML property, and some mapping them to =
native iCalendar properties).

Correct conversion from iCalendar to XML appears to require the =
converter to know about the types of each of the properties even though =
these are not explicitly specified in the source iCalendar document.   =
This is problematic if new properties are defined for iCalendar, as old =
converters won't know about the types of those properties.

So, in summary, I still don't think this is worth the trouble.   =
Regardless of the application, providing multiple ways to represent the =
same information generally seems to degrade interoperability.

Keith


On Apr 14, 2011, at 11:20 AM, The IESG wrote:

>=20
> The IESG has received a request from an individual submitter to =
consider
> the following document:
> - 'xCal: The XML format for iCalendar'
>  <draft-daboo-et-al-icalendar-in-xml-08.txt> as a Proposed Standard
>=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 2011-05-12. 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
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-daboo-et-al-icalendar-in-xml/
>=20
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-daboo-et-al-icalendar-in-xml/
>=20
>=20
>=20
> No IPR declarations have been submitted directly on this I-D.
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce


From olaf@nlnetlabs.nl  Thu Apr 14 09:25:57 2011
Return-Path: <olaf@nlnetlabs.nl>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id C7B97E08B9 for <ietf@ietfc.amsl.com>; Thu, 14 Apr 2011 09:25:57 -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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PfbFeskrpJrd for <ietf@ietfc.amsl.com>; Thu, 14 Apr 2011 09:25:56 -0700 (PDT)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by ietfc.amsl.com (Postfix) with ESMTP id A24DBE087E for <ietf@ietf.org>; Thu, 14 Apr 2011 09:25:54 -0700 (PDT)
Received: from [IPv6:2001:7b8:206:1:226:bbff:fe0e:7cc7] ([IPv6:2001:7b8:206:1:226:bbff:fe0e:7cc7]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.4/8.14.4) with ESMTP id p3EGPoZL044073 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 14 Apr 2011 18:25:50 +0200 (CEST) (envelope-from olaf@nlnetlabs.nl)
Subject: Re: IAOC: delegating ex-officio responsibility
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=koi8-r
From: Olaf Kolkman <olaf@NLnetLabs.nl>
In-Reply-To: <4DA71408.3090704@gmail.com>
Date: Thu, 14 Apr 2011 18:25:43 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <A0E8E415-123E-4643-98FC-6E022A1D7517@nlnetlabs.nl>
References: <2BE582FA-2682-4232-9D83-23A03F01A0DB@NLnetLabs.nl>	<6.2.5.6.2.20110330073936.0e1899d0@resistor.net>	<E2E41FDE-3818-4513-9933-CB1E0326B43E@nlnetlabs.nl>	<6.2.5.6.2.20110330113947.0c948bc0@resistor.net>	<4D942843.4060804@gmail.com>	<6.2.5.6.2.20110331120351.09488990@resistor.net>	<4D955661.8050502@gmail.com>	<9C81C0F6-3ABE-4479-8C5E-C20C486D052A@gmail.com>	<82A347CC-BB19-4A73-8E8A-924FBAA92A5F@NLnetLabs.nl>	<84D6568B-18C9-47B2-A457-C51C2FB3351F@gmail.com> <5419FA805EF52E79D7822966@PST.JCK.COM> <4DA71408.3090704@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Pgp-Agent: GPGMail 1.3.3
X-Mailer: Apple Mail (2.1084)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]); Thu, 14 Apr 2011 18:25:50 +0200 (CEST)
Cc: John C Klensin <john-ietf@jck.com>, Bob Hinden <bob.hinden@gmail.com>, 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: Thu, 14 Apr 2011 16:25:57 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

>=20
> Certainly the IASA/IAD/IAOC reorganisation produced a noticeable
> reduction in the IETF Chair workload, but what has changed since
> http://tools.ietf.org/html/draft-carpenter-ietf-chair-tasks-00 ?
> It would be good to have a similar analysis for the IAB chair role.
>=20


Below is a copy from a note I mailed to the IAB dd Feb 17, 2011. It wis =
a variation on a note that I mailed to the Nomcom in 2009. It may not =
map exactly to what you are asking, but I believe it is close enough.

Also, my wish to remove the _must_ in the 'iChiefs must be a member of =
the IAOC' best current practice is not a cherry picking act. The IAB has =
hired secretarial assistance for the agenda keeping, todo-list =
maintenance, minutes, etc. It is pushing forward the 'programs and =
initiatives' model that allows for subgroups to do a lot of actual work =
without the chair driving that (i.e. much more formal delegation of =
activities to sub-groups with possibly external members).



> Starting off with a personal note.
> As you know the IAB chair is selected by and from the IAB membership =
on a yearly basis. I first volunteered for the role of chair in March =
2007. When I volunteered the first time I committed myself for 3 to 5 =
years (obviously subject to Nomcom and IAB decision). A minimum of 3 =
years because anything shorter is almost not worth the investment in the =
learning curve and the personal network that is needed to do the job =
effectively. Not longer than 5 years because of the fact that(much) =
longer terms tend to result in strong identification of a person with =
the role, sharpness and creativity decline, and possibly forms of =
mannerism in dealing with issues.
> =46rom my perspective the most ideal scenario was (remember I wrote =
this in 2009) that I'd be allowed by the Nomcom and the IAB to serve as =
a chair for one more year and then be around for another to allow for =
continuity. In any case I think that it would be good for the Nomcom to =
look out for 'chair material'.
> The main reason why I want to step down now is that there have been =
some developments in the NLnet Labs situation that need my attention as =
director of that organization that can not be combined with a 0.7 FTE =
that I seem to be putting in at the moment.
>=20
> As for the responsibilities of the chair.
> 	=95 A number of 'mechanical/managerial' tasks:
> 		=95 Managing and organizing the IAB work-flow both on =
architectural and organizational items
> 		=95 Setting priorities, planning activities to be =
aligned, identify actionable items and make sure next steps are taken
> 		=95 Set up various meetings, manage agendas
> 	=95 Track minutes creation and publication
> 		=95 A chair's job can be relieved by having an executive =
director that complements a chairs talents in organizing these =
activities.
> 	=95 Drive discussions
> 		=95 defining goals
> 		=95 moderate discussions
> 		=95 call consensus
> 	=95 Identify work items
> 		=95 Incoming appeals
> 		=95 Specific questions to the IAB from external bodies
> 		=95 Track (or make sure they are tracked) various =
developments that may have impact on the IETF.
> 	=95 IASA/IAOC and Trust
> 		=95 As ex-officio membership, to represent IAB (and =
IRTF) matters
> Because the chair is involved in all these activities (s)he becomes a =
de-facto information hub, besides because the chair often act as spokes =
person there isa tendency for all major organizational work items to =
gravitate towards the chair, specifically if the interests of the other =
members are mostly architectural. There are arguments that the load on =
the IAB chair is to high and it causes the job to be more than a =
half-time position (depending on personal effectively, delegation skill, =
organizational skills and the quality of an executive director[*], it =
may even be closer to 3 quarters). And I believe that there are some =
structural questions one can ask, such as in the ex-officio membership =
of the IASA/IOAC.
> If we manage to get the Programs ran as more or less autonomous motors =
that produce recommendations to the IAB it may be that the chairs job =
becomes relatively bearable.
> While I think that with the Programs we have put a good structure in =
place it will need serious efforts of the next chair and the NEW IAB to =
make working with programs part of the common mindset.
> I think, and I realize that I am biased, that an IAB chair has some of =
the following skills, properties:
> 	=95 Organizational: tracking actions, poking people, planning =
the work load. A good Executive Director can be of tremendous help
> 	=95 Moderating and motivating: The ability to herd cats where =
occasionally a cat will have its claws out.
> 	=95 Diplomatic: In inter-organizational contacts taking the =
diplomatic way to where you would like to end up.
> 	=95 Strategic: Constantly trying to up-level and see bigger =
picture while remembering that actionable progress needs to be made.
> 	=95 Open and sharing: Open to information received and conscious =
about timely sharing of that information.
> Note that I did not list technical/architectural skills in the above. =
Obviously an IAB chair needs to understand the technical issues but I do =
not believe that the IAB needs to be the 'chief architect'. While having =
an inspiring "Architect" leading the IAB would be nice I don't think it =
is a requirement. More important is that architectural work is being =
organized and the chair allows others to excel in their technical =
expertise.
> I am not saying that I had all the skills and properties above, but =
not feeling the need to be "the technical champion" and not feeling the =
pressure from my fellow members to act like one helped a great deal.
> FWIW I am committed to several IAB projects that do not automagically =
travel with the chair (e.g. RSE project and IANA strategy) and I plan to =
continue to be involved in those
> Folding these requirements with the thoughts on alignment with the =
day-job of a chair candidate and the possible willingness of an employer =
to sponsor more than half-time of a function that has fairly little =
technical return might be a challenge.
> [*] as mentioned in my other note, a dedicated (i.e. payed staff) =
Executive Director may be a great way to reduce the time efforts needed =
by an IAB chair, and other members. I should hurry to say that this is =
not mend as a comment on Dow, day-job interference plagues us all.
>=20

________________________________________________________=20

Olaf M. Kolkman                        NLnet Labs
http://www.nlnetlabs.nl/           =20
I will start to use a new PGP key (ID 0x3B6AAA64) at the beginning
of May 2011.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: This message is locally signed.
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAk2nIAgACgkQtN/ca3YJIocPVgCdEEPdzw/VTmkmgznbX73Nokan
uIIAn37ABvdLR3z7Mtu7v2FVPJXWkWgr
=3DC205
-----END PGP SIGNATURE-----

From Leon.Portman@nice.com  Thu Apr 14 09:27:17 2011
Return-Path: <Leon.Portman@nice.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 3FA32E08C9; Thu, 14 Apr 2011 09:27:17 -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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PNGVeY7KDeVj; Thu, 14 Apr 2011 09:27:16 -0700 (PDT)
Received: from mailil.nice.com (tlvexc07.nice.com [192.114.148.38]) by ietfc.amsl.com (Postfix) with ESMTP id A1E46E08DA; Thu, 14 Apr 2011 09:27:12 -0700 (PDT)
Received: from TLVMBX01.nice.com ([192.168.253.242]) by tlvcas02.nice.com ([172.18.253.6]) with mapi; Thu, 14 Apr 2011 19:27:11 +0300
From: Leon Portman <Leon.Portman@nice.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>, "Muthu ArulMozhi Perumal (mperumal)" <mperumal@cisco.com>, "ietf@ietf.org" <ietf@ietf.org>
Date: Thu, 14 Apr 2011 19:27:10 +0300
Subject: RE: [siprec] Last Call: <draft-ietf-siprec-req-09.txt> (Use	Cases andRequirements	for SIP-based Media Recording	(SIPREC))	toInformational RFC
Thread-Topic: [siprec] Last Call: <draft-ietf-siprec-req-09.txt> (Use	Cases andRequirements	for SIP-based Media Recording	(SIPREC))	toInformational RFC
Thread-Index: Acv0WYBeRuGjGNBtTZSHeqn78QP5xwGEv6YwAAlHtwAAAvtH0AABcMXAAAdJn6A=
Message-ID: <07465C1D981ABC41A344374066AE1A2C38AB73D110@TLVMBX01.nice.com>
References: <20110406125020.17538.70016.idtracker@localhost> <1D062974A4845E4D8A343C65380492020533BB70@XMB-BGL-414.cisco.com> <A444A0F8084434499206E78C106220CA0875EB5A4E@MCHP058A.global-ad.net> <07465C1D981ABC41A344374066AE1A2C38AB73D00B@TLVMBX01.nice.com> <A444A0F8084434499206E78C106220CA0875EB5B28@MCHP058A.global-ad.net>
In-Reply-To: <A444A0F8084434499206E78C106220CA0875EB5B28@MCHP058A.global-ad.net>
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: "siprec@ietf.org" <siprec@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 Apr 2011 16:27:17 -0000

I am not sure that having wall clock only for CS start is enough, especiall=
y for partial metadata update. I will prefer to have on media level

Leon

-----Original Message-----
From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]=20
Sent: Thursday, April 14, 2011 3:58 PM
To: Leon Portman; Muthu ArulMozhi Perumal (mperumal); ietf@ietf.org
Cc: siprec@ietf.org
Subject: RE: [siprec] Last Call: <draft-ietf-siprec-req-09.txt> (Use Cases =
andRequirements for SIP-based Media Recording (SIPREC)) toInformational RFC

Understood, but if we have wall clock time for the start of a CS, wouldn't =
that be sufficient? The new requirement would cover synchronization of all =
media start/stops relative to that time.

John (as individual)
=20

> -----Original Message-----
> From: Leon Portman [mailto:Leon.Portman@nice.com]
> Sent: 14 April 2011 13:19
> To: Elwell, John; Muthu ArulMozhi Perumal (mperumal); ietf@ietf.org
> Cc: siprec@ietf.org
> Subject: RE: [siprec] Last Call:=20
> <draft-ietf-siprec-req-09.txt> (Use Cases andRequirements for=20
> SIP-based Media Recording (SIPREC)) toInformational RFC
>=20
> Actually REQ-022 and REQ-023 describing not only requirement to=20
> synchronize between different media streams but more importantly=20
> ability to relate them to real world (wall) clock. It is not only=20
> important to playback them correctly but also to know when it was=20
> said.
> One example is continue trading after closing hour (even for one=20
> second is not allowed)
>=20
> And if these media are synchronized to wall clock then they are also=20
> synchronized between them thus I am not sure if we need this=20
> additional requirement.
>=20
> Thanks
>=20
> Leon
>=20
> -----Original Message-----
> From: siprec-bounces@ietf.org
> [mailto:siprec-bounces@ietf.org] On Behalf Of Elwell, John
> Sent: Thursday, April 14, 2011 1:54 PM
> To: Muthu ArulMozhi Perumal (mperumal); ietf@ietf.org
> Cc: siprec@ietf.org
> Subject: Re: [siprec] Last Call:=20
> <draft-ietf-siprec-req-09.txt> (Use Cases andRequirements for=20
> SIP-based Media Recording (SIPREC)) toInformational RFC
>=20
>=20
> =20
>=20
> > -----Original Message-----
> > From: siprec-bounces@ietf.org
> > [mailto:siprec-bounces@ietf.org] On Behalf Of Muthu
> ArulMozhi Perumal
> > (mperumal)
> > Sent: 14 April 2011 07:34
> > To: ietf@ietf.org
> > Cc: siprec@ietf.org
> > Subject: Re: [siprec] Last Call:=20
> > <draft-ietf-siprec-req-09.txt> (Use Cases andRequirements for=20
> > SIP-based Media Recording (SIPREC)) toInformational RFC
> >=20
> > I've one major comment. It draft discusses synchronization
> between the
> > recorded media streams and synchronized playback, which
> seem important
> > for certain applications:
> >=20
> > <snip>
> > Some applications require the recording of more than one
> media stream,
> > possibly of different types. Media are synchronized, either
> at storage
> > or at playback.
> > </snip>
> >=20
> > However, in the requirements section it doesn't seem REQ-022 and
> > REQ-023 are all that are need and sufficient to achieve this with=20
> > needed precision. So, I would suggest adding another requirement as
> > follows:
> > The mechanism MUST provide means for facilitating
> synchronization of
> > the recorded media streams and metadata either at storage or at=20
> > playback.
> > This includes, but not limited to, the information needed as per
> > REQ-022 and REQ-023.
> [JRE] This seems a reasonable addition. I wonder if the new=20
> requirement (first sentence only) is sufficient as a
> **replacement** for REQ-022 and REQ-023. On reading REQ-022 and=20
> REQ-023 again, it is not so clear what their purpose was, and they=20
> seem to be more like a solution than a requirement.
> One purpose would certainly be that covered by Muthu's new=20
> requirement. Was there any other purpose?
>=20
> John
>=20
> >=20
> > A nitpick:
> > Use Case 8
> > In cases where calls inside or between branches must be recorded, a=20
> > centralized recording system in data centers together with
> telephony
> > infrastructure (e.g. PBX) me deployed.
> >=20
> > s/me/may be
> >=20
> > Muthu
> >=20
> > |-----Original Message-----
> > |From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> > Behalf Of The IESG
> > |Sent: Wednesday, April 06, 2011 6:20 PM
> > |To: IETF-Announce
> > |Cc: siprec@ietf.org
> > |Subject: [siprec] Last Call: <draft-ietf-siprec-req-09.txt>
> > (Use Cases
> > andRequirements for SIP-based
> > |Media Recording (SIPREC)) toInformational RFC
> > |
> > |
> > |The IESG has received a request from the SIP Recording WG
> (siprec) to
> > |consider the following document:
> > |- 'Use Cases and Requirements for SIP-based Media
> Recording (SIPREC)'
> > |  <draft-ietf-siprec-req-09.txt> as an 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 2011-04-20. Exceptionally,
> > comments may
> > be
> > |sent to iesg@ietf.org instead. In either case, please retain the=20
> > |beginning of the Subject line to allow automated sorting.
> > |
> > |The file can be obtained via
> > |http://datatracker.ietf.org/doc/draft-ietf-siprec-req/
> > |
> > |IESG discussion can be tracked via
> > |http://datatracker.ietf.org/doc/draft-ietf-siprec-req/
> > |
> > |
> > |
> > |No IPR declarations have been submitted directly on this I-D.
> > |_______________________________________________
> > |siprec mailing list
> > |siprec@ietf.org
> > |https://www.ietf.org/mailman/listinfo/siprec
> > _______________________________________________
> > siprec mailing list
> > siprec@ietf.org
> > https://www.ietf.org/mailman/listinfo/siprec
> >=20
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec
>=20

From bob.hinden@gmail.com  Thu Apr 14 09:31:46 2011
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 21932E089E for <ietf@ietfc.amsl.com>; Thu, 14 Apr 2011 09:31:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.932
X-Spam-Level: 
X-Spam-Status: No, score=-103.932 tagged_above=-999 required=5 tests=[AWL=-0.333, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LJd8lTnuQJzd for <ietf@ietfc.amsl.com>; Thu, 14 Apr 2011 09:31:45 -0700 (PDT)
Received: from mail-px0-f182.google.com (mail-px0-f182.google.com [209.85.212.182]) by ietfc.amsl.com (Postfix) with ESMTP id 32F0CE0807 for <ietf@ietf.org>; Thu, 14 Apr 2011 09:31:45 -0700 (PDT)
Received: by pxi20 with SMTP id 20so1125837pxi.27 for <ietf@ietf.org>; Thu, 14 Apr 2011 09:31:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=fekuSGrWvbGAZC9SI9971gyvunX0lUfmKJFIya8krrU=; b=twV20wa0LXWzhAgsP16eS4rvz+Z5gR4g1Wd+f8N9j5drwbghgERrlhLtPRqm74rKLo EyGI6k+fZwh0oc19LAnC5isdGd6CqYbqjs9iamObM1QmbQj551hw1pzXrTlzylyTxl1P YWD1B+/tJALBg511UpYa+q3+v6sAXRpoG+z7Y=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=ejfZfqw9hswDb1KH8fFbHXpkRKUhLFj0S2yGM037wuFxinxGGRLXyzx3cMpnAZui/e rdFDlP4h5z8GCg90D467NPEo2vP2XuxbxdoSeS0IooQsTTzk2bKA19bgGEJFnhezR907 Mt2gMJ76Xe3HOwXyuvWlIiUMyd4P/Ss0jGQxM=
Received: by 10.68.27.4 with SMTP id p4mr652830pbg.171.1302798704669; Thu, 14 Apr 2011 09:31:44 -0700 (PDT)
Received: from [10.0.0.37] (c-24-130-226-27.hsd1.ca.comcast.net [24.130.226.27]) by mx.google.com with ESMTPS id z10sm2504916wfj.3.2011.04.14.09.31.42 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 14 Apr 2011 09:31:43 -0700 (PDT)
Subject: Re: IAOC: delegating ex-officio responsibility
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <4DA71408.3090704@gmail.com>
Date: Thu, 14 Apr 2011 09:31:41 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <1581BE81-0C64-4E3F-B85C-B57287DDF7DD@gmail.com>
References: <2BE582FA-2682-4232-9D83-23A03F01A0DB@NLnetLabs.nl>	<6.2.5.6.2.20110330073936.0e1899d0@resistor.net>	<E2E41FDE-3818-4513-9933-CB1E0326B43E@nlnetlabs.nl>	<6.2.5.6.2.20110330113947.0c948bc0@resistor.net>	<4D942843.4060804@gmail.com>	<6.2.5.6.2.20110331120351.09488990@resistor.net>	<4D955661.8050502@gmail.com>	<9C81C0F6-3ABE-4479-8C5E-C20C486D052A@gmail.com>	<82A347CC-BB19-4A73-8E8A-924FBAA92A5F@NLnetLabs.nl>	<84D6568B-18C9-47B2-A457-C51C2FB3351F@gmail.com> <5419FA805EF52E79D7822966@PST.JCK.COM> <4DA71408.3090704@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1082)
Cc: John C Klensin <john-ietf@jck.com>, Bob Hinden <bob.hinden@gmail.com>, 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: Thu, 14 Apr 2011 16:31:46 -0000

Brian,

On Apr 14, 2011, at 8:34 AM, Brian E Carpenter wrote:

> John,
>=20
> On 2011-04-15 01:10, John C Klensin wrote:
> ...
>> But, remembering that the IASA has only the purpose of making
>> the extended IETF (including the IAB) work more efficiently, I
>> see a somewhat different question.  The roles and resource
>> requirements of the IAB and IETF Chairs have expanded
>> dramatically over the last several years..=20
>=20
> We really need to understand that better, and the underlying
> reasons for it, in some detail. I don't think that cherry-picking
> parts of the jobs to be delegated should be the starting point.
> We really need to start by reviewing all the tasks together and
> then decide what should be changed. I'd really like to hear from
> Olaf, Bernard and Russ what has changed in the workload in the
> last few years. You are of course correct that if the workload
> is constantly increasing, it will make NomCom's task very hard.
>=20
> Certainly the IASA/IAD/IAOC reorganisation produced a noticeable
> reduction in the IETF Chair workload, but what has changed since
> http://tools.ietf.org/html/draft-carpenter-ietf-chair-tasks-00 ?
> It would be good to have a similar analysis for the IAB chair role.

+1

If there is a systemic problem, let's talk about that before proposing =
point solutions.  The overload problem also affects other leadership =
positions such as the IESG AD members. =20

Bob




From bob.hinden@gmail.com  Thu Apr 14 09:52:02 2011
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 4EE6FE081E for <ietf@ietfc.amsl.com>; Thu, 14 Apr 2011 09:52:02 -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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 22sIArtQbiMM for <ietf@ietfc.amsl.com>; Thu, 14 Apr 2011 09:52:01 -0700 (PDT)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by ietfc.amsl.com (Postfix) with ESMTP id 23244E0716 for <ietf@ietf.org>; Thu, 14 Apr 2011 09:52:01 -0700 (PDT)
Received: by pzk30 with SMTP id 30so702879pzk.31 for <ietf@ietf.org>; Thu, 14 Apr 2011 09:52:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=b0ZDP8Lx8ANGAwD/C2v0hddUsVy0AaSy6B8QOHs271s=; b=WuPrCtH6tZDtnQSq6D/oXC5yjaiBn5sG6tEdTQkEpO6/7o/QZZf1Djcu552kpLIBTI 3FqLv+l5FjI1gc+g9fLbnTmwpvpR8AvPUxTakooNHTFeIFI2K1H524ghpJTsMumU0Bt3 APv6IhfsGey8RDQ6uCJ/rjBL/AV3xfy7cg4Zs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=gDMzVZA2m/ouYiEs8sAI3uPuIpsYH4NRxy2SaJjJcoSzEjOS74rPR6VqsH739Wxcmw n/DFeD1o5OY7NdG1wHum4h4bRAww5v0ScBCmN7L2EPuvGfOpGbiQxBhNhkxAfrTR4crr 9R0BVTONsZIvt+aE2Sfu8YioYKNq85sQOF1GU=
Received: by 10.143.21.1 with SMTP id y1mr276018wfi.441.1302799919689; Thu, 14 Apr 2011 09:51:59 -0700 (PDT)
Received: from [10.0.0.37] (c-24-130-226-27.hsd1.ca.comcast.net [24.130.226.27]) by mx.google.com with ESMTPS id p40sm2517332wfc.17.2011.04.14.09.51.58 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 14 Apr 2011 09:51:58 -0700 (PDT)
Subject: Re: IAOC: delegating ex-officio responsibility
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <5419FA805EF52E79D7822966@PST.JCK.COM>
Date: Thu, 14 Apr 2011 09:51:57 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <DAC0FFD9-9B3B-4726-B56B-5E9BE5A5F1D1@gmail.com>
References: <2BE582FA-2682-4232-9D83-23A03F01A0DB@NLnetLabs.nl> <6.2.5.6.2.20110330073936.0e1899d0@resistor.net> <E2E41FDE-3818-4513-9933-CB1E0326B43E@nlnetlabs.nl> <6.2.5.6.2.20110330113947.0c948bc0@resistor.net> <4D942843.4060804@gmail.com> <6.2.5.6.2.20110331120351.09488990@resistor.net> <4D955661.8050502@gmail.com> <9C81C0F6-3ABE-4479-8C5E-C20C486D052A@gmail.com> <82A347CC-BB19-4A73-8E8A-924FBAA92A5F@NLnetLabs.nl> <84D6568B-18C9-47B2-A457-C51C2FB3351F@gmail.com> <5419FA805EF52E79D7822966@PST.JCK.COM>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1082)
Cc: Bob Hinden <bob.hinden@gmail.com>, 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: Thu, 14 Apr 2011 16:52:02 -0000

John,

>> Bob,
>=20
> I think you and Olaf (and myself and others) are addressing two
> rather different questions.  Your note seems to assume the
> question is "how to make the IAOC work better".  Your answer, if
> I understand it correctly, is "it works fairly well today isn't
> broken, let's not fix it".  If that were the question, I'd agree.

No that is not correct, you have it reversed.  My concern is that this =
proposed change would likely make the IAOC work worse.  That is, I think =
it would have a negative impact on the operations of the IETF and that =
is why I am concerned.

I am sympathetic to the leadership's overload problem, but think we =
should take a broader view.  For example, another approach might be to =
split the IAB's responsibilities into two groups, one focused on =
architecture (the IAB's traditional role) and another new group to deal =
with the parts of the job that seems to be growing (liaisons, RFC =
Editor, etc.).  Something like this might make the NOMCOM job easier in =
the sense that it wouldn't have find people who were strong in =
architecture and policy administration (I don't think that is the best =
description of the rest, but can't think of anything better at the =
moment).

Bob



>=20
> But, remembering that the IASA has only the purpose of making
> the extended IETF (including the IAB) work more efficiently, I
> see a somewhat different question.  The roles and resource
> requirements of the IAB and IETF Chairs have expanded
> dramatically over the last several years.. expanded to the point
> that the appointing bodies may soon have to choose, not among
> the best people for the job, but from those who have spare time
> and resources on their hands or, worse, who work for
> organizations who see particular value in having one of their
> employees in those positions.  We have been lucky so far in
> finding very good people despite those pressures, but we can't
> count on its lasting.
>=20
> That situation suggests to me that we should be asking the
> question of how we can reduce the absolute requirements
> associated with the IAB and IETF Chair positions.  If whomever
> is in those positions has the time, resources, and interest to
> also serve on the IAOC, I'm very much in favor of that.   But,
> if an individual --or the Nomcom-- have to choose between
> exclusion of the best candidate because there aren't enough
> resources for him or her to do the [rest of the] Chair job _and_
> the IAOC versus spreading the workload out, then I think it is
> in the community's interest to have an alternative.    My
> personal preference continues to be to make the decision of who
> from the IAB (and potentially the IESG) serves on the IAOC be
> the decision of the IAB or IESG respectively rather than using
> the "delegation" model Olaf suggests but, in practice, I think
> it really makes no difference because any reasonable Chair is
> going to discuss those options with the relevant body.
>=20
> Even if we were not worried about overall workload, we've
> discovered at several recent IETF meetings that the schedule for
> IAOC-related meetings keeps the IAB and IETF Chairs out of other
> meetings that might, objectively, have been important for them
> to attend.  So it is not clear to me that having those two
> people on the IAOC in person is optimal for the community,
> independent of whether or not it is desirable for IASA.
>=20
>> =46rom that point of view, the right question from the IASA/IAOC
> perspective should not be "is it working well enough that there
> is no internal reason to make a change" but "can this type of
> change be made without serious damage".
>=20
> As far as the Trust is concerned, while we couldn't change the
> relationship until recently, we can now: if the linkage between
> Trust and IAOC membership is interfering with the simultaneous
> successful operation of the Trust and the efficient operation of
> the IAB and/or IESG, let's just change it.
>=20
>    john
>=20


From cyrus@daboo.name  Thu Apr 14 09:57:43 2011
Return-Path: <cyrus@daboo.name>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 7A9FEE08D6 for <ietf@ietfc.amsl.com>; Thu, 14 Apr 2011 09:57:43 -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.038, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lctiwH8Xvve0 for <ietf@ietfc.amsl.com>; Thu, 14 Apr 2011 09:57:42 -0700 (PDT)
Received: from daboo.name (daboo.name [151.201.22.177]) by ietfc.amsl.com (Postfix) with ESMTP id 46351E08CA for <ietf@ietf.org>; Thu, 14 Apr 2011 09:57:42 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id BA38C1C73E4EA; Thu, 14 Apr 2011 12:57:41 -0400 (EDT)
X-Virus-Scanned: amavisd-new at daboo.name
Received: from daboo.name ([127.0.0.1]) by localhost (chewy.mulberrymail.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MMFZ5N43wnPx; Thu, 14 Apr 2011 12:57:41 -0400 (EDT)
Received: from caldav.corp.apple.com (unknown [17.101.32.44]) by daboo.name (Postfix) with ESMTPSA id 6476D1C73E4D3; Thu, 14 Apr 2011 12:57:40 -0400 (EDT)
Date: Thu, 14 Apr 2011 12:57:37 -0400
From: Cyrus Daboo <cyrus@daboo.name>
To: Keith Moore <moore@network-heretics.com>, ietf@ietf.org
Subject: Re: Last Call: <draft-daboo-et-al-icalendar-in-xml-08.txt> (xCal: The	XML format for iCalendar) to Proposed Standard
Message-ID: <B692904DADBDAB05491FCF13@caldav.corp.apple.com>
In-Reply-To: <19543_1302796363_p3EFqgUp023831_9514532F-8A12-4A16-BF42-974A048BEB05@network-heretics.com>
References: <20110414152020.12635.714.idtracker@ietfc.amsl.com> <19543_1302796363_p3EFqgUp023831_9514532F-8A12-4A16-BF42-974A048BEB05@network-heretics.com>
X-Mailer: Mulberry/4.1.0a1 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; size=5485
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 16:57:43 -0000

Hi Keith,

--On April 14, 2011 11:52:37 AM -0400 Keith Moore 
<moore@network-heretics.com> wrote:

> I appreciate that great pains have been taken to ensure that this format
> is a dual of the standard iCalendar format, that translation can be
> performed in both directions without loss, and that at least some attempt
> has been made to specify the conversion algorithms in such a way that (if
> carefully implemented) they should continue to work with extensions to
> iCalendar.

Yes, that has always been a requirement for this mapping.

> I think it's confusing that many elements are referred to using an ICAL:
> prefix, when (a) the xml examples don't actually associate that prefix
> with a namespace, and (b) when iCal is probably a trademark of Apple.

Section 2 explains that the ICAL: prefix is used when elements are referred 
to outside the context of an XML fragment - i.e. in the actual text. As 
regards the possible trademark issue, to remove any possibility of that I 
will change to using IC: instead (hopefully there are not "legal" 
objections to that).

> However (and I think it's been at least 10 years since this was first
> proposed) I still find myself wondering, why is this format needed or
> even useful?    Practically speaking, I think the adoption of this format
> will only increase the burden on implementations and decrease the
> likelihood of interoperability between implementations.  It will increase
> the burden on implementations because now implementations will need to be
> able to accept, and possibly generate, two different calendar data
> formats instead of one.

First of all the real burden in handling iCalendar is not the syntax, it is 
the semantics (dealing with recurrences, timezones etc). In most cases, 
apps that use iCalendar parse the data into their own internal object model 
and deal with it there. Those implementers that have already developed 
iCalendar-in-XML parsers/generators have found it trivial to do and map to 
their internal object models (I have done that, and I am sure others can 
chime in and confirm this too).

Secondly, there is a great push on now to include iCalendar data in various 
web tools and automated systems, where XML is the primary format that is 
used. In particular, OASIS is planning on adopting this specification as a 
key component of smart grid work they are undertaking. The Calendaring and 
Scheduling Consortium has been advising them and helping develop APIs 
(REST, SOAP) etc to enable the kinds of calendar data access and 
manipulation that they need.

> I think that adoption of this format will in practice require that (a)
> any extensions to iCalendar to also explicitly specify how they are
> mapped into xCalendar, and (b) every, or nearly every,
> iCalendar<>xCalendar conversion product to be updated every time there is
> an extension to the iCalendar format.

I disagree that extensions will need to describe anything related to 
iCalendar-in-XML. We have tried very hard to have an automatic mapping. In 
fact I have several iCalendar extension drafts in the works and none of 
them will make reference to iCalendar-in-XML.

> I also suspect that converting the format to XML will encourage ad hoc
> extensions to xCalendar which might not map well to iCalendar - since the
> constraints and extension model of iCalendar will not be obvious to the
> typical XML code developer.

That is a concern. But any changes to the semantics of iCalendar that go on 
the standards track are covered by the IANA registration procedures 
outlined in 5545. As such designated experts get to review those and those 
experts can keep this problem in check (yes I happen to be one of those 
designated experts).

> Use of the "XML" property in iCalendar implies that the conversion
> routine needs to know which properties are "already" defined in
> iCalendar, which either implies that iCalendar cannot be extended, or
> that different converters (knowledgable about different versions of
> iCalendar) will produce different results (some mapping unknown
> properties to the iCalendar XML property, and some mapping them to native
> iCalendar properties).

One of the primary uses for iCalendar-in-XML is to allow it to be easily 
embedded in other XML documents (e.g. business-to-business automated 
transactions that require detailed specification of timing), and to also 
allow "annotation" of the iCalendar data with other XML elements (in a 
different namespace) that may provide references back to the enclosing 
data. The "XML" property is designed to allow round-tripping of XML data in 
other namespaces embedded in the iCalendar-in-XML data.

> Correct conversion from iCalendar to XML appears to require the converter
> to know about the types of each of the properties even though these are
> not explicitly specified in the source iCalendar document.   This is
> problematic if new properties are defined for iCalendar, as old
> converters won't know about the types of those properties.

Hrmm, good point. I will need to think about how the default value type can 
be handled in that case.

> So, in summary, I still don't think this is worth the trouble.
> Regardless of the application, providing multiple ways to represent the
> same information generally seems to degrade interoperability.

I take it that you would consider offering similar comments on the 
vCard-in-XML draft (draft-ietf-vcarddav-vcardxml) which is also in IETF 
last call?

-- 
Cyrus Daboo


From douglm@rpi.edu  Thu Apr 14 12:36:40 2011
Return-Path: <douglm@rpi.edu>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 365A7E076D for <ietf@ietfc.amsl.com>; Thu, 14 Apr 2011 12:36:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R27RAjKem-Jy for <ietf@ietfc.amsl.com>; Thu, 14 Apr 2011 12:36:39 -0700 (PDT)
Received: from smtp7.server.rpi.edu (smtp7.server.rpi.edu [128.113.2.227]) by ietfc.amsl.com (Postfix) with ESMTP id C05EFE074A for <Ietf@ietf.org>; Thu, 14 Apr 2011 12:36:35 -0700 (PDT)
Received: from [128.113.124.225] (blue-eyes-white-dragon-17.dynamic2.rpi.edu [128.113.124.225]) (authenticated bits=0) by smtp7.server.rpi.edu (8.13.1/8.13.1) with ESMTP id p3EJaXCV028312 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <Ietf@ietf.org>; Thu, 14 Apr 2011 15:36:33 -0400
Message-ID: <4DA74CC1.2030205@rpi.edu>
Date: Thu, 14 Apr 2011 15:36:33 -0400
From: Mike Douglass <douglm@rpi.edu>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.14) Gecko/20110223 Lightning/1.0b2 Thunderbird/3.1.8
MIME-Version: 1.0
To: Ietf@ietf.org
Subject: Re: Last Call: <draft-daboo-et-al-icalendar-in-xml-08.txt> (xCal: The XML format for iCalendar) to Proposed Standard
References: <4DA7488F.5040608@rpi.edu>
In-Reply-To: <4DA7488F.5040608@rpi.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Bayes-Prob: 0.0001 (Score 0)
X-RPI-SA-Score: 1.40 (*) [Hold at 10.00] RATWARE_GECKO_BUILD,22490(-25)
X-CanItPRO-Stream: outgoing
X-Canit-Stats-ID: Bayes signature not available
X-Scanned-By: CanIt (www . roaringpenguin . com) on 128.113.2.227
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 19:36:40 -0000

On 04/14/2011 03:18 PM, Keith Moore wrote:
> I appreciate that great pains have been taken to ensure that this 
> format is a dual of the standard iCalendar format, that translation 
> can be performed in both directions without loss, and that at least 
> some attempt has been made to specify the conversion algorithms in 
> such a way that (if carefully implemented) they should continue to 
> work with extensions to iCalendar.
>
> I think it's confusing that many elements are referred to using an 
> ICAL: prefix, when (a) the xml examples don't actually associate that 
> prefix with a namespace, and (b) when iCal is probably a trademark of 
> Apple.
>
> However (and I think it's been at least 10 years since this was first 
> proposed) I still find myself wondering, why is this format needed or 
> even useful?    Practically speaking, I think the adoption of this 
> format will only increase the burden on implementations and decrease 
> the likelihood of interoperability between implementations.  It will 
> increase the burden on implementations because now implementations 
> will need to be able to accept, and possibly generate, two different 
> calendar data formats instead of one.
>
> It will decrease interoperability because there will certainly be some 
> attempts to send xCalendar data created by new implementations, to old 
> implementations that only accept iCalendar data.  It will also 
> decrease interoperability because, inevitably, some implementations of 
> the conversion routines will fail to be sufficiently general in order 
> to handle currently-undefined properties and components.   This is an 
> almost inherent consequence of the likely use of XML schema 
> description languages that explicitly enumerate element names, and 
> processing languages that associate explicit element names with 
> processing actions.   Finally it will decrease interoperability 
> because it will no longer be the case that only producers and 
> consumers of iCalendar data have to interoperate - it will then be 
> necessary for producers, consumers, and converters to all interoperate 
> - thus introducing more opportunities for both implementation bugs and 
> version skew to create problems.
>
In many situations XML is the only acceptable data format. The work 
going on for the SmartGrid has made that clear to us. Far from 
decreasing interoperability this work will help keep the work done in 
XML based environments in line with that in the rest of the calendaring 
world.

It is already the case that other data formats are in use - we're not 
going to prevent that. The best we can do is to try to provide 
standardised approaches to conversion and data formats.
> I also get the impression that the mapping of "values" or data types 
> (section 3.6) between iCalendar and XML is not sufficiently general to 
> permit continued interoperability across extensions.
>
> I think that adoption of this format will in practice require that (a) 
> any extensions to iCalendar to also explicitly specify how they are 
> mapped into xCalendar, and (b) every, or nearly every, 
> iCalendar<>xCalendar conversion product to be updated every time there 
> is an extension to the iCalendar format.
In the JAXB and SOAP worlds at least this is not an issue. By default 
those environments ignore elements they are not aware of. That's fine as 
schemas can be updated when it is important to handle these extensions. 
An iCalendar XML schema is being developed for use in those environments 
and already does a reasonable job of handling extensions. We're aware of 
the problems posed by extensibility (as is most of the enterprise XML 
world) and are developing ways of mitigating them.

>
> I also suspect that converting the format to XML will encourage ad hoc 
> extensions to xCalendar which might not map well to iCalendar - since 
> the constraints and extension model of iCalendar will not be obvious 
> to the typical XML code developer.
>
> Use of the "XML" property in iCalendar implies that the conversion 
> routine needs to know which properties are "already" defined in 
> iCalendar, which either implies that iCalendar cannot be extended, or 
> that different converters (knowledgable about different versions of 
> iCalendar) will produce different results (some mapping unknown 
> properties to the iCalendar XML property, and some mapping them to 
> native iCalendar properties).
>
> Correct conversion from iCalendar to XML appears to require the 
> converter to know about the types of each of the properties even 
> though these are not explicitly specified in the source iCalendar 
> document.   This is problematic if new properties are defined for 
> iCalendar, as old converters won't know about the types of those 
> properties.
>
> So, in summary, I still don't think this is worth the trouble.   
> Regardless of the application, providing multiple ways to represent 
> the same information generally seems to degrade interoperability.
>
> Keith
>
It's worth remembering that the initial motivation for this 
specification was not to promote the use of XML but in response to the 
already widespread use of differing and incompatible XML forms of 
calendar data.

-- 

Mike Douglass                           douglm@rpi.edu
Senior Systems Programmer
Communication&  Collaboration Technologies      518 276 6780(voice) 2809
(fax)
Rensselaer Polytechnic Institute 110 8th Street, Troy, NY 12180


From mperumal@cisco.com  Thu Apr 14 13:41:46 2011
Return-Path: <mperumal@cisco.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 9F486E07AB; Thu, 14 Apr 2011 13:41:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.099
X-Spam-Level: 
X-Spam-Status: No, score=-10.099 tagged_above=-999 required=5 tests=[AWL=0.500, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZWcjnN-gUaZQ; Thu, 14 Apr 2011 13:41:45 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfc.amsl.com (Postfix) with ESMTP id 86D3BE075D; Thu, 14 Apr 2011 13:41:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=mperumal@cisco.com; l=8285; q=dns/txt; s=iport; t=1302813704; x=1304023304; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=D3clFY1gSlqow6VkpWXOB40IUcfn9Z1iVHI5Yj1rh98=; b=MtD6N1FMxrL3M/1lIib6rbaZYmetvLnAIKEOW0+mAS9gQQuwv6YeCBeQ UCGg5DJdNROB0wM1VcGgKGI/rgUy9bA+CEEOwVMVxzlJlZqaV1+31sdZV rhAgOHDx/wfiOnWXrvdZlbnmtZk9Tl+OkXZNMqGejAd35iAhFwW8eKfh2 A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvEAALpbp02Q/khNgWdsb2JhbACXfI19FAEBFiYlpjydCoIhg00EhViMEQ
X-IronPort-AV: E=Sophos;i="4.64,213,1301875200"; d="scan'208";a="83637303"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-1.cisco.com with ESMTP; 14 Apr 2011 20:41:43 +0000
Received: from xbh-bgl-411.cisco.com (xbh-bgl-411.cisco.com [72.163.129.201]) by ams-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p3EKfcwI024785; Thu, 14 Apr 2011 20:41:43 GMT
Received: from xmb-bgl-414.cisco.com ([72.163.129.210]) by xbh-bgl-411.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 15 Apr 2011 02:11:38 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [siprec] Last Call: <draft-ietf-siprec-req-09.txt>(Use	Cases	andRequirements	for SIP-based MediaRecording	(SIPREC))	toInformational RFC
Date: Fri, 15 Apr 2011 02:11:38 +0530
Message-ID: <1D062974A4845E4D8A343C65380492020533BD38@XMB-BGL-414.cisco.com>
In-Reply-To: <35BCE99A477D6A4986FB2216D8CF2CFD06009D00@XMB-BGL-417.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] Last Call: <draft-ietf-siprec-req-09.txt>(Use	Cases	andRequirements	for SIP-based MediaRecording	(SIPREC))	toInformational RFC
Thread-Index: Acv0WYBeRuGjGNBtTZSHeqn78QP5xwGEv6YwAAlHtwAAAvtH0AABcMXAAAdJn6AAAIZ7cAAHjozg
References: <20110406125020.17538.70016.idtracker@localhost><1D062974A4845E4D8A343C65380492020533BB70@XMB-BGL-414.cisco.com><A444A0F8084434499206E78C106220CA0875EB5A4E@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38AB73D00B@TLVMBX01.nice.com><A444A0F8084434499206E78C106220CA0875EB5B28@MCHP058A.global-ad.net> <07465C1D981ABC41A344374066AE1A2C38AB73D110@TLVMBX01.nice.com> <35BCE99A477D6A4986FB2216D8CF2CFD06009D00@XMB-BGL-417.cisco.com>
From: "Muthu ArulMozhi Perumal (mperumal)" <mperumal@cisco.com>
To: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>, "Leon Portman" <Leon.Portman@nice.com>, "Elwell, John" <john.elwell@siemens-enterprise.com>, <ietf@ietf.org>
X-OriginalArrivalTime: 14 Apr 2011 20:41:38.0945 (UTC) FILETIME=[5A95DF10:01CBFAE4]
Cc: siprec@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 Apr 2011 20:41:46 -0000

I agree with John that these seem more like part of a solution rather
than actual requirements. In addition, sending the wallclock time at
media start/end alone may not suffice for achieving inter-media
synchronization and playback, instead we may need to send the wallclock
time periodically, like RTCP. For e.g, if there is a codec renegotiation
in CS the RTP timestamp can restart from a random value. If silence
suppression is enabled there would be gaps in the RTP timestamp.=20

These are things that need to be discussed as part of the solution --
the requirement itself should be generic enough, like what I described.
REQ-022 and REQ-023 we have doesn't seem to clearly indicate the
purpose.

Muthu=20

|-----Original Message-----
|From: Ram Mohan R (rmohanr)
|Sent: Thursday, April 14, 2011 10:13 PM
|To: Leon Portman; Elwell, John; Muthu ArulMozhi Perumal (mperumal);
ietf@ietf.org
|Cc: siprec@ietf.org
|Subject: RE: [siprec] Last Call: <draft-ietf-siprec-req-09.txt>(Use
Cases andRequirements for SIP-
|based MediaRecording (SIPREC)) toInformational RFC
|
|We already have  attributes Start-Time / End-time in Media Stream
block. This is for the same purpose
|to indicate the wall clock time for start/end of media.
|
|Ram
|
|> -----Original Message-----
|> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
|> Behalf Of Leon Portman
|> Sent: Thursday, April 14, 2011 9:57 PM
|> To: Elwell, John; Muthu ArulMozhi Perumal (mperumal); ietf@ietf.org
|> Cc: siprec@ietf.org
|> Subject: Re: [siprec] Last Call: <draft-ietf-siprec-req-09.txt>(Use
|> Cases andRequirements for SIP-based MediaRecording (SIPREC))
|> toInformational RFC
|>
|> I am not sure that having wall clock only for CS start is enough,
|> especially for partial metadata update. I will prefer to have on
media
|> level
|>
|> Leon
|>
|> -----Original Message-----
|> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
|> Sent: Thursday, April 14, 2011 3:58 PM
|> To: Leon Portman; Muthu ArulMozhi Perumal (mperumal); ietf@ietf.org
|> Cc: siprec@ietf.org
|> Subject: RE: [siprec] Last Call: <draft-ietf-siprec-req-09.txt> (Use
|> Cases andRequirements for SIP-based Media Recording (SIPREC))
|> toInformational RFC
|>
|> Understood, but if we have wall clock time for the start of a CS,
|> wouldn't that be sufficient? The new requirement would cover
|> synchronization of all media start/stops relative to that time.
|>
|> John (as individual)
|>
|>
|> > -----Original Message-----
|> > From: Leon Portman [mailto:Leon.Portman@nice.com]
|> > Sent: 14 April 2011 13:19
|> > To: Elwell, John; Muthu ArulMozhi Perumal (mperumal); ietf@ietf.org
|> > Cc: siprec@ietf.org
|> > Subject: RE: [siprec] Last Call:
|> > <draft-ietf-siprec-req-09.txt> (Use Cases andRequirements for
|> > SIP-based Media Recording (SIPREC)) toInformational RFC
|> >
|> > Actually REQ-022 and REQ-023 describing not only requirement to
|> > synchronize between different media streams but more importantly
|> > ability to relate them to real world (wall) clock. It is not only
|> > important to playback them correctly but also to know when it was
|> > said.
|> > One example is continue trading after closing hour (even for one
|> > second is not allowed)
|> >
|> > And if these media are synchronized to wall clock then they are
also
|> > synchronized between them thus I am not sure if we need this
|> > additional requirement.
|> >
|> > Thanks
|> >
|> > Leon
|> >
|> > -----Original Message-----
|> > From: siprec-bounces@ietf.org
|> > [mailto:siprec-bounces@ietf.org] On Behalf Of Elwell, John
|> > Sent: Thursday, April 14, 2011 1:54 PM
|> > To: Muthu ArulMozhi Perumal (mperumal); ietf@ietf.org
|> > Cc: siprec@ietf.org
|> > Subject: Re: [siprec] Last Call:
|> > <draft-ietf-siprec-req-09.txt> (Use Cases andRequirements for
|> > SIP-based Media Recording (SIPREC)) toInformational RFC
|> >
|> >
|> >
|> >
|> > > -----Original Message-----
|> > > From: siprec-bounces@ietf.org
|> > > [mailto:siprec-bounces@ietf.org] On Behalf Of Muthu
|> > ArulMozhi Perumal
|> > > (mperumal)
|> > > Sent: 14 April 2011 07:34
|> > > To: ietf@ietf.org
|> > > Cc: siprec@ietf.org
|> > > Subject: Re: [siprec] Last Call:
|> > > <draft-ietf-siprec-req-09.txt> (Use Cases andRequirements for
|> > > SIP-based Media Recording (SIPREC)) toInformational RFC
|> > >
|> > > I've one major comment. It draft discusses synchronization
|> > between the
|> > > recorded media streams and synchronized playback, which
|> > seem important
|> > > for certain applications:
|> > >
|> > > <snip>
|> > > Some applications require the recording of more than one
|> > media stream,
|> > > possibly of different types. Media are synchronized, either
|> > at storage
|> > > or at playback.
|> > > </snip>
|> > >
|> > > However, in the requirements section it doesn't seem REQ-022 and
|> > > REQ-023 are all that are need and sufficient to achieve this with
|> > > needed precision. So, I would suggest adding another requirement
as
|> > > follows:
|> > > The mechanism MUST provide means for facilitating
|> > synchronization of
|> > > the recorded media streams and metadata either at storage or at
|> > > playback.
|> > > This includes, but not limited to, the information needed as per
|> > > REQ-022 and REQ-023.
|> > [JRE] This seems a reasonable addition. I wonder if the new
|> > requirement (first sentence only) is sufficient as a
|> > **replacement** for REQ-022 and REQ-023. On reading REQ-022 and
|> > REQ-023 again, it is not so clear what their purpose was, and they
|> > seem to be more like a solution than a requirement.
|> > One purpose would certainly be that covered by Muthu's new
|> > requirement. Was there any other purpose?
|> >
|> > John
|> >
|> > >
|> > > A nitpick:
|> > > Use Case 8
|> > > In cases where calls inside or between branches must be recorded,
a
|> > > centralized recording system in data centers together with
|> > telephony
|> > > infrastructure (e.g. PBX) me deployed.
|> > >
|> > > s/me/may be
|> > >
|> > > Muthu
|> > >
|> > > |-----Original Message-----
|> > > |From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org]
On
|> > > Behalf Of The IESG
|> > > |Sent: Wednesday, April 06, 2011 6:20 PM
|> > > |To: IETF-Announce
|> > > |Cc: siprec@ietf.org
|> > > |Subject: [siprec] Last Call: <draft-ietf-siprec-req-09.txt>
|> > > (Use Cases
|> > > andRequirements for SIP-based
|> > > |Media Recording (SIPREC)) toInformational RFC
|> > > |
|> > > |
|> > > |The IESG has received a request from the SIP Recording WG
|> > (siprec) to
|> > > |consider the following document:
|> > > |- 'Use Cases and Requirements for SIP-based Media
|> > Recording (SIPREC)'
|> > > |  <draft-ietf-siprec-req-09.txt> as an 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 2011-04-20. 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.
|> > > |
|> > > |The file can be obtained via
|> > > |http://datatracker.ietf.org/doc/draft-ietf-siprec-req/
|> > > |
|> > > |IESG discussion can be tracked via
|> > > |http://datatracker.ietf.org/doc/draft-ietf-siprec-req/
|> > > |
|> > > |
|> > > |
|> > > |No IPR declarations have been submitted directly on this I-D.
|> > > |_______________________________________________
|> > > |siprec mailing list
|> > > |siprec@ietf.org
|> > > |https://www.ietf.org/mailman/listinfo/siprec
|> > > _______________________________________________
|> > > siprec mailing list
|> > > siprec@ietf.org
|> > > https://www.ietf.org/mailman/listinfo/siprec
|> > >
|> > _______________________________________________
|> > siprec mailing list
|> > siprec@ietf.org
|> > https://www.ietf.org/mailman/listinfo/siprec
|> >
|> _______________________________________________
|> siprec mailing list
|> siprec@ietf.org
|> https://www.ietf.org/mailman/listinfo/siprec

From housley@vigilsec.com  Thu Apr 14 14:13:25 2011
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 10986E0823 for <ietf@ietfc.amsl.com>; Thu, 14 Apr 2011 14:13:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.731
X-Spam-Level: 
X-Spam-Status: No, score=-102.731 tagged_above=-999 required=5 tests=[AWL=-0.132, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 98flLoRGVxlf for <ietf@ietfc.amsl.com>; Thu, 14 Apr 2011 14:13:24 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfc.amsl.com (Postfix) with ESMTP id F2FCCE07E6 for <ietf@ietf.org>; Thu, 14 Apr 2011 14:13:23 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 0E071F24081; Thu, 14 Apr 2011 17:13:25 -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 1VoJzjNr5qs4; Thu, 14 Apr 2011 17:13:23 -0400 (EDT)
Received: from [192.168.2.100] (pool-71-178-218-117.washdc.fios.verizon.net [71.178.218.117]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 84D4BF2402C; Thu, 14 Apr 2011 17:13:24 -0400 (EDT)
Subject: Re: IAOC: delegating ex-officio responsibility
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <4DA71408.3090704@gmail.com>
Date: Thu, 14 Apr 2011 17:13:22 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <7220CC90-02B0-45B0-9113-236A933BBD16@vigilsec.com>
References: <2BE582FA-2682-4232-9D83-23A03F01A0DB@NLnetLabs.nl>	<6.2.5.6.2.20110330073936.0e1899d0@resistor.net>	<E2E41FDE-3818-4513-9933-CB1E0326B43E@nlnetlabs.nl>	<6.2.5.6.2.20110330113947.0c948bc0@resistor.net>	<4D942843.4060804@gmail.com>	<6.2.5.6.2.20110331120351.09488990@resistor.net>	<4D955661.8050502@gmail.com>	<9C81C0F6-3ABE-4479-8C5E-C20C486D052A@gmail.com>	<82A347CC-BB19-4A73-8E8A-924FBAA92A5F@NLnetLabs.nl>	<84D6568B-18C9-47B2-A457-C51C2FB3351F@gmail.com> <5419FA805EF52E79D7822966@PST.JCK.COM> <4DA71408.3090704@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.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: Thu, 14 Apr 2011 21:13:25 -0000

Brian:

> I'd really like to hear from
> Olaf, Bernard and Russ what has changed in the workload in the
> last few years.

I am fortunate that my sponsorship situation lets me spend almost full =
time on the IETF Chair position.  Even so, there are aspects of the job =
that exceed full time.  I am not talking about IETF meeting week -- the =
job far exceeds full time for many others too during that week.  That =
said, the answer to your question is not simple.

The IETF Chair is a member of the IAOC, the IETF Trust, the IAB, and the =
IESG.

The IAOC has many committees, and I am unable to participate in all of =
them.  Even though I am interested in all of the topics, it is just not =
possible to participate in all of them.  So, I rely on the people that =
do participate and review their recommendations when they come to the =
whole IAOC for a vote.

The IETF Trust is the least time commitment.  It is important, but it is =
not usually time consuming.

The IAB has recently adopted a structure of  "projects" and =
"initiatives."  These are much like IAOC committees, and it will not be =
possible for any IAB member to participate in all of them.  This is =
necessary and healthy.  It also lets the IAB draw on expertise from =
outside the IAB more easily.

The IESG does much less work by committee, but some ADs have =
directorates or review teams to help with the vast amount of document =
review.  The IETF Chair has relied on Gen-ART since it was established =
by Harald about eight years ago.  I know that I depend on these reviews =
heavily.

The IETF Chair also depends upon the IETF Executive Director and other =
members of the Secretariat for many day-to-day tasks.  I believe that I =
have made greater use of the Secretariat than many previous IETF Chairs.

So, you can readilly see that there is a significant amount of =
delegation going on.  Still, some tasks get starved, simply because =
other things are more important at the time.  Recently, for example, =
activities around the relationship with ITU SG15 have consumed all =
available cycles.

The proposed update to BCP 101 permits further delegation of the IAOC =
voting position.  While I do not see myself taking advantage of this new =
feature, I do think we should give future IETF Chairs this option.  It =
is a cohesive part of the work that can be delegated.  Some coordination =
between the IETF Chair and the delegate would be necessary, but the time =
commitment would be significantly less than participating in the IAOC =
and a subset of its committees.

Russ



From bob.hinden@gmail.com  Thu Apr 14 14:26:31 2011
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 40886E07D5 for <ietf@ietfc.amsl.com>; Thu, 14 Apr 2011 14:26:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.349
X-Spam-Level: 
X-Spam-Status: No, score=-103.349 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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lPsw7-WEGxuy for <ietf@ietfc.amsl.com>; Thu, 14 Apr 2011 14:26:29 -0700 (PDT)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by ietfc.amsl.com (Postfix) with ESMTP id 6FF54E07BC for <ietf@ietf.org>; Thu, 14 Apr 2011 14:26:29 -0700 (PDT)
Received: by iwn39 with SMTP id 39so2261306iwn.31 for <ietf@ietf.org>; Thu, 14 Apr 2011 14:26:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=V6UMO374zJIlC6mui3HOPFZQuUFJjpOIz0XMlrVd088=; b=xgAWdhQFfEYZcAYBl9zjHBaPDksojZi4WFeJF053+B0S7UCY1q7tVUyU4is9ztnoBe aEyF5w7gKSmeASBT7k4rFVSi/ycECJkmN9KKXnQmtYnGaW1bl94lu7Ymira2b9WH6YFr IQsRsE+b+DQfQ3y9sj8Y+jP5KiDQwsywFptzc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=u98pEzsEto4+Nj70a2nuLkcBd0qxc3UptX91bTlQlJz9ctoYQtmh/b9Awm0Z+VLv2O xQo7n6+fwepXnaEPqZca6Kk3kSvlGZZVk7YKFtRwdYh1JbG+uRyV99kILEmZEZpjjWno JVzzUrgr6PryL0lIiuimP37DZq8GgCuCPiTOI=
Received: by 10.231.115.209 with SMTP id j17mr1151688ibq.19.1302816388801; Thu, 14 Apr 2011 14:26:28 -0700 (PDT)
Received: from [172.16.224.217] ([209.97.127.34]) by mx.google.com with ESMTPS id 13sm1440279ibo.8.2011.04.14.14.26.27 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 14 Apr 2011 14:26:28 -0700 (PDT)
Subject: Re: IAOC: delegating ex-officio responsibility
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <7220CC90-02B0-45B0-9113-236A933BBD16@vigilsec.com>
Date: Thu, 14 Apr 2011 14:26:26 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <8F2607B3-F58E-4786-A60D-4A2758E2C35E@gmail.com>
References: <2BE582FA-2682-4232-9D83-23A03F01A0DB@NLnetLabs.nl>	<6.2.5.6.2.20110330073936.0e1899d0@resistor.net>	<E2E41FDE-3818-4513-9933-CB1E0326B43E@nlnetlabs.nl>	<6.2.5.6.2.20110330113947.0c948bc0@resistor.net>	<4D942843.4060804@gmail.com>	<6.2.5.6.2.20110331120351.09488990@resistor.net>	<4D955661.8050502@gmail.com>	<9C81C0F6-3ABE-4479-8C5E-C20C486D052A@gmail.com>	<82A347CC-BB19-4A73-8E8A-924FBAA92A5F@NLnetLabs.nl>	<84D6568B-18C9-47B2-A457-C51C2FB3351F@gmail.com> <5419FA805EF52E79D7822966@PST.JCK.COM> <4DA71408.3090704@gmail.com> <7220CC90-02B0-45B0-9113-236A933BBD16@vigilsec.com>
To: Russ Housley <housley@vigilsec.com>
X-Mailer: Apple Mail (2.1082)
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: Thu, 14 Apr 2011 21:26:31 -0000

Russ,


> The proposed update to BCP 101 permits further delegation of the IAOC =
voting position.  While I do not see myself taking advantage of this new =
feature, I do think we should give future IETF Chairs this option.  It =
is a cohesive part of the work that can be delegated.  Some coordination =
between the IETF Chair and the delegate would be necessary, but the time =
commitment would be significantly less than participating in the IAOC =
and a subset of its committees.


This prompts me to ask a question.  Who would the IETF Chair delegate =
this responsibility to?  The draft doesn't specify. =20

An Area Director is the obvious answer, except from what I understand =
ADs are also extremely busy.  This trades one problem for another.  If =
it is someone not on the IESG, then this is effectively turning into =
giving the IESG another IAOC slot to select.=20

As a general comment on the draft, I think it needs to be clear as to =
who the delegation can be made to and how much authority is delegated.

Thanks,
Bob






From Dave.Thewlis@calconnect.org  Thu Apr 14 14:28:21 2011
Return-Path: <Dave.Thewlis@calconnect.org>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 5C0ADE08B8 for <ietf@ietfc.amsl.com>; Thu, 14 Apr 2011 14:28:21 -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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ITbe5U683ej5 for <ietf@ietfc.amsl.com>; Thu, 14 Apr 2011 14:28:20 -0700 (PDT)
Received: from newredwood.morsemedia.net (newredwood.morsemedia.net [69.50.246.34]) by ietfc.amsl.com (Postfix) with ESMTP id 77AC4E0732 for <ietf@ietf.org>; Thu, 14 Apr 2011 14:28:20 -0700 (PDT)
Received: from [75.111.59.123] (helo=[192.168.0.218]) by newredwood.morsemedia.net with esmtpa (Exim 4.69) (envelope-from <Dave.Thewlis@calconnect.org>) id 1QAU5C-0002KF-6w; Thu, 14 Apr 2011 14:28:10 -0700
From: Dave Thewlis <Dave.Thewlis@calconnect.org>
Content-Type: multipart/alternative; boundary=Apple-Mail-9-239265627
Date: Thu, 14 Apr 2011 14:28:16 -0700
Subject: RE: Last Call: <draft-lear-iana-timezone-database-03.txt> (IANA Procedures for Maintaining the Timezone Database) to BCP
To: ietf@ietf.org
Message-Id: <8E2234E1-3C81-4115-A41E-13D308011951@calconnect.org>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
X-MorseMedia-MailScanner-Information: Please contact the ISP for more information
X-MorseMedia-MailScanner-ID: 1QAU5C-0002KF-6w
X-MorseMedia-MailScanner: Not scanned: please contact your Internet E-Mail Service Provider for details
X-MorseMedia-MailScanner-SpamCheck: 
X-MorseMedia-MailScanner-From: dave.thewlis@calconnect.org
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - newredwood.morsemedia.net
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - calconnect.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 Apr 2011 21:28:21 -0000

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



On behalf of CalConnect and its members I would like to voice our =
support for the timezone database proposal:  =
http://datatracker.ietf.org/doc/draft-lear-iana-timezone-database/  and =
encourage its adoption.  In particular this proposal is supported by our =
Timezone Technical Committee (TC TIMEZONE).  Valid, accurate and timely =
timezone information is increasingly essential to computing and the =
internet, and with Mr. Olson's retirement soon, it becomes critical to =
determine a permanent home for the process and the the database, while =
continuing and encouraging the volunteers who provide and manage the =
data itself.  CalConnect has worked from its earliest days on improving =
ways of accessing timezone data, which is critical to calendaring and =
scheduling, and has been an early and ongoing supporter of the IETF and =
IANA offering to provide a home for the Olson database and processes. =20=


Dave Thewlis




--
Dave Thewlis, Executive Director
CalConnect - The Calendaring and Scheduling Consortium
+1 707 840 9391 voice | +1 707 498 2238 mobile | +1 415 946 3454 fax
http://www.calconnect.org | Dave.Thewlis@calconnect.org


--Apple-Mail-9-239265627
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><br></div><div><br></div>On behalf of CalConnect and its members =
I would like to voice our support for the timezone database proposal: =
&nbsp;<a =
href=3D"http://datatracker.ietf.org/doc/draft-lear-iana-timezone-database/=
">http://datatracker.ietf.org/doc/draft-lear-iana-timezone-database/</a>&n=
bsp;&nbsp;and encourage its adoption. &nbsp;In particular this proposal =
is supported by our Timezone Technical Committee (TC TIMEZONE). =
&nbsp;Valid, accurate and timely timezone information is increasingly =
essential to computing and the internet, and with Mr. Olson's retirement =
soon, it becomes critical to determine a permanent home for the process =
and the the database, while continuing and encouraging the volunteers =
who provide and manage the data itself. &nbsp;CalConnect has worked from =
its earliest days on improving ways of accessing timezone data, which is =
critical to calendaring and scheduling, and has been an early and =
ongoing supporter of the IETF and IANA offering to provide a home for =
the Olson database and processes. &nbsp;<div><br></div><div>Dave =
Thewlis</div><div><br></div><div><br></div><br><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: 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-size: medium; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; 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; "><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div>--</div><div><b>Dave Thewlis, Executive =
Director</b></div><div><b>CalConnect - The Calendaring and Scheduling =
Consortium</b></div><div>+1 707 840 9391 voice | +1 707 498 2238 mobile =
| +1 415 946 3454 fax</div><div><a =
href=3D"http://www.calconnect.org">http://www.calconnect.org</a> | <a =
href=3D"mailto:Dave.Thewlis@calconnect.org">Dave.Thewlis@calconnect.org</a=
></div></div></span></span>
</div>
<br></body></html>=

--Apple-Mail-9-239265627--

From ole@cisco.com  Thu Apr 14 15:51:29 2011
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 7ED5AE07B6 for <ietf@ietfc.amsl.com>; Thu, 14 Apr 2011 15:51: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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FhSsTBzTVpLf for <ietf@ietfc.amsl.com>; Thu, 14 Apr 2011 15:51:26 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by ietfc.amsl.com (Postfix) with ESMTP id 6C1BFE07B1 for <ietf@ietf.org>; Thu, 14 Apr 2011 15:51:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=939; q=dns/txt; s=iport; t=1302821486; x=1304031086; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=fVKhukNPn3XnDtFBNQA5HY8vNGH0SoDdiQDhzJBKa1A=; b=jJdyXjLExGKaXkhaSILUZBT5OVaZ+3aOjCImJrZ3E+zC43jA1LFVO1hI TUx4lgodT8RNTwvvuRmbpMz3FnvMoKI3PwmfVnr3qPA51qDyjZqGnI0bH Oi1qV3RDubTWEMoDhfmiZ7DhPzjE+ikQ7PzyoXvng6s6Pi6Z45iinmHKq I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhUFAAR5p02rRDoI/2dsb2JhbACZK4xRd4hvnjiCcw4BmgCDGIJWBIVajAg
X-IronPort-AV: E=Sophos;i="4.64,214,1301875200"; d="scan'208";a="681714463"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by sj-iport-6.cisco.com with ESMTP; 14 Apr 2011 22:51:02 +0000
Received: from [10.24.17.59] ([10.24.17.59]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p3EMp271006859; Thu, 14 Apr 2011 22:51:02 GMT
Date: Thu, 14 Apr 2011 15:51:02 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: Bob Hinden <bob.hinden@gmail.com>
Subject: Re: IAOC: delegating ex-officio responsibility
In-Reply-To: <8F2607B3-F58E-4786-A60D-4A2758E2C35E@gmail.com>
Message-ID: <alpine.OSX.2.01.1104141547390.82851@173-11-110-133-sfba.hfc.comcastbusiness.net>
References: <2BE582FA-2682-4232-9D83-23A03F01A0DB@NLnetLabs.nl> <6.2.5.6.2.20110330073936.0e1899d0@resistor.net> <E2E41FDE-3818-4513-9933-CB1E0326B43E@nlnetlabs.nl> <6.2.5.6.2.20110330113947.0c948bc0@resistor.net> <4D942843.4060804@gmail.com> <6.2.5.6.2.20110331120351.09488990@resistor.net> <4D955661.8050502@gmail.com> <9C81C0F6-3ABE-4479-8C5E-C20C486D052A@gmail.com> <82A347CC-BB19-4A73-8E8A-924FBAA92A5F@NLnetLabs.nl> <84D6568B-18C9-47B2-A457-C51C2FB3351F@gmail.com> <5419FA805EF52E79D7822966@PST.JCK.COM> <4DA71408.3090704@gmail.com> <7220CC90-02B0-45B0-9113-236A933BBD16@vigilsec.com> <8F2607B3-F58E-4786-A60D-4A2758E2C35E@gmail.com>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
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
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: Thu, 14 Apr 2011 22:51:29 -0000

On Thu, 14 Apr 2011, Bob Hinden wrote:

> Russ,
> 
> 
> This prompts me to ask a question.  Who would the IETF Chair 
> delegate this responsibility to?  The draft doesn't specify.

I am thinking it would be someone like the IESG Secretary (if there is 
such a person), and I mean a member of the IESG, not some contractor.

Suppose, for a moment, we were talking about the ISOC BoT here instead 
of the IESG, the *obvious* choice would be Scott Bradner who has been 
Board Secretary for longer than any one can remember and clearly has a 
very good idea about the "sense of the board" at any given time.

So, is there an "equivalent" person in the IESG, that isn't also the
IESG (IETF) Chair?


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

 

From leslie@thinkingcat.com  Thu Apr 14 16:19:32 2011
Return-Path: <leslie@thinkingcat.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id C30CEE0750 for <ietf@ietfc.amsl.com>; Thu, 14 Apr 2011 16:19:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.949
X-Spam-Level: 
X-Spam-Status: No, score=-102.949 tagged_above=-999 required=5 tests=[AWL=1.650, BAYES_00=-2.599, GB_I_LETTER=-2, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id navMAF9Rff9F for <ietf@ietfc.amsl.com>; Thu, 14 Apr 2011 16:19:31 -0700 (PDT)
Received: from zeke.ecotroph.net (zeke.ecotroph.net [70.164.19.155]) by ietfc.amsl.com (Postfix) with ESMTP id 29C4DE0791 for <ietf@ietf.org>; Thu, 14 Apr 2011 16:19:30 -0700 (PDT)
Received: from beethoven.local ([::ffff:173.71.208.218]) (AUTH: PLAIN leslie, SSL: TLSv1/SSLv3,256bits,AES256-SHA) by zeke.ecotroph.net with esmtp; Thu, 14 Apr 2011 19:19:27 -0400 id 000180DA.4DA780FF.00002E5C
Message-ID: <4DA780FE.4010703@thinkingcat.com>
Date: Thu, 14 Apr 2011 19:19:26 -0400
From: Leslie Daigle <leslie@thinkingcat.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Olaf Kolkman <olaf@NLnetLabs.nl>
Subject: Re: IAOC: delegating ex-officio responsibility
References: <2BE582FA-2682-4232-9D83-23A03F01A0DB@NLnetLabs.nl>	<6.2.5.6.2.20110330073936.0e1899d0@resistor.net>	<E2E41FDE-3818-4513-9933-CB1E0326B43E@nlnetlabs.nl>	<6.2.5.6.2.20110330113947.0c948bc0@resistor.net>	<4D942843.4060804@gmail.com>	<6.2.5.6.2.20110331120351.09488990@resistor.net>	<4D955661.8050502@gmail.com>	<9C81C0F6-3ABE-4479-8C5E-C20C486D052A@gmail.com>	<82A347CC-BB19-4A73-8E8A-924FBAA92A5F@NLnetLabs.nl>	<84D6568B-18C9-47B2-A457-C51C2FB3351F@gmail.com>	<4DA69F79.6030700@gmail.com> <E19E3F13-90E4-48B0-9A6C-951DAA97D24E@nlnetlabs.nl>
In-Reply-To: <E19E3F13-90E4-48B0-9A6C-951DAA97D24E@nlnetlabs.nl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Bob Hinden <bob.hinden@gmail.com>, 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: Thu, 14 Apr 2011 23:19:32 -0000

Speaking as an individual, but an individual who helped set up this 
structure and who sat in the non-delegated ex officio IAB Chair position 
on the IAOC (and IETF Trust) for a couple of years, let me offer some 
comments.

As Bob noted, elsewhere in the thread, your draft does not describe how 
to delegate responsibilities, it describes how to allow alternatively 
fill the positions.  And I believe that is a fatal flaw.

The discussion on this thread certainly indicates that there isn't a 
clear grasp of what the responsibilities are for the positions in 
question.  The responsibilities are not:  show up for meetings/telecons, 
offer opinions about how to administer the IETF, and put in a vote when 
called upon, although those certainly are the functions expected.

You described the IAB Chair as "hub" as if that was a bad thing.   In 
fact, the one thing the Chair (of the IAB -- but it applies in analog to 
the IETF) needs to do is to support the IAB's functioning (through 
leadership, organization, note-taking, cajoling, listening, etc).  That 
doesn't mean the IAB Chair has to do the work of the whole IAB, but it 
does mean that an overall perspective is critical, and each Chair has to 
best organize her/himself to achieve the one task.

In setting up the IAOC as it is, the intent was to inject the IAB 
Chair's overall perspective into the IAOC's discussions, including the 
support for IAB activities.  It was not a question of simply finding 
more credible people to put on the IAOC.

If change is needed, the one path away from the fatal flaw seems to be 
to articulate the actual responsibilities of the IAB Chair (and IETF 
Chair and ISOC CEO, as appropriate) in the intended ex officio 
positions, such that it is possible to get agreement and external 
confirmation that the role is being properly fulfilled by whomever is 
selected to perform them.

Anything else, IMO, is mindless deconstruction.

Leslie.



On 4/14/11 5:01 AM, Olaf Kolkman wrote:
> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>
>
> On Apr 14, 2011, at 9:17 AM, Brian E Carpenter wrote:
>
>> On 2011-04-14 06:19, Bob Hinden wrote:
>>> Olaf,
>>>
>>> On Apr 2, 2011, at 1:28 AM, Olaf Kolkman wrote:
>>>
>>>> [as editor:]
>>>>
>>>> It seems that the high order bit of this discussion circles
>>>> around the question on whether it a requirement for the IETF
>>>> Chair to have a voting position in order to effectively perform
>>>> oversight. Once we figured out where we want to go with that we
>>>> can think about delegation by the chair vs appointment by the
>>>> bodies and the implementation details with respect to the
>>>> trust.
>>>
>>> For the record, I don't agree with this summary.  That is, I
>>> still question the basic assumption in the proposal.  We have
>>> "running code" in the IASA model and it appears to work
>>> reasonable well.  Not perfect, of course.  In particular I think
>>> that having the IETF chair, IAB chair, and ISOC president as
>>> voting members of the IAOC (and IETF Trust) has worked very well.
>>> It makes them an active part of decisions the IAOC and IETF Trust
>>> are making and helps keep the IAOC from getting disconnected from
>>> the community.  It also makes them share the responsibility for
>>> decisions by having their vote be publicly recorded.
>>
>> I agree. I think this responsibility should not be delegated. It's
>> fundamental to the success of the IETF (and the ISOC for that
>> matter - the IETF is a major source of ISOC's legitimacy). The IAOC
>> delegates execution to the IAD etc. - maybe the real bug is that
>> the IAOC itself needs to delegate more?
>>
>
>
>
> I agree the IASA model is working well and I also agree that the
> chairs have played an important role.
>
> But I am not convinced that it is the only way to keep the IAOC from
> getting disconnected from the community. To turn that argument
> around: If it is the case that we need the IAB chair, IETF chair and
> ISOC president [iChiefs] to keep the IAOC on track then why do we
> have NOMCOM appointments? One could easily argue that the NOMCOM
> appointments are made to keep the IAOC connected to the community.
>
> I also do not see why it 'it's fundamental to the success of the
> IETF'. I do agree that the iChiefs need to understand what is going
> on, there is no dispute about, but I question whether IAOC membership
> is best and most efficient instrument.
>
>
>
>>> I also don't understand what the effect of the proposal is on the
>>> IETF Trust.  Currently all IAOC members are members of the IETF
>>> Trust.  They have to sign a letter accepting this role.  I don't
>>> think it can then be delegated.
>>
>> It can't be delegated. However, a duly approved update to BCP101
>> can change the definition of the formal membership of the IAOC, and
>> that would automatically change the membership of the Trust. An
>> alternative would be a formal change to the Trust Agreement, but
>> since IANAL, I don't know whether a change to allow delegation or
>> proxies would be possible under the law of the Commonwealth of
>> Virginia, where the Trust was established.
>>
>
> I do not want to brush over this important detail. But, let us first
> figure out what we want with the IAOC. If there is no consensus on
> having the iChiefs play a less involved role then fine tuning the
> details doesn't make sense. If we gain consensus then fixing the
> Trust is doable.
>
>>>
>>> Your draft focuses on one area (that is, reducing the burden of
>>> these positions), but does not discuss any other aspects of
>>> making this change.  What might the negative aspects of
>>> delegating this responsibility be?  How will this be dealt with?
>
> Help me out.
>
> The main _potential_ negative aspect is a drop of iChiefs' awareness
> of what is going on; and the ability to directly influence
> decisions.
>
>
>>>
>>> Each of the positions (IETF Chair, IAB chair, ISOC President) are
>>> different in the way they are selected and this effects their
>>> ability to delegate their responsibility and who they might
>>> delegate it to.  For example, the IETF chair is selected by the
>>> NOMCOM and one of his/her responsibilities is to sit on the IAB,
>>> IAOC, and IETF Trust.  The IAB chair is selected by the IAB.  The
>>> ISOC president is hired by the ISOC Board of Trustees.
>>> Consequently, I think the authority to delegate differs and they
>>> should be considered separately.
>
> I agree, this needs discussion. But lets first see if there is any
> consensus on going down the path of getting the iChiefs out
> day-to-day IAOC business.
>
>
>>>
>>>> [as olaf:]
>>>>
>>>> I agree that the IETF chair needs to have a good oversight
>>>> about what goes on in the IETF, to a lesser extend it is good
>>>> that the IAB has that oversight too (specifically with respect
>>>> to its chartered responsibilities) but I wonder if a voting
>>>> membership is the appropriate instrument.
>>>
>>> Why not?  It does appear to work.
>
>
>
> Yes it works. But it consumes a lot of time too. IAOC retreat,
> meetings at the IETF, regular tele-chats, participation in sub
> committees, etc, etc...
>
> We have a responsibility to our leadership to make their jobs
> scalable and manageable. We need to have our leadership positions
> accessible to our peers, who may not have the support of their
> company for more than a half time job, or, not to forget, may not
> have the support of their families for the travel and the long
> evenings with telechats. Being effective in what committees and
> meetings one participates in is part of making the job scalable.
>
> The Best Current Practice is that the iChiefs _must_ participate in
> the IAOC, I like that _must_ being removed.
>
>
>>>
>>>> I believe effective oversight depends on having the appropriate
>>>> high level information and having the opportunity to timely
>>>> inject information that is needed to steer an outcome. An
>>>> alternative method for sharing and injecting is having regular
>>>> meetings between the I* chairs and the ISOC President/CEO. I
>>>> believe that such meetings are much more effective for the
>>>> parties involved than being exposed to all details.
>>>
>>> Do we really need to have another regular meeting?  Would this
>>> give the I* chairs more authority than they have now? Sort of an
>>> executive committee.  Would these meetings be public, have votes,
>>> have public minutes?
>
>
> It is not another meeting, it is replacing a lot of other meetings by
> one regular meeting that talks about issues at the right level of
> detail. Also, sharing information is not decision making. Russ and I
> had weekly calls planned (we didn't have them weekly, but that aside)
> to share information and brainstorm about potential issues.
>
> I don't see the 'more authority' argument, not in the context where
> one argues for direct votes in order to get effective oversight. I
> think that having a weekly iChiefs meeting gives less formal
> authority and (yes) a bit more informal authority.
>
>
>>>> This only an illustration of an instrument, there may be other
>>>> instruments for oversight as well. But I do not think the
>>>> ex-officio membership is the only method.
>>>
>>> It's not perfect but it is the one we have now and it is working.
>>> We should only change it if we are sure that it will improve the
>>> overall IASA operation.  I am seriously concerned about the
>>> current proposal.
>
>
> My question is whether there is any will to pursue a change to the
> BCP to work towards removing the _must_. (The Best Current Practice
> is that the iChiefs _must_ participate in the IAOC, I like that
> _must_ being removed.)
>
> I have seen Brian and Bob argue against. And not very many people
> argue 'for'
>
> - --Olaf
>
>
> ________________________________________________________
>
> Olaf M. Kolkman                        NLnet Labs
> http://www.nlnetlabs.nl/ I will start to use a new PGP key (ID
> 0x3B6AAA64) at the beginning of May 2011.
>
> -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17
> (Darwin) Comment: This message is locally signed. Comment: GPGTools -
> http://gpgtools.org
>
> iEYEARECAAYFAk2muAIACgkQtN/ca3YJIocKGwCggV3Z5um2cmWrUdXcba19SLNr
> cH4AoI0vilyFYRIa5Bx1j6i7T45klrYs =F6bJ -----END PGP SIGNATURE-----
> _______________________________________________ Ietf mailing list
> Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf

-- 

-------------------------------------------------------------------
"Reality:
      Yours to discover."
                                 -- ThinkingCat
Leslie Daigle
leslie@thinkingcat.com
-------------------------------------------------------------------

From housley@vigilsec.com  Thu Apr 14 16:22:45 2011
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id CDF77E0750 for <ietf@ietfc.amsl.com>; Thu, 14 Apr 2011 16:22:45 -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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tXGt89MeAj-x for <ietf@ietfc.amsl.com>; Thu, 14 Apr 2011 16:22:45 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfc.amsl.com (Postfix) with ESMTP id 4741FE06C4 for <ietf@ietf.org>; Thu, 14 Apr 2011 16:22:45 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 4F2DEF240A8; Thu, 14 Apr 2011 19:22:50 -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 Z2m-kcOv-IUC; Thu, 14 Apr 2011 19:22:40 -0400 (EDT)
Received: from [192.168.2.100] (pool-71-178-218-117.washdc.fios.verizon.net [71.178.218.117]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id D62D2F240A6; Thu, 14 Apr 2011 19:22:49 -0400 (EDT)
Subject: Re: IAOC: delegating ex-officio responsibility
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <8F2607B3-F58E-4786-A60D-4A2758E2C35E@gmail.com>
Date: Thu, 14 Apr 2011 19:22:43 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <FC7B14F4-47B7-4FF2-A72F-D9B8F2B4AA08@vigilsec.com>
References: <2BE582FA-2682-4232-9D83-23A03F01A0DB@NLnetLabs.nl>	<6.2.5.6.2.20110330073936.0e1899d0@resistor.net>	<E2E41FDE-3818-4513-9933-CB1E0326B43E@nlnetlabs.nl>	<6.2.5.6.2.20110330113947.0c948bc0@resistor.net>	<4D942843.4060804@gmail.com>	<6.2.5.6.2.20110331120351.09488990@resistor.net>	<4D955661.8050502@gmail.com>	<9C81C0F6-3ABE-4479-8C5E-C20C486D052A@gmail.com>	<82A347CC-BB19-4A73-8E8A-924FBAA92A5F@NLnetLabs.nl>	<84D6568B-18C9-47B2-A457-C51C2FB3351F@gmail.com> <5419FA805EF52E79D7822966@PST.JCK.COM> <4DA71408.3090704@gmail.com> <7220CC90-02B0-45B0-9113-236A933BBD16@vigilsec.com> <8F2607B3-F58E-4786-A60D-4A2758E2C35E@gmail.com>
To: Bob Hinden <bob.hinden@gmail.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: Thu, 14 Apr 2011 23:22:46 -0000

Bob:

>> The proposed update to BCP 101 permits further delegation of the IAOC =
voting position.  While I do not see myself taking advantage of this new =
feature, I do think we should give future IETF Chairs this option.  It =
is a cohesive part of the work that can be delegated.  Some coordination =
between the IETF Chair and the delegate would be necessary, but the time =
commitment would be significantly less than participating in the IAOC =
and a subset of its committees.
>=20
>=20
> This prompts me to ask a question.  Who would the IETF Chair delegate =
this responsibility to?  The draft doesn't specify. =20
>=20
> An Area Director is the obvious answer, except from what I understand =
ADs are also extremely busy.  This trades one problem for another.  If =
it is someone not on the IESG, then this is effectively turning into =
giving the IESG another IAOC slot to select.=20
>=20
> As a general comment on the draft, I think it needs to be clear as to =
who the delegation can be made to and how much authority is delegated.

I think that the delegate would have t be an IESG member, otherwise it =
the expected insight would not be provided.

Russ


From ole@cisco.com  Thu Apr 14 18:43:28 2011
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 8D9A7E07A9 for <ietf@ietfc.amsl.com>; Thu, 14 Apr 2011 18:43:28 -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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gd73MbQ4mi6a for <ietf@ietfc.amsl.com>; Thu, 14 Apr 2011 18:43:27 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by ietfc.amsl.com (Postfix) with ESMTP id B02E9E07A6 for <ietf@ietf.org>; Thu, 14 Apr 2011 18:43:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=431; q=dns/txt; s=iport; t=1302831807; x=1304041407; h=date:from:reply-to:to:subject:message-id:mime-version; bh=rNgsv4/RZBDsS2cg0WKlHoo0jjygzvJ/5munaXDK6LE=; b=kMuSzxEdSWgA/UuTxgwinlzquqbRONB+bbFgy1qRK5RLoYI/dFk/kBOn rsdL0W3IGYbK4VLVfWXzoICACxuSSe/DZATpixfQjpaiOFCPkBt3tcZA+ FACRH2rjaWTM8Qe4iqqv0aTK/lqlEUNM0rWIYYNyZilYlnk0V6oJ0rxHX c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhYFAE2ip02rRDoH/2dsb2JhbAAumH6MUXenVIJzDgGaDIMYglYEhVqMCA
X-IronPort-AV: E=Sophos;i="4.64,215,1301875200"; d="scan'208";a="681792959"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by sj-iport-6.cisco.com with ESMTP; 15 Apr 2011 01:43:27 +0000
Received: from [10.24.17.59] ([10.24.17.59]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p3F1hQPq017820 for <ietf@ietf.org>; Fri, 15 Apr 2011 01:43:26 GMT
Date: Thu, 14 Apr 2011 18:43:26 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: The IETF <ietf@ietf.org>
Subject: Flashback
Message-ID: <alpine.OSX.2.01.1104141839410.82851@173-11-110-133-sfba.hfc.comcastbusiness.net>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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: Fri, 15 Apr 2011 01:43:28 -0000

So, here we are celebrating 25 years of the IETF and it seems like 
only yesterday that I put together this slide deck of the 20 year
celebration:

http://www.yikes.com/~ole/store/IETF-20years.pdf

Enjoy!

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


From tme@americafree.tv  Thu Apr 14 18:57:36 2011
Return-Path: <tme@americafree.tv>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 28036E07BD for <ietf@ietfc.amsl.com>; Thu, 14 Apr 2011 18:57:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.299
X-Spam-Level: 
X-Spam-Status: No, score=-104.299 tagged_above=-999 required=5 tests=[AWL=4.300, BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8nQfoYqvmWE7 for <ietf@ietfc.amsl.com>; Thu, 14 Apr 2011 18:57:34 -0700 (PDT)
Received: from mail.americafree.tv (rossini.americafree.tv [63.105.122.34]) by ietfc.amsl.com (Postfix) with ESMTP id 7F417E07B3 for <ietf@ietf.org>; Thu, 14 Apr 2011 18:57:34 -0700 (PDT)
Received: from [IPv6:::1] (rossini.americafree.tv [63.105.122.34]) by mail.americafree.tv (Postfix) with ESMTP id DF86EA77B282; Thu, 14 Apr 2011 21:57:33 -0400 (EDT)
Subject: Re: IAOC: delegating ex-officio responsibility
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Marshall Eubanks <tme@americafree.tv>
In-Reply-To: <E19E3F13-90E4-48B0-9A6C-951DAA97D24E@nlnetlabs.nl>
Date: Thu, 14 Apr 2011 21:57:30 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <DE2E98CD-F146-4730-95C2-7B80A58A7D73@americafree.tv>
References: <2BE582FA-2682-4232-9D83-23A03F01A0DB@NLnetLabs.nl>	<6.2.5.6.2.20110330073936.0e1899d0@resistor.net>	<E2E41FDE-3818-4513-9933-CB1E0326B43E@nlnetlabs.nl>	<6.2.5.6.2.20110330113947.0c948bc0@resistor.net>	<4D942843.4060804@gmail.com>	<6.2.5.6.2.20110331120351.09488990@resistor.net>	<4D955661.8050502@gmail.com>	<9C81C0F6-3ABE-4479-8C5E-C20C486D052A@gmail.com>	<82A347CC-BB19-4A73-8E8A-924FBAA92A5F@NLnetLabs.nl> <84D6568B-18C9-47B2-A457-C51C2FB3351F@gmail.com> <4DA69F79.6030700@gmail.com> <E19E3F13-90E4-48B0-9A6C-951DAA97D24E@nlnetlabs.nl>
To: Olaf Kolkman <olaf@NLnetLabs.nl>
X-Mailer: Apple Mail (2.1081)
Cc: Bob Hinden <bob.hinden@gmail.com>, 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: Fri, 15 Apr 2011 01:57:36 -0000

On Apr 14, 2011, at 5:01 AM, Olaf Kolkman wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
>=20
> On Apr 14, 2011, at 9:17 AM, Brian E Carpenter wrote:
>=20
>> On 2011-04-14 06:19, Bob Hinden wrote:
>>> Olaf,
>>>=20
>>> On Apr 2, 2011, at 1:28 AM, Olaf Kolkman wrote:
>>>=20
>>>> [as editor:]
>>>>=20
>>>> It seems that the high order bit of this discussion circles
>>>> around the question on whether it a requirement for the
>>>> IETF Chair to have a voting position in order to
>>>> effectively perform oversight. Once we figured out where we
>>>> want to go with that we can think about delegation by the
>>>> chair vs appointment by the bodies and the implementation
>>>> details with respect to the trust.
>>>=20
>>> For the record, I don't agree with this summary.  That is, I
>>> still question the basic assumption in the proposal.  We have
>>> "running code" in the IASA model and it appears to work
>>> reasonable well.  Not perfect, of course.  In particular I
>>> think that having the IETF chair, IAB chair, and ISOC
>>> president as voting members of the IAOC (and IETF Trust) has
>>> worked very well.  It makes them an active part of decisions
>>> the IAOC and IETF Trust are making and helps keep the IAOC
>>> from getting disconnected from the community.  It also makes
>>> them share the responsibility for decisions by having their
>>> vote be publicly recorded.
>>=20
>> I agree. I think this responsibility should not be delegated.
>> It's fundamental to the success of the IETF (and the ISOC for
>> that matter - the IETF is a major source of ISOC's legitimacy).
>> The IAOC delegates execution to the IAD etc. - maybe the real
>> bug is that the IAOC itself needs to delegate more?
>>=20
>=20
>=20
>=20
> I agree the IASA model is working well and I also agree that the =
chairs have played an important role.=20
>=20
> But I am not convinced that it is the only way to keep the IAOC from =
getting disconnected from the community. To turn that argument around: =
If it is the case that we need the IAB chair, IETF chair and ISOC =
president [iChiefs] to keep the IAOC on track then why do we have NOMCOM =
appointments? One could easily argue that the NOMCOM appointments are =
made to keep the IAOC connected to the community.
>=20
> I also do not see why it 'it's fundamental to the success of the =
IETF'. I do agree that the iChiefs need to understand what is going on, =
there is no dispute about, but I question whether IAOC membership is =
best and most efficient instrument.
>=20
>=20
>=20
>>> I also don't understand what the effect of the proposal is on
>>> the IETF Trust.  Currently all IAOC members are members of
>>> the IETF Trust.  They have to sign a letter accepting this
>>> role.  I don't think it can then be delegated.
>>=20
>> It can't be delegated. However, a duly approved update to BCP101
>> can change the definition of the formal membership of the
>> IAOC, and that would automatically change the membership of
>> the Trust. An alternative would be a formal change to the Trust
>> Agreement, but since IANAL, I don't know whether a change to
>> allow delegation or proxies would be possible under the law of
>> the Commonwealth of Virginia, where the Trust was established.
>>=20
>=20
> I do not want to brush over this important detail. But, let us first =
figure out what we want with the IAOC. If there is no consensus on =
having the iChiefs play a less involved role then fine tuning the =
details doesn't make sense. If we gain consensus then fixing the Trust =
is doable.
>=20

Please note that, as I am sure you are aware, the consensus that would =
have to be gained to modify the Trust agreement is among the
Trustees.=20



>>>=20
>>> Your draft focuses on one area (that is, reducing the burden
>>> of these positions), but does not discuss any other aspects
>>> of making this change.  What might the negative aspects of
>>> delegating this responsibility be?  How will this be dealt
>>> with?
>=20
> Help me out.
>=20
> The main _potential_ negative aspect is a drop of iChiefs' awareness =
of what is going on; and the ability to directly influence decisions.
>=20

I think that you are neglecting the potential impact on the IAOC/Trust.=20=


When the IETF Chair or the IAB Chair speaks in the IAOC or the Trust on =
a matter in their area of responsibility, their words carry a lot of =
weight.=20
Their representative will inevitably lose some of that weight, and their =
use will thus change the balance in the IAOC and the Trust.=20

Suppose, for example, that the iChief in question has been negotiating =
some issue with the US DoC or the ITU or ICANN or a potential host =
country's IT Ministry. Such negotiations frequently impact either the =
IAOC or the Trust (or both) - in terms of the budget, sponsors,=20
meeting locations, etc.=20

Will their IAOC/Trust representative be part of any such negotiations as =
a matter of course ? If not, then they will not speak=20
authoritatively about them.  No matter how carefully they are briefed, =
there may be matters arising that the briefing did not
anticipate. That will for sure delay matters (as questions will have to =
them be relayed back and forth) and
may adversely affect the decisions made (when the representative thinks =
that they fully understand some issue, and do not). =20


Regards
Marshall

>=20
>>>=20
>>> Each of the positions (IETF Chair, IAB chair, ISOC President)
>>> are different in the way they are selected and this effects
>>> their ability to delegate their responsibility and who they
>>> might delegate it to.  For example, the IETF chair is
>>> selected by the NOMCOM and one of his/her responsibilities is
>>> to sit on the IAB, IAOC, and IETF Trust.  The IAB chair is
>>> selected by the IAB.  The ISOC president is hired by the ISOC
>>> Board of Trustees.  Consequently, I think the authority to
>>> delegate differs and they should be considered separately.
>=20
> I agree, this needs discussion. But lets first see if there is any =
consensus on going down the path of getting the iChiefs out day-to-day =
IAOC business.
>=20
>=20
>>>=20
>>>> [as olaf:]
>>>>=20
>>>> I agree that the IETF chair needs to have a good oversight
>>>> about what goes on in the IETF, to a lesser extend it is
>>>> good that the IAB has that oversight too (specifically with
>>>> respect to its chartered responsibilities) but I wonder if
>>>> a voting membership is the appropriate instrument.
>>>=20
>>> Why not?  It does appear to work.
>=20
>=20
>=20
> Yes it works. But it consumes a lot of time too. IAOC retreat, =
meetings at the IETF, regular tele-chats, participation in sub =
committees, etc, etc...=20
>=20
> We have a responsibility to our leadership to make their jobs scalable =
and manageable. We need to have our leadership positions accessible to =
our peers, who may not have the support of their company for more than a =
half time job, or, not to forget, may not have the support of their =
families for the travel and the long evenings with telechats. Being =
effective in what committees and meetings one participates in is part of =
making the job scalable.=20
>=20
> The Best Current Practice is that the iChiefs _must_ participate in =
the IAOC, I like that _must_ being removed.
>=20
>=20
>>>=20
>>>> I believe effective oversight depends on having the
>>>> appropriate high level information and having the
>>>> opportunity to timely inject information that is needed to
>>>> steer an outcome. An alternative method for sharing and
>>>> injecting is having regular meetings between the I* chairs
>>>> and the ISOC President/CEO. I believe that such meetings
>>>> are much more effective for the parties involved than being
>>>> exposed to all details.
>>>=20
>>> Do we really need to have another regular meeting?  Would
>>> this give the I* chairs more authority than they have now?
>>> Sort of an executive committee.  Would these meetings be
>>> public, have votes, have public minutes?
>=20
>=20
> It is not another meeting, it is replacing a lot of other meetings by =
one regular meeting that talks about issues at the right level of =
detail. Also, sharing information is not decision making. Russ and I had =
weekly calls planned (we didn't have them weekly, but that aside) to =
share information and brainstorm about potential issues.=20
>=20
> I don't see the 'more authority' argument, not in the context where =
one argues for direct votes in order to get effective oversight. I think =
that having a weekly iChiefs meeting gives less formal authority and =
(yes) a bit more informal authority.
>=20
>=20
>>>> This only an illustration of an instrument, there may be
>>>> other instruments for oversight as well. But I do not think
>>>> the ex-officio membership is the only method.
>>>=20
>>> It's not perfect but it is the one we have now and it is
>>> working.   We should only change it if we are sure that it
>>> will improve the overall IASA operation.  I am seriously
>>> concerned about the current proposal.
>=20
>=20
> My question is whether there is any will to pursue a change to the BCP =
to work towards removing the _must_. (The Best Current Practice is that =
the iChiefs _must_ participate in the IAOC, I like that _must_ being =
removed.)
>=20
> I have seen Brian and Bob argue against. And not very many people =
argue 'for'
>=20
> - --Olaf
>=20
>=20
> ________________________________________________________=20
>=20
> Olaf M. Kolkman                        NLnet Labs
> http://www.nlnetlabs.nl/           =20
> I will start to use a new PGP key (ID 0x3B6AAA64) at the beginning
> of May 2011.
>=20
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
> Comment: This message is locally signed.
> Comment: GPGTools - http://gpgtools.org
>=20
> iEYEARECAAYFAk2muAIACgkQtN/ca3YJIocKGwCggV3Z5um2cmWrUdXcba19SLNr
> cH4AoI0vilyFYRIa5Bx1j6i7T45klrYs
> =3DF6bJ
> -----END PGP SIGNATURE-----
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>=20


From i.grok@comcast.net  Thu Apr 14 20:22:26 2011
Return-Path: <i.grok@comcast.net>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id EBBD1E0755 for <ietf@ietfc.amsl.com>; Thu, 14 Apr 2011 20:22:26 -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, J_CHICKENPOX_25=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rOkUhVUyaFK1 for <ietf@ietfc.amsl.com>; Thu, 14 Apr 2011 20:22:26 -0700 (PDT)
Received: from qmta12.westchester.pa.mail.comcast.net (qmta12.westchester.pa.mail.comcast.net [76.96.59.227]) by ietfc.amsl.com (Postfix) with ESMTP id ECF19E0750 for <ietf@ietf.org>; Thu, 14 Apr 2011 20:22:25 -0700 (PDT)
Received: from omta07.westchester.pa.mail.comcast.net ([76.96.62.59]) by qmta12.westchester.pa.mail.comcast.net with comcast id XfF91g00B1GhbT85CfNSPy; Fri, 15 Apr 2011 03:22:26 +0000
Received: from odin.ulthar.us ([68.33.77.0]) by omta07.westchester.pa.mail.comcast.net with comcast id XfNS1g00G00PQ6U3TfNSR3; Fri, 15 Apr 2011 03:22:26 +0000
Received: from odin.ulthar.us (localhost [127.0.0.1]) by odin.ulthar.us (8.14.4/8.14.3) with ESMTP id p3F3MM21025922 for <ietf@ietf.org>; Thu, 14 Apr 2011 23:22:22 -0400
Received: (from draco@localhost) by odin.ulthar.us (8.14.4/8.14.4/Submit) id p3F3MMmN025920 for ietf@ietf.org; Thu, 14 Apr 2011 23:22:22 -0400
Date: Thu, 14 Apr 2011 23:22:22 -0400
From: Scott Schmit <i.grok@comcast.net>
To: ietf@ietf.org
Subject: Re: audio streaming archive...
Message-ID: <20110415032222.GB22852@odin.ulthar.us>
Mail-Followup-To: ietf@ietf.org
References: <201104140254.p3E2sMjk014471@fs4113.wdf.sap.corp> <4DA67EF0.4050209@bogus.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4DA67EF0.4050209@bogus.com>
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: Fri, 15 Apr 2011 03:22:27 -0000

On Wed, Apr 13, 2011 at 09:58:24PM -0700, Joel Jaeggli wrote:
> there was a naming convention issue on the channel5 recorder which I
> thought that we caught all of those by I could be wrong...
> 
> The contractor has the channel8 recorder and should be able toretrive
> the file.

Is there an ETA for the fix to that?

I listened to both the .mp3 and .mp3.1 file for wed-am ch8, and neither
sounds like the DANE session to me.

-- 
Scott Schmit

> On 4/13/11 7:54 PM, Martin Rex wrote:
> > Peter Saint-Andre wrote:
> >>
> >> On 3/29/11 2:16 AM, Joel Jaeggli wrote:
> >>
> >>> the long term home as with all other recordings is:
> >>>
> >>> http://www.ietf.org/audio/
> >>
> >> I receive a 403 Forbidden error there.
> > 
> > There seems to be an(other?) archive here:
> > http://ietf80streaming.dnsalias.net/ietf80/
> > 
> > I tried to listen to the DANE session from Wednesday morning
> > (should have been channel 8 according to the agenda),
> > but the ch8 wed-am file seems to be a copy of ch5 wed-am instead. :-(
> > 
> > -Martin

From narten@us.ibm.com  Thu Apr 14 21:53:10 2011
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 36171E06AE for <ietf@ietfc.amsl.com>; Thu, 14 Apr 2011 21:53:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.949
X-Spam-Level: 
X-Spam-Status: No, score=-105.949 tagged_above=-999 required=5 tests=[AWL=0.650, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kISJtGDEJM5B for <ietf@ietfc.amsl.com>; Thu, 14 Apr 2011 21:53:09 -0700 (PDT)
Received: from e32.co.us.ibm.com (e32.co.us.ibm.com [32.97.110.150]) by ietfc.amsl.com (Postfix) with ESMTP id 4F421E0668 for <ietf@ietf.org>; Thu, 14 Apr 2011 21:53:06 -0700 (PDT)
Received: from d03relay01.boulder.ibm.com (d03relay01.boulder.ibm.com [9.17.195.226]) by e32.co.us.ibm.com (8.14.4/8.13.1) with ESMTP id p3F4g42G010541 for <ietf@ietf.org>; Thu, 14 Apr 2011 22:42:04 -0600
Received: from d03av05.boulder.ibm.com (d03av05.boulder.ibm.com [9.17.195.85]) by d03relay01.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p3F4r4JV062970 for <ietf@ietf.org>; Thu, 14 Apr 2011 22:53:04 -0600
Received: from d03av05.boulder.ibm.com (loopback [127.0.0.1]) by d03av05.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id p3F4r4CA017644 for <ietf@ietf.org>; Thu, 14 Apr 2011 22:53:04 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.151.17]) by d03av05.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id p3F4r34E017617 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 14 Apr 2011 22:53:04 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id p3F4r2Ba011659 for <ietf@ietf.org>; Fri, 15 Apr 2011 00:53:03 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.4/8.14.4/Submit) id p3F4r2gt011647 for ietf@ietf.org; Fri, 15 Apr 2011 00:53:02 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201104150453.p3F4r2gt011647@rotala.raleigh.ibm.com>
Date: Fri, 15 Apr 2011 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-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 04:53:10 -0000

Total of 57 messages in the last 7 days.
 
script run at: Fri Apr 15 00:53:02 EDT 2011
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  8.77% |    5 |  7.70% |    35805 | bob.hinden@gmail.com
  5.26% |    3 |  4.54% |    21094 | housley@vigilsec.com
  1.75% |    1 |  7.14% |    33185 | chalikars@gmail.com
  3.51% |    2 |  5.22% |    24276 | olaf@nlnetlabs.nl
  3.51% |    2 |  4.94% |    22939 | ron.even.tlv@gmail.com
  3.51% |    2 |  4.46% |    20736 | mperumal@cisco.com
  3.51% |    2 |  3.99% |    18525 | leon.portman@nice.com
  3.51% |    2 |  3.89% |    18058 | john.elwell@siemens-enterprise.com
  3.51% |    2 |  3.46% |    16080 | brian.e.carpenter@gmail.com
  3.51% |    2 |  3.02% |    14042 | cyrus@daboo.name
  3.51% |    2 |  2.49% |    11556 | lear@cisco.com
  3.51% |    2 |  2.24% |    10392 | ole@cisco.com
  1.75% |    1 |  3.32% |    15451 | hallam@gmail.com
  1.75% |    1 |  3.20% |    14849 | leslie@thinkingcat.com
  1.75% |    1 |  3.00% |    13947 | tme@americafree.tv
  1.75% |    1 |  2.84% |    13175 | even.roni@huawei.com
  1.75% |    1 |  2.79% |    12957 | stpeter@stpeter.im
  1.75% |    1 |  2.02% |     9366 | douglm@rpi.edu
  1.75% |    1 |  2.00% |     9274 | moore@network-heretics.com
  1.75% |    1 |  1.90% |     8808 | dave.thewlis@calconnect.org
  1.75% |    1 |  1.85% |     8620 | john-ietf@jck.com
  1.75% |    1 |  1.70% |     7911 | barryleiba@computer.org
  1.75% |    1 |  1.65% |     7671 | tglassey@earthlink.net
  1.75% |    1 |  1.42% |     6599 | evnikita2@gmail.com
  1.75% |    1 |  1.35% |     6283 | narten@us.ibm.com
  1.75% |    1 |  1.33% |     6182 | tt@smartcomsoftware.com
  1.75% |    1 |  1.22% |     5655 | fred@cisco.com
  1.75% |    1 |  1.18% |     5471 | iljitsch@muada.com
  1.75% |    1 |  1.15% |     5337 | dworley@avaya.com
  1.75% |    1 |  1.13% |     5238 | sm@resistor.net
  1.75% |    1 |  1.12% |     5225 | dot@dotat.at
  1.75% |    1 |  1.10% |     5103 | i.grok@comcast.net
  1.75% |    1 |  1.06% |     4905 | msk@cloudmark.com
  1.75% |    1 |  1.03% |     4790 | joelja@bogus.com
  1.75% |    1 |  1.01% |     4693 | dougb@dougbarton.us
  1.75% |    1 |  1.00% |     4627 | amorris@amsl.com
  1.75% |    1 |  0.99% |     4588 | chair@ietf.org
  1.75% |    1 |  0.98% |     4575 | ben@estacado.net
  1.75% |    1 |  0.98% |     4538 | mail@sabahattin-gucukoglu.com
  1.75% |    1 |  0.94% |     4349 | mohta@necom830.hpcl.titech.ac.jp
  1.75% |    1 |  0.86% |     3995 | mrex@sap.com
  1.75% |    1 |  0.82% |     3831 | glen@amsl.com
--------+------+--------+----------+------------------------
100.00% |   57 |100.00% |   464701 | Total

From john.elwell@siemens-enterprise.com  Thu Apr 14 23:22:55 2011
Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id C9E7DE069D; Thu, 14 Apr 2011 23:22:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.924
X-Spam-Level: 
X-Spam-Status: No, score=-102.924 tagged_above=-999 required=5 tests=[AWL=-0.325, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id miRTmq+YKCS7; Thu, 14 Apr 2011 23:22:54 -0700 (PDT)
Received: from mail216.messagelabs.com (mail216.messagelabs.com [85.158.143.99]) by ietfc.amsl.com (Postfix) with SMTP id DE29CE0693; Thu, 14 Apr 2011 23:22:50 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: john.elwell@siemens-enterprise.com
X-Msg-Ref: server-15.tower-216.messagelabs.com!1302848569!2311714!1
X-StarScan-Version: 6.2.9; banners=-,-,-
X-Originating-IP: [62.134.46.9]
Received: (qmail 31408 invoked from network); 15 Apr 2011 06:22:49 -0000
Received: from unknown (HELO senmx11-mx) (62.134.46.9) by server-15.tower-216.messagelabs.com with SMTP; 15 Apr 2011 06:22:49 -0000
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx11-mx (Server) with ESMTP id 8FA501EB83E1; Fri, 15 Apr 2011 08:22:49 +0200 (CEST)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Fri, 15 Apr 2011 08:22:49 +0200
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: "Muthu ArulMozhi Perumal (mperumal)" <mperumal@cisco.com>, "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>, Leon Portman <Leon.Portman@nice.com>, "ietf@ietf.org" <ietf@ietf.org>
Date: Fri, 15 Apr 2011 08:22:48 +0200
Subject: RE: [siprec] Last Call: <draft-ietf-siprec-req-09.txt>(Use	Cases andRequirements	for SIP-based MediaRecording	(SIPREC))	toInformational RFC
Thread-Topic: [siprec] Last Call: <draft-ietf-siprec-req-09.txt>(Use	Cases andRequirements	for SIP-based MediaRecording	(SIPREC))	toInformational RFC
Thread-Index: Acv0WYBeRuGjGNBtTZSHeqn78QP5xwGEv6YwAAlHtwAAAvtH0AABcMXAAAdJn6AAAIZ7cAAHjozgABTz8IA=
Message-ID: <A444A0F8084434499206E78C106220CA0875EB5D69@MCHP058A.global-ad.net>
References: <20110406125020.17538.70016.idtracker@localhost><1D062974A4845E4D8A343C65380492020533BB70@XMB-BGL-414.cisco.com><A444A0F8084434499206E78C106220CA0875EB5A4E@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38AB73D00B@TLVMBX01.nice.com><A444A0F8084434499206E78C106220CA0875EB5B28@MCHP058A.global-ad.net> <07465C1D981ABC41A344374066AE1A2C38AB73D110@TLVMBX01.nice.com> <35BCE99A477D6A4986FB2216D8CF2CFD06009D00@XMB-BGL-417.cisco.com> <1D062974A4845E4D8A343C65380492020533BD38@XMB-BGL-414.cisco.com>
In-Reply-To: <1D062974A4845E4D8A343C65380492020533BD38@XMB-BGL-414.cisco.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
Cc: "siprec@ietf.org" <siprec@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 Apr 2011 06:22:56 -0000

So perhaps if we replace REQ-022 and REQ-023 with the requirement that Muth=
u has proposed and one further requirement, e.g.:

"REQ-022 The mechanism MUST provide means for facilitating synchronization =
of the
recorded media streams and metadata either at storage or at playback.

REQ-023 The mechanism MUST provide means for relating recordings to wall cl=
ock time."

John (as individual)=20

> -----Original Message-----
> From: Muthu ArulMozhi Perumal (mperumal) [mailto:mperumal@cisco.com]=20
> Sent: 14 April 2011 21:42
> To: Ram Mohan R (rmohanr); Leon Portman; Elwell, John; ietf@ietf.org
> Cc: siprec@ietf.org
> Subject: RE: [siprec] Last Call:=20
> <draft-ietf-siprec-req-09.txt>(Use Cases andRequirements for=20
> SIP-based MediaRecording (SIPREC)) toInformational RFC
>=20
> I agree with John that these seem more like part of a solution rather
> than actual requirements. In addition, sending the wallclock time at
> media start/end alone may not suffice for achieving inter-media
> synchronization and playback, instead we may need to send the=20
> wallclock
> time periodically, like RTCP. For e.g, if there is a codec=20
> renegotiation
> in CS the RTP timestamp can restart from a random value. If silence
> suppression is enabled there would be gaps in the RTP timestamp.=20
>=20
> These are things that need to be discussed as part of the solution --
> the requirement itself should be generic enough, like what I=20
> described.
> REQ-022 and REQ-023 we have doesn't seem to clearly indicate the
> purpose.
>=20
> Muthu=20
>=20
> |-----Original Message-----
> |From: Ram Mohan R (rmohanr)
> |Sent: Thursday, April 14, 2011 10:13 PM
> |To: Leon Portman; Elwell, John; Muthu ArulMozhi Perumal (mperumal);
> ietf@ietf.org
> |Cc: siprec@ietf.org
> |Subject: RE: [siprec] Last Call: <draft-ietf-siprec-req-09.txt>(Use
> Cases andRequirements for SIP-
> |based MediaRecording (SIPREC)) toInformational RFC
> |
> |We already have  attributes Start-Time / End-time in Media Stream
> block. This is for the same purpose
> |to indicate the wall clock time for start/end of media.
> |
> |Ram
> |
> |> -----Original Message-----
> |> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> |> Behalf Of Leon Portman
> |> Sent: Thursday, April 14, 2011 9:57 PM
> |> To: Elwell, John; Muthu ArulMozhi Perumal (mperumal); ietf@ietf.org
> |> Cc: siprec@ietf.org
> |> Subject: Re: [siprec] Last Call: <draft-ietf-siprec-req-09.txt>(Use
> |> Cases andRequirements for SIP-based MediaRecording (SIPREC))
> |> toInformational RFC
> |>
> |> I am not sure that having wall clock only for CS start is enough,
> |> especially for partial metadata update. I will prefer to have on
> media
> |> level
> |>
> |> Leon
> |>
> |> -----Original Message-----
> |> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> |> Sent: Thursday, April 14, 2011 3:58 PM
> |> To: Leon Portman; Muthu ArulMozhi Perumal (mperumal); ietf@ietf.org
> |> Cc: siprec@ietf.org
> |> Subject: RE: [siprec] Last Call:=20
> <draft-ietf-siprec-req-09.txt> (Use
> |> Cases andRequirements for SIP-based Media Recording (SIPREC))
> |> toInformational RFC
> |>
> |> Understood, but if we have wall clock time for the start of a CS,
> |> wouldn't that be sufficient? The new requirement would cover
> |> synchronization of all media start/stops relative to that time.
> |>
> |> John (as individual)
> |>
> |>
> |> > -----Original Message-----
> |> > From: Leon Portman [mailto:Leon.Portman@nice.com]
> |> > Sent: 14 April 2011 13:19
> |> > To: Elwell, John; Muthu ArulMozhi Perumal (mperumal);=20
> ietf@ietf.org
> |> > Cc: siprec@ietf.org
> |> > Subject: RE: [siprec] Last Call:
> |> > <draft-ietf-siprec-req-09.txt> (Use Cases andRequirements for
> |> > SIP-based Media Recording (SIPREC)) toInformational RFC
> |> >
> |> > Actually REQ-022 and REQ-023 describing not only requirement to
> |> > synchronize between different media streams but more importantly
> |> > ability to relate them to real world (wall) clock. It is not only
> |> > important to playback them correctly but also to know when it was
> |> > said.
> |> > One example is continue trading after closing hour (even for one
> |> > second is not allowed)
> |> >
> |> > And if these media are synchronized to wall clock then they are
> also
> |> > synchronized between them thus I am not sure if we need this
> |> > additional requirement.
> |> >
> |> > Thanks
> |> >
> |> > Leon
> |> >
> |> > -----Original Message-----
> |> > From: siprec-bounces@ietf.org
> |> > [mailto:siprec-bounces@ietf.org] On Behalf Of Elwell, John
> |> > Sent: Thursday, April 14, 2011 1:54 PM
> |> > To: Muthu ArulMozhi Perumal (mperumal); ietf@ietf.org
> |> > Cc: siprec@ietf.org
> |> > Subject: Re: [siprec] Last Call:
> |> > <draft-ietf-siprec-req-09.txt> (Use Cases andRequirements for
> |> > SIP-based Media Recording (SIPREC)) toInformational RFC
> |> >
> |> >
> |> >
> |> >
> |> > > -----Original Message-----
> |> > > From: siprec-bounces@ietf.org
> |> > > [mailto:siprec-bounces@ietf.org] On Behalf Of Muthu
> |> > ArulMozhi Perumal
> |> > > (mperumal)
> |> > > Sent: 14 April 2011 07:34
> |> > > To: ietf@ietf.org
> |> > > Cc: siprec@ietf.org
> |> > > Subject: Re: [siprec] Last Call:
> |> > > <draft-ietf-siprec-req-09.txt> (Use Cases andRequirements for
> |> > > SIP-based Media Recording (SIPREC)) toInformational RFC
> |> > >
> |> > > I've one major comment. It draft discusses synchronization
> |> > between the
> |> > > recorded media streams and synchronized playback, which
> |> > seem important
> |> > > for certain applications:
> |> > >
> |> > > <snip>
> |> > > Some applications require the recording of more than one
> |> > media stream,
> |> > > possibly of different types. Media are synchronized, either
> |> > at storage
> |> > > or at playback.
> |> > > </snip>
> |> > >
> |> > > However, in the requirements section it doesn't seem=20
> REQ-022 and
> |> > > REQ-023 are all that are need and sufficient to=20
> achieve this with
> |> > > needed precision. So, I would suggest adding another=20
> requirement
> as
> |> > > follows:
> |> > > The mechanism MUST provide means for facilitating
> |> > synchronization of
> |> > > the recorded media streams and metadata either at storage or at
> |> > > playback.
> |> > > This includes, but not limited to, the information=20
> needed as per
> |> > > REQ-022 and REQ-023.
> |> > [JRE] This seems a reasonable addition. I wonder if the new
> |> > requirement (first sentence only) is sufficient as a
> |> > **replacement** for REQ-022 and REQ-023. On reading REQ-022 and
> |> > REQ-023 again, it is not so clear what their purpose=20
> was, and they
> |> > seem to be more like a solution than a requirement.
> |> > One purpose would certainly be that covered by Muthu's new
> |> > requirement. Was there any other purpose?
> |> >
> |> > John
> |> >
> |> > >
> |> > > A nitpick:
> |> > > Use Case 8
> |> > > In cases where calls inside or between branches must=20
> be recorded,
> a
> |> > > centralized recording system in data centers together with
> |> > telephony
> |> > > infrastructure (e.g. PBX) me deployed.
> |> > >
> |> > > s/me/may be
> |> > >
> |> > > Muthu
> |> > >
> |> > > |-----Original Message-----
> |> > > |From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org]
> On
> |> > > Behalf Of The IESG
> |> > > |Sent: Wednesday, April 06, 2011 6:20 PM
> |> > > |To: IETF-Announce
> |> > > |Cc: siprec@ietf.org
> |> > > |Subject: [siprec] Last Call: <draft-ietf-siprec-req-09.txt>
> |> > > (Use Cases
> |> > > andRequirements for SIP-based
> |> > > |Media Recording (SIPREC)) toInformational RFC
> |> > > |
> |> > > |
> |> > > |The IESG has received a request from the SIP Recording WG
> |> > (siprec) to
> |> > > |consider the following document:
> |> > > |- 'Use Cases and Requirements for SIP-based Media
> |> > Recording (SIPREC)'
> |> > > |  <draft-ietf-siprec-req-09.txt> as an 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 2011-04-20. Exceptionally,
> |> > > comments may
> |> > > be
> |> > > |sent to iesg@ietf.org instead. In either case, please=20
> retain the
> |> > > |beginning of the Subject line to allow automated sorting.
> |> > > |
> |> > > |The file can be obtained via
> |> > > |http://datatracker.ietf.org/doc/draft-ietf-siprec-req/
> |> > > |
> |> > > |IESG discussion can be tracked via
> |> > > |http://datatracker.ietf.org/doc/draft-ietf-siprec-req/
> |> > > |
> |> > > |
> |> > > |
> |> > > |No IPR declarations have been submitted directly on this I-D.
> |> > > |_______________________________________________
> |> > > |siprec mailing list
> |> > > |siprec@ietf.org
> |> > > |https://www.ietf.org/mailman/listinfo/siprec
> |> > > _______________________________________________
> |> > > siprec mailing list
> |> > > siprec@ietf.org
> |> > > https://www.ietf.org/mailman/listinfo/siprec
> |> > >
> |> > _______________________________________________
> |> > siprec mailing list
> |> > siprec@ietf.org
> |> > https://www.ietf.org/mailman/listinfo/siprec
> |> >
> |> _______________________________________________
> |> siprec mailing list
> |> siprec@ietf.org
> |> https://www.ietf.org/mailman/listinfo/siprec
> =

From brian.e.carpenter@gmail.com  Fri Apr 15 01:05:34 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 9E12DE06AB for <ietf@ietfc.amsl.com>; Fri, 15 Apr 2011 01:05:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.753
X-Spam-Level: 
X-Spam-Status: No, score=-103.753 tagged_above=-999 required=5 tests=[AWL=-0.154, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8fPsnaHKVcRE for <ietf@ietfc.amsl.com>; Fri, 15 Apr 2011 01:05:33 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfc.amsl.com (Postfix) with ESMTP id BCD6EE0693 for <ietf@ietf.org>; Fri, 15 Apr 2011 01:05:32 -0700 (PDT)
Received: by wyb29 with SMTP id 29so2277789wyb.31 for <ietf@ietf.org>; Fri, 15 Apr 2011 01:05:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=ZquICyQGEb5oabRua1mY+NYQzvIqvSIIWOlobgD/gVU=; b=CXtzy9G7pzVpa/xduAsHW3DZx65mquIGVDj+cSvdZJNOEnxPnCD73ZGYvoJqEYqPoJ CtxcNgyjvbIpmNlrp4i/UC0+/iAmVzHfETCUghAjHg5FAlBxX+5lby1hrXpg0JTPBDp1 XtwtXPo36XAAgnwSa+XFv30dhIkTZ+uDaCWdw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=rob6uJ6oWf3m6clBVsz/v3y9Arx9JixiQLWrNIn11AQ9Rk+IjoJZr/JhwIvdV1oM0A juxQwZfnACWLy3na+ABUn7xRY02hc5i4A0VcgYXyIU2wkU2UGoS7v0nDMI5AeBtA9b0x qucaYgcGdqOtOXp6jxAKf2tnvt4mlLk8KOtI8=
Received: by 10.227.173.4 with SMTP id n4mr1768219wbz.132.1302854731972; Fri, 15 Apr 2011 01:05:31 -0700 (PDT)
Received: from [192.168.1.65] (host81-159-213-38.range81-159.btcentralplus.com [81.159.213.38]) by mx.google.com with ESMTPS id x1sm1447239wbh.19.2011.04.15.01.05.30 (version=SSLv3 cipher=OTHER); Fri, 15 Apr 2011 01:05:31 -0700 (PDT)
Message-ID: <4DA7FC49.60401@gmail.com>
Date: Fri, 15 Apr 2011 20:05:29 +1200
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: Olaf Kolkman <olaf@NLnetLabs.nl>
Subject: Re: IAOC: delegating ex-officio responsibility
References: <2BE582FA-2682-4232-9D83-23A03F01A0DB@NLnetLabs.nl>	<6.2.5.6.2.20110330073936.0e1899d0@resistor.net>	<E2E41FDE-3818-4513-9933-CB1E0326B43E@nlnetlabs.nl>	<6.2.5.6.2.20110330113947.0c948bc0@resistor.net>	<4D942843.4060804@gmail.com>	<6.2.5.6.2.20110331120351.09488990@resistor.net>	<4D955661.8050502@gmail.com>	<9C81C0F6-3ABE-4479-8C5E-C20C486D052A@gmail.com>	<82A347CC-BB19-4A73-8E8A-924FBAA92A5F@NLnetLabs.nl>	<84D6568B-18C9-47B2-A457-C51C2FB3351F@gmail.com> <5419FA805EF52E79D7822966@PST.JCK.COM> <4DA71408.3090704@gmail.com> <A0E8E415-123E-4643-98FC-6E022A1D7517@nlnetlabs.nl>
In-Reply-To: <A0E8E415-123E-4643-98FC-6E022A1D7517@nlnetlabs.nl>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: John C Klensin <john-ietf@jck.com>, Bob Hinden <bob.hinden@gmail.com>, 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: Fri, 15 Apr 2011 08:05:34 -0000

Olaf,

Thanks for posting this analysis. I'm on travel but will have
a careful look in a few days.

   Brian

On 2011-04-15 04:25, Olaf Kolkman wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
>> Certainly the IASA/IAD/IAOC reorganisation produced a noticeable
>> reduction in the IETF Chair workload, but what has changed since
>> http://tools.ietf.org/html/draft-carpenter-ietf-chair-tasks-00 ?
>> It would be good to have a similar analysis for the IAB chair role.
>>
>=20
>=20
> Below is a copy from a note I mailed to the IAB dd Feb 17, 2011. It wis=
 a variation on a note that I mailed to the Nomcom in 2009. It may not ma=
p exactly to what you are asking, but I believe it is close enough.
>=20
> Also, my wish to remove the _must_ in the 'iChiefs must be a member of =
the IAOC' best current practice is not a cherry picking act. The IAB has =
hired secretarial assistance for the agenda keeping, todo-list maintenanc=
e, minutes, etc. It is pushing forward the 'programs and initiatives' mod=
el that allows for subgroups to do a lot of actual work without the chair=
 driving that (i.e. much more formal delegation of activities to sub-grou=
ps with possibly external members).
>=20
>=20
>=20
>> Starting off with a personal note.
>> As you know the IAB chair is selected by and from the IAB membership o=
n a yearly basis. I first volunteered for the role of chair in March 2007=
=2E When I volunteered the first time I committed myself for 3 to 5 years=
 (obviously subject to Nomcom and IAB decision). A minimum of 3 years bec=
ause anything shorter is almost not worth the investment in the learning =
curve and the personal network that is needed to do the job effectively. =
Not longer than 5 years because of the fact that(much) longer terms tend =
to result in strong identification of a person with the role, sharpness a=
nd creativity decline, and possibly forms of mannerism in dealing with is=
sues.
>> From my perspective the most ideal scenario was (remember I wrote this=
 in 2009) that I'd be allowed by the Nomcom and the IAB to serve as a cha=
ir for one more year and then be around for another to allow for continui=
ty. In any case I think that it would be good for the Nomcom to look out =
for 'chair material'.
>> The main reason why I want to step down now is that there have been so=
me developments in the NLnet Labs situation that need my attention as dir=
ector of that organization that can not be combined with a 0.7 FTE that I=
 seem to be putting in at the moment.
>>
>> As for the responsibilities of the chair.
>> 	=E2=88=99 A number of 'mechanical/managerial' tasks:
>> 		=E2=88=99 Managing and organizing the IAB work-flow both on architec=
tural and organizational items
>> 		=E2=88=99 Setting priorities, planning activities to be aligned, ide=
ntify actionable items and make sure next steps are taken
>> 		=E2=88=99 Set up various meetings, manage agendas
>> 	=E2=88=99 Track minutes creation and publication
>> 		=E2=88=99 A chair's job can be relieved by having an executive direc=
tor that complements a chairs talents in organizing these activities.
>> 	=E2=88=99 Drive discussions
>> 		=E2=88=99 defining goals
>> 		=E2=88=99 moderate discussions
>> 		=E2=88=99 call consensus
>> 	=E2=88=99 Identify work items
>> 		=E2=88=99 Incoming appeals
>> 		=E2=88=99 Specific questions to the IAB from external bodies
>> 		=E2=88=99 Track (or make sure they are tracked) various developments=
 that may have impact on the IETF.
>> 	=E2=88=99 IASA/IAOC and Trust
>> 		=E2=88=99 As ex-officio membership, to represent IAB (and IRTF) matt=
ers
>> Because the chair is involved in all these activities (s)he becomes a =
de-facto information hub, besides because the chair often act as spokes p=
erson there isa tendency for all major organizational work items to gravi=
tate towards the chair, specifically if the interests of the other member=
s are mostly architectural. There are arguments that the load on the IAB =
chair is to high and it causes the job to be more than a half-time positi=
on (depending on personal effectively, delegation skill, organizational s=
kills and the quality of an executive director[*], it may even be closer =
to 3 quarters). And I believe that there are some structural questions on=
e can ask, such as in the ex-officio membership of the IASA/IOAC.
>> If we manage to get the Programs ran as more or less autonomous motors=
 that produce recommendations to the IAB it may be that the chairs job be=
comes relatively bearable.
>> While I think that with the Programs we have put a good structure in p=
lace it will need serious efforts of the next chair and the NEW IAB to ma=
ke working with programs part of the common mindset.
>> I think, and I realize that I am biased, that an IAB chair has some of=
 the following skills, properties:
>> 	=E2=88=99 Organizational: tracking actions, poking people, planning t=
he work load. A good Executive Director can be of tremendous help
>> 	=E2=88=99 Moderating and motivating: The ability to herd cats where o=
ccasionally a cat will have its claws out.
>> 	=E2=88=99 Diplomatic: In inter-organizational contacts taking the dip=
lomatic way to where you would like to end up.
>> 	=E2=88=99 Strategic: Constantly trying to up-level and see bigger pic=
ture while remembering that actionable progress needs to be made.
>> 	=E2=88=99 Open and sharing: Open to information received and consciou=
s about timely sharing of that information.
>> Note that I did not list technical/architectural skills in the above. =
Obviously an IAB chair needs to understand the technical issues but I do =
not believe that the IAB needs to be the 'chief architect'. While having =
an inspiring "Architect" leading the IAB would be nice I don't think it i=
s a requirement. More important is that architectural work is being organ=
ized and the chair allows others to excel in their technical expertise.
>> I am not saying that I had all the skills and properties above, but no=
t feeling the need to be "the technical champion" and not feeling the pre=
ssure from my fellow members to act like one helped a great deal.
>> FWIW I am committed to several IAB projects that do not automagically =
travel with the chair (e.g. RSE project and IANA strategy) and I plan to =
continue to be involved in those
>> Folding these requirements with the thoughts on alignment with the day=
-job of a chair candidate and the possible willingness of an employer to =
sponsor more than half-time of a function that has fairly little technica=
l return might be a challenge.
>> [*] as mentioned in my other note, a dedicated (i.e. payed staff) Exec=
utive Director may be a great way to reduce the time efforts needed by an=
 IAB chair, and other members. I should hurry to say that this is not men=
d as a comment on Dow, day-job interference plagues us all.
>>
>=20
> ________________________________________________________=20
>=20
> Olaf M. Kolkman                        NLnet Labs
> http://www.nlnetlabs.nl/           =20
> I will start to use a new PGP key (ID 0x3B6AAA64) at the beginning
> of May 2011.
>=20
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
> Comment: This message is locally signed.
> Comment: GPGTools - http://gpgtools.org
>=20
> iEYEARECAAYFAk2nIAgACgkQtN/ca3YJIocPVgCdEEPdzw/VTmkmgznbX73Nokan
> uIIAn37ABvdLR3z7Mtu7v2FVPJXWkWgr
> =3DC205
> -----END PGP SIGNATURE-----
>=20


From olaf@nlnetlabs.nl  Fri Apr 15 02:00:01 2011
Return-Path: <olaf@nlnetlabs.nl>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 99388E072B for <ietf@ietfc.amsl.com>; Fri, 15 Apr 2011 02:00:01 -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=[AWL=-0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QAltXvsqUA28 for <ietf@ietfc.amsl.com>; Fri, 15 Apr 2011 01:59:50 -0700 (PDT)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by ietfc.amsl.com (Postfix) with ESMTP id 25CB2E070D for <ietf@ietf.org>; Fri, 15 Apr 2011 01:59:50 -0700 (PDT)
Received: from aagje.fritz.box (xs4all.dacht.net [82.95.132.144]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.4/8.14.4) with ESMTP id p3F8xjhw014462 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 15 Apr 2011 10:59:46 +0200 (CEST) (envelope-from olaf@nlnetlabs.nl)
Subject: Re: IAOC: delegating ex-officio responsibility
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Olaf Kolkman <olaf@NLnetLabs.nl>
In-Reply-To: <4DA780FE.4010703@thinkingcat.com>
Date: Fri, 15 Apr 2011 10:59:40 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <BCF381B7-F48E-4012-BF26-1B6E934F46A9@nlnetlabs.nl>
References: <2BE582FA-2682-4232-9D83-23A03F01A0DB@NLnetLabs.nl>	<6.2.5.6.2.20110330073936.0e1899d0@resistor.net>	<E2E41FDE-3818-4513-9933-CB1E0326B43E@nlnetlabs.nl>	<6.2.5.6.2.20110330113947.0c948bc0@resistor.net>	<4D942843.4060804@gmail.com>	<6.2.5.6.2.20110331120351.09488990@resistor.net>	<4D955661.8050502@gmail.com>	<9C81C0F6-3ABE-4479-8C5E-C20C486D052A@gmail.com>	<82A347CC-BB19-4A73-8E8A-924FBAA92A5F@NLnetLabs.nl>	<84D6568B-18C9-47B2-A457-C51C2FB3351F@gmail.com>	<4DA69F79.6030700@gmail.com> <E19E3F13-90E4-48B0-9A6C-951DAA97D24E@nlnetlabs.nl> <4DA780FE.4010703@thinkingcat.com>
To: Leslie Daigle <leslie@thinkingcat.com>
X-Pgp-Agent: GPGMail 1.3.3
X-Mailer: Apple Mail (2.1084)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (open.nlnetlabs.nl [213.154.224.1]); Fri, 15 Apr 2011 10:59:46 +0200 (CEST)
Cc: Bob Hinden <bob.hinden@gmail.com>, 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: Fri, 15 Apr 2011 09:00:01 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On Apr 15, 2011, at 1:19 AM, Leslie Daigle wrote:

>=20
> Speaking as an individual, but an individual who helped set up this =
structure and who sat in the non-delegated ex officio IAB Chair position =
on the IAOC (and IETF Trust) for a couple of years, let me offer some =
comments.
>=20
> As Bob noted, elsewhere in the thread, your draft does not describe =
how to delegate responsibilities, it describes how to allow =
alternatively fill the positions.  And I believe that is a fatal flaw.
>=20
> The discussion on this thread certainly indicates that there isn't a =
clear grasp of what the responsibilities are for the positions in =
question.  The responsibilities are not:  show up for meetings/telecons, =
offer opinions about how to administer the IETF, and put in a vote when =
called upon, although those certainly are the functions expected.
>=20
> You described the IAB Chair as "hub" as if that was a bad thing.  =20

Certainly not my intention to qualify it as 'bad'. The note was written =
from the perspective of "what is the work load and what are the tasks". =
Not from the perspective of what are the responsibilities of the chair.=20=


> In fact, the one thing the Chair (of the IAB -- but it applies in =
analog to the IETF) needs to do is to support the IAB's functioning =
(through leadership, organization, note-taking, cajoling, listening, =
etc).  That doesn't mean the IAB Chair has to do the work of the whole =
IAB, but it does mean that an overall perspective is critical, and each =
Chair has to best organize her/himself to achieve the one task.

Agreed, being informed (as 'information hub') seems to be a prerequisite =
for gaining that overall perspective.

>=20
> In setting up the IAOC as it is, the intent was to inject the IAB =
Chair's overall perspective into the IAOC's discussions, including the =
support for IAB activities.  It was not a question of simply finding =
more credible people to put on the IAOC.
>=20
> If change is needed, the one path away from the fatal flaw seems to be =
to articulate the actual responsibilities of the IAB Chair (and IETF =
Chair and ISOC CEO, as appropriate) in the intended ex officio =
positions, such that it is possible to get agreement and external =
confirmation that the role is being properly fulfilled by whomever is =
selected to perform them.

Fair enough, and in addition, as a take-away from the thread so far:  =
those responsibilities go two ways: incoming and outgoing. It is not =
only the general perspective that the iChiefs bring to the IAOC but also =
what they take out of it. For instance; getting informed about the =
general state and health of things.

I guess I have some homework to do because at the moment I am not able =
to formulate the responsibility in a way that goes beyond (for the IAB =
role): providing the IAB perspective into IAOC decisions; and getting =
informed about IAOC activities that are relevant for the IAB and the =
activities it oversees.

- --Olaf

PS: Why does the following phrase come to mind: when in a hole stop =
digging...



________________________________________________________=20

Olaf M. Kolkman                        NLnet Labs
http://www.nlnetlabs.nl/           =20
I will start to use a new PGP key (ID 0x3B6AAA64) at the beginning
of May 2011.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: This message is locally signed.
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAk2oCPwACgkQtN/ca3YJIofdBgCgquirmPwR35riQZRzBvkPaoqb
tGEAoPkbV6MfxzEaPcp+2/gz9sea5AVr
=3DncXX
-----END PGP SIGNATURE-----

From jari.arkko@piuha.net  Fri Apr 15 03:59:12 2011
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id D6E73E06DB for <ietf@ietfc.amsl.com>; Fri, 15 Apr 2011 03:59:12 -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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QlA8HEIqEq3b for <ietf@ietfc.amsl.com>; Fri, 15 Apr 2011 03:59:12 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfc.amsl.com (Postfix) with ESMTP id B12A2E06C0 for <ietf@ietf.org>; Fri, 15 Apr 2011 03:59:11 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 326532CC4D; Fri, 15 Apr 2011 13:59:10 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hIowqUDuY9gu; Fri, 15 Apr 2011 13:59:09 +0300 (EEST)
Received: from [IPv6:::1] (unknown [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 715922CC2F; Fri, 15 Apr 2011 13:59:09 +0300 (EEST)
Message-ID: <4DA824FD.5020205@piuha.net>
Date: Fri, 15 Apr 2011 13:59:09 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
Subject: Re: IAOC: delegating ex-officio responsibility
References: <2BE582FA-2682-4232-9D83-23A03F01A0DB@NLnetLabs.nl>	<6.2.5.6.2.20110330073936.0e1899d0@resistor.net>	<E2E41FDE-3818-4513-9933-CB1E0326B43E@nlnetlabs.nl>	<6.2.5.6.2.20110330113947.0c948bc0@resistor.net>	<4D942843.4060804@gmail.com>	<6.2.5.6.2.20110331120351.09488990@resistor.net>	<4D955661.8050502@gmail.com>	<9C81C0F6-3ABE-4479-8C5E-C20C486D052A@gmail.com>	<82A347CC-BB19-4A73-8E8A-924FBAA92A5F@NLnetLabs.nl>	<84D6568B-18C9-47B2-A457-C51C2FB3351F@gmail.com>	<5419FA805EF52E79D7822966@PST.JCK.COM> <4DA71408.3090704@gmail.com>	<7220CC90-02B0-45B0-9113-236A933BBD16@vigilsec.com>	<8F2607B3-F58E-4786-A60D-4A2758E2C35E@gmail.com> <FC7B14F4-47B7-4FF2-A72F-D9B8F2B4AA08@vigilsec.com>
In-Reply-To: <FC7B14F4-47B7-4FF2-A72F-D9B8F2B4AA08@vigilsec.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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, 15 Apr 2011 10:59:13 -0000

A couple of observations from my personal viewpoint.

I tend to agree with others that we need to think about this in a 
top-down fashion, i.e. start from what is the problem that we intend to 
solve. I do have a serious concern about the workload for the people 
involved, particularly the chairs. But I wanted to make a couple of 
additional points.

First, I would not necessarily take it for granted that we have an 
infinite supply of people for various tasks. Finding an IESG member with 
enough time on their hands to participate the IAOC is not a given. We 
could of course always choose from outside the IESG, but again, most of 
the IETF participants are not here for administrative work, so while 
many can do it, I'm guessing some arm twisting would be required.

Second, even if you do find one, its not given that it provides the kind 
of connection between the chair and the IAOC that we want. Olaf pointed 
out that its bidirectional information transfer. Only a very small part 
of the IESG work is actually talking about IAOC matters, so I'm guessing 
that even if the delegate is another AD, the chair would still have to 
arrange extra time with this other AD in order to ensure that 
information transfer happens.

Third, I forget if it was Bob who noted that if we are strained by the 
tasks that we are doing, perhaps its time to outsource a bigger part of 
it to paid employees or businesses. For instance, I'm kind of hoping 
that 99% of the meeting selection load is on the IAD and the 
secretariat, not on the IAOC members. The members should set the policy, 
adjust the policy, and monitor implementation. If you are meeting every 
two weeks and deciding details then maybe you are on the wrong track. It 
should be the board, not the work horse.

Fourth, I think we are bringing on some of the load by our own actions. 
We have increased the number of entities that need to have a board and 
increased the amount of coordination needed. For instance, the RFC 
Editor was at one time one person, and today I'm honestly not sure I 
know how many entities it consists of. Of course, we needed much of this 
restructuring as the IETF has grown and has changed its operational mode 
also in other ways. But we should also watch it and avoid creating 
unnecessary structure where none is needed. I'm a little bit scared that 
adding a layer of delegation may cause the collective us to have more 
meetings, not less.

I also had a couple of thoughts on possible alternative directions to 
reducing the problem. Outsourcing more is one approach. Another one is 
to not have more people from the IESG and IAB attend the IAOC, but have 
people from the IAOC bring more information to these bodies. For 
instance, in the IESG we always have an "IAB report" but we don't 
normally have a Trust or IAOC report. Should we? A third direction is 
separating the role of the chairs as *working* members of the IAOC from 
their ability to attend and vote where needed. Would this detach the 
chairs too much? I don't know, but I think there might actually be less 
detaching than if you delegated your role away for a year. Russ, Olaf, 
how much do you normally participate the IAOC work? Are you in the 
subcommittees, do you work on details of agreements with our service 
providers?

Jari


From lars.eggert@nokia.com  Thu Apr 14 01:58:05 2011
Return-Path: <lars.eggert@nokia.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id A1AD3E066A for <ietf@ietfc.amsl.com>; Thu, 14 Apr 2011 01:58:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.536
X-Spam-Level: 
X-Spam-Status: No, score=-103.536 tagged_above=-999 required=5 tests=[AWL=0.952, BAYES_00=-2.599, GB_I_INVITATION=-2, SARE_NETPROD=0.111, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yHpg4S4AIscb for <ietf@ietfc.amsl.com>; Thu, 14 Apr 2011 01:58:04 -0700 (PDT)
Received: from mgw-da02.nokia.com (smtp.nokia.com [147.243.128.26]) by ietfc.amsl.com (Postfix) with ESMTP id A1E1EE0664 for <ietf@ietf.org>; Thu, 14 Apr 2011 01:58:04 -0700 (PDT)
Received: from mail.fit.nokia.com (esdhcp030222.research.nokia.com [172.21.30.222]) by mgw-da02.nokia.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p3E8w21T022507 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 14 Apr 2011 11:58:03 +0300
From: Lars Eggert <lars.eggert@nokia.com>
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.97 at fit.nokia.com
Content-Type: multipart/signed; boundary=Apple-Mail-24-194247365; protocol="application/pkcs7-signature"; micalg=sha1
Subject: Call for Nominations: Applied Networking Research Prize (ANRP)
Date: Thu, 14 Apr 2011 16:57:58 +0800
Message-Id: <A47B652B-898B-4243-981C-1702A9EF9514@nokia.com>
To: ietf@ietf.org
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (mail.fit.nokia.com); Thu, 14 Apr 2011 11:57:59 +0300 (EEST)
X-Nokia-AV: Clean
X-Mailman-Approved-At: Fri, 15 Apr 2011 07:54:25 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: anrp@isoc.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, 14 Apr 2011 08:58:05 -0000

--Apple-Mail-24-194247365
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii


                   CALL FOR NOMINATIONS:

          APPLIED NETWORKING RESEARCH PRIZE (ANRP)


*** Apply until May 8, 2011 for the ANR Prize for IETF-81,
*** July 24-29, 2011 in Quebec City, Canada!

The Applied Networking Research Prize (ANRP) is awarded for
recent results in applied networking research that are relevant
for transitioning into shipping Internet products and related
standardization efforts. Researchers with relevant, recently
published results are encouraged to apply for this prize, which
will offer them the opportunity to present and discuss their work
with the engineers, network operators, policy makers and
scientists that participate in the Internet Engineering Task
Force (IETF) and its research arm, the Internet Research Task
Force (IRTF). Third-party nominations for this prize are also
encouraged. The goal of the Applied Networking Research Prize
(ANRP) is to recognize the best new ideas in networking, and
bring them to the IETF and IRTF especially in cases where they
would not otherwise see much exposure or discussion.

The Applied Networking Research Prize (ANRP) consists of:

  * cash prize of $500 (USD)

  * invited talk at the IRTF Open Meeting

  * travel grant to attend the week-long IETF meeting
    (airfare, hotel, registration, stipend)

  * recognition at the IETF plenary

  * invitation to related social activities

  * potential for additional travel grants to future IETF
    meetings, based on community feedback

The Applied Networking Research Prize (ANRP) will be awarded
three times per year, in conjunction with the three annual IETF
meetings.


HOW TO APPLY

Applicants must nominate a peer-reviewed, recently-published,
original journal, conference or workshop paper. Both self
nominations (nominating one's own paper) and third-party
nominations (nominating someone else's paper) are encouraged. The
nominee must be one of the main authors of the nominated paper.

The nominated paper should provide a scientific foundation for
possible future IETF engineering work or IRTF experimentation,
analyze the behavior of Internet protocols in operational
deployments or realistic testbeds, make an important contribution
to the understanding of Internet scalability, performance,
reliability, security or capability, or otherwise be of relevance
to ongoing or future IETF or IRTF activities.

Applicants must briefly describe how the nominated paper relates
to these goals, and are encouraged to describe how presentation
of these research results will foster their transition into new
IETF engineering or IRTF experimentation, or otherwise seed new
activities that will have an impact on the real-world Internet.

The goal of the Applied Networking Research Prize (ANRP) is to
foster the transitioning of research results into real-world
benefits for the Internet. Therefore, applicants must indicate
that they (or the nominee, in case of third-party applications)
are available to attend the respective IETF meeting in person and
in its entirety.

Applications must include:

  * the name and email address of the nominee

  * a reference to the published nominated paper

  * a PDF copy of the nominated paper

  * a statement that describes how the nominated paper
    fulfills the goals of the award

  * a statement that the nominee is available to attend the
    respective IETF meeting in person and in its entirety

  * a brief biography or CV of the nominee

  * optionally, any other supporting information (link to
    nominee's web site, etc.)

*** Applications are submitted by email to anrp@isoc.org. ***


SELECTION PROCESS

A small selection committee comprised of individuals
knowledgeable about the IRTF, IETF and the broader networking
research community will evaluate the submissions against these
selection criteria. The goal is to select 1-2 submissions for the
Applied Networking Research Prize (ANRP) during each application
period. All applicants will be notified by email.


IMPORTANT DATES

Applications open:      April 11, 2011
Applications close:     May 8, 2011
Notifications:          May 31, 2011
IETF-81 Meeting:        July 24-29, 2011


SPONSORS

The Applied Networking Research Prize (ANRP) is supported by the
Internet Society (ISOC), as part of its Internet Research Award
Programme, in coordination with the Internet Research Task Force
(IRTF).


--Apple-Mail-24-194247365
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMRjCCBVAw
ggQ4oAMCAQICEGxdPUZzCwUJ8KBiJwH+bYgwDQYJKoZIhvcNAQEFBQAwgd0xCzAJBgNVBAYTAlVT
MRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y
azE7MDkGA1UECxMyVGVybXMgb2YgdXNlIGF0IGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEg
KGMpMDkxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDE3MDUGA1UEAxMuVmVyaVNpZ24g
Q2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0EgLSBHMzAeFw0xMDEwMTUwMDAwMDBaFw0x
MTEwMTUyMzU5NTlaMIIBEzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9S
UEEgSW5jb3JwLiBieSBSZWYuLExJQUIuTFREKGMpOTgxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZh
bGlkYXRlZDEzMDEGA1UECxMqRGlnaXRhbCBJRCBDbGFzcyAxIC0gTmV0c2NhcGUgRnVsbCBTZXJ2
aWNlMRQwEgYDVQQDFAtMYXJzIEVnZ2VydDEkMCIGCSqGSIb3DQEJARYVbGFycy5lZ2dlcnRAbm9r
aWEuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwolKEyOz/NQZJJlw0x9XBS9W
wCmabdY1fXpbWSdcaJiEWhQpRzSIC/pgIwCgaUW9g3JsWioXCawyjUVeg8xR42sR690f4z+OPAUm
3jokZxsuRaGX6fuPkPQomYAGz7htUHws/8FZIU+4dciETQf4vF5ptitJ+QZCVRCTLqisj6mG/kG4
65Op3G5/YZF9F/a390LdhuRP6vdY2Y+dqm8LDa0zmENPpoE98u1pIZGqCcnskN/nNBtEPd+a4lNh
ZSGnPuL4XCUSJYR9NB7FAYBvi5N7LSWHR3fspwa5EgpXynJcsLzaLA0iGfjFOBYFxul/07edmyw4
FIXuCIkaMDUfEwIDAQABo4HSMIHPMAkGA1UdEwQCMAAwRAYDVR0gBD0wOzA5BgtghkgBhvhFAQcX
ATAqMCgGCCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhMAsGA1UdDwQEAwIF
oDAdBgNVHSUEFjAUBggrBgEFBQcDBAYIKwYBBQUHAwIwUAYDVR0fBEkwRzBFoEOgQYY/aHR0cDov
L2luZGMxZGlnaXRhbGlkLWczLWNybC52ZXJpc2lnbi5jb20vSW5kQzFEaWdpdGFsSUQtRzMuY3Js
MA0GCSqGSIb3DQEBBQUAA4IBAQAlSTzUKqa3ZouKWFQfIJ+4l/KsztPnY4Onwzt8lqAmeiFPqOmf
kLTXbXDKtC6caFadNtyHpnsmQFFKXwhe5Z9/AaVSwryu6F9992DzYLp3j8PE0DSU0wmpUXUtp+rz
TFqJRkzB8RCBoq/TPBmkMPr68qB0TkU3dbYiVIvscOt1MRkdHiwG4wKQLyCf8XRRWqmMY6lbun7g
kiEWiris5StGKRvE5+e1SrcdnoZxIKQFF7Etr+4ftClrsDQWX9nRCEjYcmz4y/deq+HU8ylBaKZE
0ZJmcnYlAaD50OYWi0ckGDnKYyeMUEtCZJSV0otm2LqyIUAu9WPv/GNHt2ntjnUaMIIG7jCCBdag
AwIBAgIQcRVmBUrkkSFN6bxE+azT3DANBgkqhkiG9w0BAQUFADCByjELMAkGA1UEBhMCVVMxFzAV
BgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTow
OAYDVQQLEzEoYykgMTk5OSBWZXJpU2lnbiwgSW5jLiAtIEZvciBhdXRob3JpemVkIHVzZSBvbmx5
MUUwQwYDVQQDEzxWZXJpU2lnbiBDbGFzcyAxIFB1YmxpYyBQcmltYXJ5IENlcnRpZmljYXRpb24g
QXV0aG9yaXR5IC0gRzMwHhcNMDkwNTAxMDAwMDAwWhcNMTkwNDMwMjM1OTU5WjCB3TELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBO
ZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29t
L3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJp
U2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBDQSAtIEczMIIBIjANBgkqhkiG9w0B
AQEFAAOCAQ8AMIIBCgKCAQEA7cRH3yooHXwGa7vXITLJbBOP6bGNQU4099oL42r6ZYggCxET6Zvg
SU6Lb9UB0F8NR5GKWkx0Pj/GkQm7TDSejW6hglFi92l2WJYHr54UGAdPWr2f0jGyVBlzRmoZQhHs
EnMhjfXcMM3l2VYKMcU2bSkUl70t2olHGYjYSwQ967Y8Zx50ABMN0Ibak2f4MwOuGjxraXj2wCyO
4YM/d/mZ//6fUlrCtIcK2GypR8FUKWVDPkrAlh/Brfd3r2yxBF6+wbaULZeQLSfSux7pg2qE9sSy
riMGZSalJ1grByK0b6ZiSBp38tVQJ5op05b7KPW6JHZi44xZ6/tu1ULEvkHH9QIDAQABo4ICuTCC
ArUwNAYIKwYBBQUHAQEEKDAmMCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC52ZXJpc2lnbi5jb20w
EgYDVR0TAQH/BAgwBgEB/wIBADBwBgNVHSAEaTBnMGUGC2CGSAGG+EUBBxcBMFYwKAYIKwYBBQUH
AgEWHGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9jcHMwKgYIKwYBBQUHAgIwHhocaHR0cHM6Ly93
d3cudmVyaXNpZ24uY29tL3JwYTA0BgNVHR8ELTArMCmgJ6AlhiNodHRwOi8vY3JsLnZlcmlzaWdu
LmNvbS9wY2ExLWczLmNybDAOBgNVHQ8BAf8EBAMCAQYwbgYIKwYBBQUHAQwEYjBgoV6gXDBaMFgw
VhYJaW1hZ2UvZ2lmMCEwHzAHBgUrDgMCGgQUS2u5KJYGDLvQUjibKaxLB4shBRgwJhYkaHR0cDov
L2xvZ28udmVyaXNpZ24uY29tL3ZzbG9nbzEuZ2lmMC4GA1UdEQQnMCWkIzAhMR8wHQYDVQQDExZQ
cml2YXRlTGFiZWw0LTIwNDgtMTE4MB0GA1UdDgQWBBR5R2EIQf04BKJL57XM9UP2SSsR+DCB8QYD
VR0jBIHpMIHmoYHQpIHNMIHKMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4x
HzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxOjA4BgNVBAsTMShjKSAxOTk5IFZlcmlT
aWduLCBJbmMuIC0gRm9yIGF1dGhvcml6ZWQgdXNlIG9ubHkxRTBDBgNVBAMTPFZlcmlTaWduIENs
YXNzIDEgUHVibGljIFByaW1hcnkgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgLSBHM4IRAItbdVaE
VIULAM+vOEjOsaQwDQYJKoZIhvcNAQEFBQADggEBADlNz0GZgbWpBbVSOOk5hIls5DSoWufYbAlM
JBq6WaSHO3Mh8ZOBz79oY1pn/jWFK6HDXaNKwjoZ3TDWzE3v8dKBl8pUWkO/N4t6jhmND0OojPKv
YLMVirOVnDzgnrMnmKQ1chfl/Cpdh9OKDcLRRSr4wPSsKpM61a4ScAjr+zvid+zoK2Q1ds262uDR
yxTWcVibvtU+fbbZ6CTFJGZMXZEfdrMXPn8NxiGJL7M3uKH/XLJtSd5lUkL7DojS7Uodv0vj+Mxy
+kgOZY5JyNb4mZg7t5Q+MXEGh/psWVMu198r7V9jAKwV7QO4VRaMxmgD5yKocwuxvKDaUljdCg5/
wYIxggSLMIIEhwIBATCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMu
MR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1c2Ug
YXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29uYSBO
b3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2Ny
aWJlciBDQSAtIEczAhBsXT1GcwsFCfCgYicB/m2IMAkGBSsOAwIaBQCgggJtMBgGCSqGSIb3DQEJ
AzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDQxNDA4NTc1OFowIwYJKoZIhvcNAQkE
MRYEFNir9cPhDjERQq9d3j0MB3caWECcMIIBAwYJKwYBBAGCNxAEMYH1MIHyMIHdMQswCQYDVQQG
EwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5l
dHdvcmsxOzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20v
cnBhIChjKTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlT
aWduIENsYXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCEGxdPUZzCwUJ8KBiJwH+
bYgwggEFBgsqhkiG9w0BCRACCzGB9aCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlT
aWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJt
cyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMV
UGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1
YWwgU3Vic2NyaWJlciBDQSAtIEczAhBsXT1GcwsFCfCgYicB/m2IMA0GCSqGSIb3DQEBAQUABIIB
ADL7YMWUDYe9WYhxcTxcIGLyTS7cum6U+DE8iBqjPda2oX8ebAFF4RUZujTWXyUR+x3FCm+recwE
91dYvoTM6CAHQbp6N6KGi6Ync6b+eBjMvon/PIO1iXUie+up4FW9f9OYKVwccvmc3ZCcWNiAPygL
R7B55KwxR8q9ycqTlo3Xbmus6FiaMzDfj+7peIMfu4helSSZGrbL5zWOcU22PVkcwfTBT4ccgWe3
+i9Ksms5x2VNdwR60qVvxk7MQeCs/24zDn+U9YeFjV68HmYgnuf9vkJ16jRaBiQ5Sjy9nASSG3Ru
tQreZP4NL3hqcqKnappFIMx+HinuoUhVJ8ioD74AAAAAAAA=

--Apple-Mail-24-194247365--

From tom111.taylor@bell.net  Thu Apr 14 17:24:22 2011
Return-Path: <tom111.taylor@bell.net>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 89D71E07CE; Thu, 14 Apr 2011 17:24:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.598
X-Spam-Level: 
X-Spam-Status: No, score=-99.598 tagged_above=-999 required=5 tests=[AWL=-0.102, BAYES_00=-2.599, MANGLED_LIST=2.3, MSGID_FROM_MTA_HEADER=0.803, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RAV+ABDrPFp4; Thu, 14 Apr 2011 17:24:21 -0700 (PDT)
Received: from blu0-omc2-s38.blu0.hotmail.com (blu0-omc2-s38.blu0.hotmail.com [65.55.111.113]) by ietfc.amsl.com (Postfix) with ESMTP id BEAC6E061E; Thu, 14 Apr 2011 17:24:21 -0700 (PDT)
Received: from BLU0-SMTP16 ([65.55.111.73]) by blu0-omc2-s38.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 14 Apr 2011 17:24:21 -0700
X-Originating-IP: [64.231.151.226]
X-Originating-Email: [tom111.taylor@bell.net]
Message-ID: <BLU0-SMTP16BADEB237741F6CAC2F9ED8AC0@phx.gbl>
Received: from [192.168.2.17] ([64.231.151.226]) by BLU0-SMTP16.blu0.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Thu, 14 Apr 2011 17:24:20 -0700
Date: Thu, 14 Apr 2011 20:24:17 -0400
From: Tom Taylor <tom111.taylor@bell.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Ben Campbell <ben@estacado.net>
Subject: Re: Gen-ART LC Review of draft-ietf-ancp-protocol-15
References: <A2F4272F-30B3-4C85-BAAF-800858B988BF@estacado.net>
In-Reply-To: <A2F4272F-30B3-4C85-BAAF-800858B988BF@estacado.net>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 15 Apr 2011 00:24:20.0442 (UTC) FILETIME=[76A883A0:01CBFB03]
X-Mailman-Approved-At: Fri, 15 Apr 2011 07:54:25 -0700
Cc: General Area Review Team <gen-art@ietf.org>, The IETF <ietf@ietf.org>, draft-ietf-ancp-protocol.all@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 Apr 2011 00:24:22 -0000

Here are our considered responses, generated while I am still editing 
the -16 version, but I think they'll stick.

Tom Taylor

On 09/03/2011 7:08 PM, Ben Campbell 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-ancp-protocol-15 Reviewer: Ben Campbell Review
> Date: 2011-03-09 IETF LC End Date: 2011-03-09 IESG Telechat date: (if
> known)
>
> Summary: This draft is essentially ready for publication as a
> proposed standard. I have a few minor comments that might be worth
> considering prior to final publication.
>
> Major issues:
>
> None
>
> Minor issues:
>
> -- section 1.1: "This specification uses requirements language in
> lower case and between quotation marks (e.g., "must") to denote
> requirements on the interface between ANCP and the control
> application. Such requirements are inherently untestable but need to
> be taken into account by the implementor."
>
> I must admit to be curious as to the goal of this approach to
> normative language. I don't necessarily think it's a problem--I'm
> just calling it out as unusual in case anyone else cares.

[PTT] The intention was to call out potential work items for the 
Broadband Forum. We agreed in Prague to either drop the text concerned 
or replace it by narrative descriptions where desirable.
>
> -- section 3.1, definition of "Identifier"
>
> Is there any concern about distinguishing between the two
> (effectively different) protocols with the same value?

[PTT] This issue drew a lot of comment/discusses from the IESG. The 
final resolution was to make ANCP stand alone (RFC 3292 purely 
informational) and to set up a joint registry for GSMP and ANCP versions 
(1-3 for GSMP, 50+ for ANCP). The key differentiator between the two 
protocols would therefore be the version number, which comes at the 
beginning of every message.
>
> -- section 3.2, 2nd to last paragraph: "Port 6068 is used for TCP
> connection."
>
> Is this a default, or is it required to always be 6068?

[PTT] The list decision was to make it mandatory.
>
> -- section 3.5.2, 2nd paragraph: "It is RECOMMENDED that both ends
> specify the same timer value;"
>
> What are the implications if they dont?

[PTT] The timer is related to liveness testing exchanges. One side sends 
an ACK on timer expiry, the other returns an ACK. It doesn't seem 
necessary to repeat the exchange with the other side being the 
initiator. The second exchange can be avoided by adding the instruction 
that when an ACK is received, the receiver resets its timer.
>
> -- 3.6.1.4, Code value 7, recommended action : "If multiple instances
> of this error occur..."
>
> Can you provide any guidance on how many? I'm not asking for an exact
> count, but a general idea would be helpful.
>
[PTT] I provided an analysis to the list yesterday showing that this 
error can never actually occur. The error is defined in GSMPv3, but if 
you make the assumption that multiple adjacencies can be multiplexed 
over the same TCP connection (something the WG decided a year or two 
ago), messages get demultiplexed by Partition ID. Thus a message with 
the "wrong Partition ID" never gets steered to an adjacency where it is 
wrong. (It is dropped silently if the ID isn't in use.)
>
> Nits/editorial comments:
>
> -- section 1, 1st paragraph:
>
> Please expand QoS on first mention

[PTT] Done.
>
> -- 3.1, RFC Editor's Note:
>
> Any reason not to make the change in the draft prior to approval?
>
[PTT] Done. Also got rid of sub-version and just specified the version 
to be 50 (0x32).

> -- 5.1.2, heading before first bullet: "As normative requirements on
> ANCP agents conforming to this section:"
>
> I don't follow the sentence structure for this heading.

[PTT] Rephrased to: "ANCP agents conforming to this section MUST satisfy 
the following requirements:"
>
> -- 9.2, general:
>
> Can you reference the explicit URLs for the mentioned existing
> registries?
>
[PTT] Will do, but with independence from RFC 3292, the only existing 
one that will be referenced relates to port assignments.

From rmohanr@cisco.com  Thu Apr 14 09:42:45 2011
Return-Path: <rmohanr@cisco.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 22A02E079C; Thu, 14 Apr 2011 09:42:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.517
X-Spam-Level: 
X-Spam-Status: No, score=-10.517 tagged_above=-999 required=5 tests=[AWL=0.082, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Yt+FANOOE2vD; Thu, 14 Apr 2011 09:42:43 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfc.amsl.com (Postfix) with ESMTP id 2ED66E0663; Thu, 14 Apr 2011 09:42:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=rmohanr@cisco.com; l=7021; q=dns/txt; s=iport; t=1302799363; x=1304008963; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=6rUe3sEq4q/mACJdc92WAmc4p0YxXstExn5GPFIStGw=; b=mJsXDRQu1mfYueGrh0+2SgYlHp8ANlg218gJfXYMxzzR26m3TlIPg00o Zx5LpMvHWrUbGSc70v2uRRpFfS76emJ6MmdTJb9+drltcxmZrMIe8vm9S 4vgHesS8qxGwSXz/FfsbynMWVnSyD6fOIWJLuexGqOY300afJUBQm1GAm k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AuQAAP8ip02Q/khNgWdsb2JhbACXeY19FAEBFiYlpEOcfoIhg00EhViMEQ
X-IronPort-AV: E=Sophos;i="4.64,212,1301875200"; d="scan'208";a="25742336"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-2.cisco.com with ESMTP; 14 Apr 2011 16:42:42 +0000
Received: from xbh-bgl-412.cisco.com (xbh-bgl-412.cisco.com [72.163.129.202]) by ams-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p3EGgfs1007873; Thu, 14 Apr 2011 16:42:41 GMT
Received: from xmb-bgl-417.cisco.com ([72.163.129.213]) by xbh-bgl-412.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 14 Apr 2011 22:12:40 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [siprec] Last Call: <draft-ietf-siprec-req-09.txt>(Use	Cases	andRequirements	for SIP-based MediaRecording	(SIPREC))	toInformational RFC
Date: Thu, 14 Apr 2011 22:12:39 +0530
Message-ID: <35BCE99A477D6A4986FB2216D8CF2CFD06009D00@XMB-BGL-417.cisco.com>
In-Reply-To: <07465C1D981ABC41A344374066AE1A2C38AB73D110@TLVMBX01.nice.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] Last Call: <draft-ietf-siprec-req-09.txt>(Use	Cases	andRequirements	for SIP-based MediaRecording	(SIPREC))	toInformational RFC
Thread-Index: Acv0WYBeRuGjGNBtTZSHeqn78QP5xwGEv6YwAAlHtwAAAvtH0AABcMXAAAdJn6AAAIZ7cA==
References: <20110406125020.17538.70016.idtracker@localhost><1D062974A4845E4D8A343C65380492020533BB70@XMB-BGL-414.cisco.com><A444A0F8084434499206E78C106220CA0875EB5A4E@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38AB73D00B@TLVMBX01.nice.com><A444A0F8084434499206E78C106220CA0875EB5B28@MCHP058A.global-ad.net> <07465C1D981ABC41A344374066AE1A2C38AB73D110@TLVMBX01.nice.com>
From: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>
To: "Leon Portman" <Leon.Portman@nice.com>, "Elwell, John" <john.elwell@siemens-enterprise.com>, "Muthu ArulMozhi Perumal (mperumal)" <mperumal@cisco.com>, <ietf@ietf.org>
X-OriginalArrivalTime: 14 Apr 2011 16:42:40.0734 (UTC) FILETIME=[F8587FE0:01CBFAC2]
X-Mailman-Approved-At: Fri, 15 Apr 2011 07:54:25 -0700
Cc: siprec@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 Apr 2011 16:42:45 -0000

We already have  attributes Start-Time / End-time in Media Stream block.
This is for the same purpose to indicate the wall clock time for
start/end of media.

Ram

> -----Original Message-----
> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> Behalf Of Leon Portman
> Sent: Thursday, April 14, 2011 9:57 PM
> To: Elwell, John; Muthu ArulMozhi Perumal (mperumal); ietf@ietf.org
> Cc: siprec@ietf.org
> Subject: Re: [siprec] Last Call: <draft-ietf-siprec-req-09.txt>(Use
> Cases andRequirements for SIP-based MediaRecording (SIPREC))
> toInformational RFC
>=20
> I am not sure that having wall clock only for CS start is enough,
> especially for partial metadata update. I will prefer to have on media
> level
>=20
> Leon
>=20
> -----Original Message-----
> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> Sent: Thursday, April 14, 2011 3:58 PM
> To: Leon Portman; Muthu ArulMozhi Perumal (mperumal); ietf@ietf.org
> Cc: siprec@ietf.org
> Subject: RE: [siprec] Last Call: <draft-ietf-siprec-req-09.txt> (Use
> Cases andRequirements for SIP-based Media Recording (SIPREC))
> toInformational RFC
>=20
> Understood, but if we have wall clock time for the start of a CS,
> wouldn't that be sufficient? The new requirement would cover
> synchronization of all media start/stops relative to that time.
>=20
> John (as individual)
>=20
>=20
> > -----Original Message-----
> > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > Sent: 14 April 2011 13:19
> > To: Elwell, John; Muthu ArulMozhi Perumal (mperumal); ietf@ietf.org
> > Cc: siprec@ietf.org
> > Subject: RE: [siprec] Last Call:
> > <draft-ietf-siprec-req-09.txt> (Use Cases andRequirements for
> > SIP-based Media Recording (SIPREC)) toInformational RFC
> >
> > Actually REQ-022 and REQ-023 describing not only requirement to
> > synchronize between different media streams but more importantly
> > ability to relate them to real world (wall) clock. It is not only
> > important to playback them correctly but also to know when it was
> > said.
> > One example is continue trading after closing hour (even for one
> > second is not allowed)
> >
> > And if these media are synchronized to wall clock then they are also
> > synchronized between them thus I am not sure if we need this
> > additional requirement.
> >
> > Thanks
> >
> > Leon
> >
> > -----Original Message-----
> > From: siprec-bounces@ietf.org
> > [mailto:siprec-bounces@ietf.org] On Behalf Of Elwell, John
> > Sent: Thursday, April 14, 2011 1:54 PM
> > To: Muthu ArulMozhi Perumal (mperumal); ietf@ietf.org
> > Cc: siprec@ietf.org
> > Subject: Re: [siprec] Last Call:
> > <draft-ietf-siprec-req-09.txt> (Use Cases andRequirements for
> > SIP-based Media Recording (SIPREC)) toInformational RFC
> >
> >
> >
> >
> > > -----Original Message-----
> > > From: siprec-bounces@ietf.org
> > > [mailto:siprec-bounces@ietf.org] On Behalf Of Muthu
> > ArulMozhi Perumal
> > > (mperumal)
> > > Sent: 14 April 2011 07:34
> > > To: ietf@ietf.org
> > > Cc: siprec@ietf.org
> > > Subject: Re: [siprec] Last Call:
> > > <draft-ietf-siprec-req-09.txt> (Use Cases andRequirements for
> > > SIP-based Media Recording (SIPREC)) toInformational RFC
> > >
> > > I've one major comment. It draft discusses synchronization
> > between the
> > > recorded media streams and synchronized playback, which
> > seem important
> > > for certain applications:
> > >
> > > <snip>
> > > Some applications require the recording of more than one
> > media stream,
> > > possibly of different types. Media are synchronized, either
> > at storage
> > > or at playback.
> > > </snip>
> > >
> > > However, in the requirements section it doesn't seem REQ-022 and
> > > REQ-023 are all that are need and sufficient to achieve this with
> > > needed precision. So, I would suggest adding another requirement
as
> > > follows:
> > > The mechanism MUST provide means for facilitating
> > synchronization of
> > > the recorded media streams and metadata either at storage or at
> > > playback.
> > > This includes, but not limited to, the information needed as per
> > > REQ-022 and REQ-023.
> > [JRE] This seems a reasonable addition. I wonder if the new
> > requirement (first sentence only) is sufficient as a
> > **replacement** for REQ-022 and REQ-023. On reading REQ-022 and
> > REQ-023 again, it is not so clear what their purpose was, and they
> > seem to be more like a solution than a requirement.
> > One purpose would certainly be that covered by Muthu's new
> > requirement. Was there any other purpose?
> >
> > John
> >
> > >
> > > A nitpick:
> > > Use Case 8
> > > In cases where calls inside or between branches must be recorded,
a
> > > centralized recording system in data centers together with
> > telephony
> > > infrastructure (e.g. PBX) me deployed.
> > >
> > > s/me/may be
> > >
> > > Muthu
> > >
> > > |-----Original Message-----
> > > |From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> > > Behalf Of The IESG
> > > |Sent: Wednesday, April 06, 2011 6:20 PM
> > > |To: IETF-Announce
> > > |Cc: siprec@ietf.org
> > > |Subject: [siprec] Last Call: <draft-ietf-siprec-req-09.txt>
> > > (Use Cases
> > > andRequirements for SIP-based
> > > |Media Recording (SIPREC)) toInformational RFC
> > > |
> > > |
> > > |The IESG has received a request from the SIP Recording WG
> > (siprec) to
> > > |consider the following document:
> > > |- 'Use Cases and Requirements for SIP-based Media
> > Recording (SIPREC)'
> > > |  <draft-ietf-siprec-req-09.txt> as an 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 2011-04-20. 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.
> > > |
> > > |The file can be obtained via
> > > |http://datatracker.ietf.org/doc/draft-ietf-siprec-req/
> > > |
> > > |IESG discussion can be tracked via
> > > |http://datatracker.ietf.org/doc/draft-ietf-siprec-req/
> > > |
> > > |
> > > |
> > > |No IPR declarations have been submitted directly on this I-D.
> > > |_______________________________________________
> > > |siprec mailing list
> > > |siprec@ietf.org
> > > |https://www.ietf.org/mailman/listinfo/siprec
> > > _______________________________________________
> > > siprec mailing list
> > > siprec@ietf.org
> > > https://www.ietf.org/mailman/listinfo/siprec
> > >
> > _______________________________________________
> > siprec mailing list
> > siprec@ietf.org
> > https://www.ietf.org/mailman/listinfo/siprec
> >
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec

From eckelcu@cisco.com  Thu Apr 14 16:29:21 2011
Return-Path: <eckelcu@cisco.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 87F42E06C4; Thu, 14 Apr 2011 16:29:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.393
X-Spam-Level: 
X-Spam-Status: No, score=-10.393 tagged_above=-999 required=5 tests=[AWL=0.206, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9oCZkSyg6EoL; Thu, 14 Apr 2011 16:29:20 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by ietfc.amsl.com (Postfix) with ESMTP id 88EDDE0794; Thu, 14 Apr 2011 16:29:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eckelcu@cisco.com; l=9502; q=dns/txt; s=iport; t=1302823759; x=1304033359; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=QDdZ+c3W8XjRN73JvdYUW2cpG5YTakJDlJ4FqptvlS0=; b=hIy+YLmy1xQTW7W2yfJb7PsLSi8JcV7v7Iv0zrFDMWO+I7JGP9XhQagz nkWlqAAOHak2chLUul96Dl90W6KjjcEmU7B4QIclGF7QPS0U06OiPouqR dyacVOzbh2MhhT50TTuOY+K4r7vNlYAwfcF1XM+5IlbNdyoDqofLwXMUl c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Al0BACSCp02rRDoG/2dsb2JhbACXf41+d6cnnHWCIYNNBIVajA8
X-IronPort-AV: E=Sophos;i="4.64,214,1301875200"; d="scan'208";a="337779740"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by sj-iport-2.cisco.com with ESMTP; 14 Apr 2011 23:29:18 +0000
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p3ENTIwS028622; Thu, 14 Apr 2011 23:29:18 GMT
Received: from xmb-sjc-234.amer.cisco.com ([128.107.191.111]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 14 Apr 2011 16:29:18 -0700
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [siprec] Last Call:<draft-ietf-siprec-req-09.txt>(Use	Cases	andRequirements	forSIP-based MediaRecording	(SIPREC))	toInformational RFC
Date: Thu, 14 Apr 2011 16:29:18 -0700
Message-ID: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C0408A56E@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <1D062974A4845E4D8A343C65380492020533BD38@XMB-BGL-414.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] Last Call:<draft-ietf-siprec-req-09.txt>(Use	Cases	andRequirements	forSIP-based MediaRecording	(SIPREC))	toInformational RFC
Thread-Index: Acv0WYBeRuGjGNBtTZSHeqn78QP5xwGEv6YwAAlHtwAAAvtH0AABcMXAAAdJn6AAAIZ7cAAHjozgAAa08QA=
References: <20110406125020.17538.70016.idtracker@localhost><1D062974A4845E4D8A343C65380492020533BB70@XMB-BGL-414.cisco.com><A444A0F8084434499206E78C106220CA0875EB5A4E@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38AB73D00B@TLVMBX01.nice.com><A444A0F8084434499206E78C106220CA0875EB5B28@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38AB73D110@TLVMBX01.nice.com><35BCE99A477D6A4986FB2216D8CF2CFD06009D00@XMB-BGL-417.cisco.com> <1D062974A4845E4D8A343C65380492020533BD38@XMB-BGL-414.cisco.com>
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Muthu ArulMozhi Perumal (mperumal)" <mperumal@cisco.com>, "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>, "Leon Portman" <Leon.Portman@nice.com>, "Elwell, John" <john.elwell@siemens-enterprise.com>, <ietf@ietf.org>
X-OriginalArrivalTime: 14 Apr 2011 23:29:18.0632 (UTC) FILETIME=[C6A04A80:01CBFAFB]
X-Mailman-Approved-At: Fri, 15 Apr 2011 07:54:25 -0700
Cc: siprec@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 Apr 2011 23:29:21 -0000

I was thinking we needed a way to synchronize media from multiple CSs,
which may be received by the SRS from one or more SRCs. Is this not a
requirement?

Thanks,
Charles

> -----Original Message-----
> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
Behalf Of Muthu ArulMozhi Perumal
> (mperumal)
> Sent: Thursday, April 14, 2011 1:42 PM
> To: Ram Mohan R (rmohanr); Leon Portman; Elwell, John; ietf@ietf.org
> Cc: siprec@ietf.org
> Subject: Re: [siprec] Last Call:<draft-ietf-siprec-req-09.txt>(Use
Cases andRequirements forSIP-based
> MediaRecording (SIPREC)) toInformational RFC
>=20
> I agree with John that these seem more like part of a solution rather
> than actual requirements. In addition, sending the wallclock time at
> media start/end alone may not suffice for achieving inter-media
> synchronization and playback, instead we may need to send the
wallclock
> time periodically, like RTCP. For e.g, if there is a codec
renegotiation
> in CS the RTP timestamp can restart from a random value. If silence
> suppression is enabled there would be gaps in the RTP timestamp.
>=20
> These are things that need to be discussed as part of the solution --
> the requirement itself should be generic enough, like what I
described.
> REQ-022 and REQ-023 we have doesn't seem to clearly indicate the
> purpose.
>=20
> Muthu
>=20
> |-----Original Message-----
> |From: Ram Mohan R (rmohanr)
> |Sent: Thursday, April 14, 2011 10:13 PM
> |To: Leon Portman; Elwell, John; Muthu ArulMozhi Perumal (mperumal);
> ietf@ietf.org
> |Cc: siprec@ietf.org
> |Subject: RE: [siprec] Last Call: <draft-ietf-siprec-req-09.txt>(Use
> Cases andRequirements for SIP-
> |based MediaRecording (SIPREC)) toInformational RFC
> |
> |We already have  attributes Start-Time / End-time in Media Stream
> block. This is for the same purpose
> |to indicate the wall clock time for start/end of media.
> |
> |Ram
> |
> |> -----Original Message-----
> |> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> |> Behalf Of Leon Portman
> |> Sent: Thursday, April 14, 2011 9:57 PM
> |> To: Elwell, John; Muthu ArulMozhi Perumal (mperumal); ietf@ietf.org
> |> Cc: siprec@ietf.org
> |> Subject: Re: [siprec] Last Call: <draft-ietf-siprec-req-09.txt>(Use
> |> Cases andRequirements for SIP-based MediaRecording (SIPREC))
> |> toInformational RFC
> |>
> |> I am not sure that having wall clock only for CS start is enough,
> |> especially for partial metadata update. I will prefer to have on
> media
> |> level
> |>
> |> Leon
> |>
> |> -----Original Message-----
> |> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> |> Sent: Thursday, April 14, 2011 3:58 PM
> |> To: Leon Portman; Muthu ArulMozhi Perumal (mperumal); ietf@ietf.org
> |> Cc: siprec@ietf.org
> |> Subject: RE: [siprec] Last Call: <draft-ietf-siprec-req-09.txt>
(Use
> |> Cases andRequirements for SIP-based Media Recording (SIPREC))
> |> toInformational RFC
> |>
> |> Understood, but if we have wall clock time for the start of a CS,
> |> wouldn't that be sufficient? The new requirement would cover
> |> synchronization of all media start/stops relative to that time.
> |>
> |> John (as individual)
> |>
> |>
> |> > -----Original Message-----
> |> > From: Leon Portman [mailto:Leon.Portman@nice.com]
> |> > Sent: 14 April 2011 13:19
> |> > To: Elwell, John; Muthu ArulMozhi Perumal (mperumal);
ietf@ietf.org
> |> > Cc: siprec@ietf.org
> |> > Subject: RE: [siprec] Last Call:
> |> > <draft-ietf-siprec-req-09.txt> (Use Cases andRequirements for
> |> > SIP-based Media Recording (SIPREC)) toInformational RFC
> |> >
> |> > Actually REQ-022 and REQ-023 describing not only requirement to
> |> > synchronize between different media streams but more importantly
> |> > ability to relate them to real world (wall) clock. It is not only
> |> > important to playback them correctly but also to know when it was
> |> > said.
> |> > One example is continue trading after closing hour (even for one
> |> > second is not allowed)
> |> >
> |> > And if these media are synchronized to wall clock then they are
> also
> |> > synchronized between them thus I am not sure if we need this
> |> > additional requirement.
> |> >
> |> > Thanks
> |> >
> |> > Leon
> |> >
> |> > -----Original Message-----
> |> > From: siprec-bounces@ietf.org
> |> > [mailto:siprec-bounces@ietf.org] On Behalf Of Elwell, John
> |> > Sent: Thursday, April 14, 2011 1:54 PM
> |> > To: Muthu ArulMozhi Perumal (mperumal); ietf@ietf.org
> |> > Cc: siprec@ietf.org
> |> > Subject: Re: [siprec] Last Call:
> |> > <draft-ietf-siprec-req-09.txt> (Use Cases andRequirements for
> |> > SIP-based Media Recording (SIPREC)) toInformational RFC
> |> >
> |> >
> |> >
> |> >
> |> > > -----Original Message-----
> |> > > From: siprec-bounces@ietf.org
> |> > > [mailto:siprec-bounces@ietf.org] On Behalf Of Muthu
> |> > ArulMozhi Perumal
> |> > > (mperumal)
> |> > > Sent: 14 April 2011 07:34
> |> > > To: ietf@ietf.org
> |> > > Cc: siprec@ietf.org
> |> > > Subject: Re: [siprec] Last Call:
> |> > > <draft-ietf-siprec-req-09.txt> (Use Cases andRequirements for
> |> > > SIP-based Media Recording (SIPREC)) toInformational RFC
> |> > >
> |> > > I've one major comment. It draft discusses synchronization
> |> > between the
> |> > > recorded media streams and synchronized playback, which
> |> > seem important
> |> > > for certain applications:
> |> > >
> |> > > <snip>
> |> > > Some applications require the recording of more than one
> |> > media stream,
> |> > > possibly of different types. Media are synchronized, either
> |> > at storage
> |> > > or at playback.
> |> > > </snip>
> |> > >
> |> > > However, in the requirements section it doesn't seem REQ-022
and
> |> > > REQ-023 are all that are need and sufficient to achieve this
with
> |> > > needed precision. So, I would suggest adding another
requirement
> as
> |> > > follows:
> |> > > The mechanism MUST provide means for facilitating
> |> > synchronization of
> |> > > the recorded media streams and metadata either at storage or at
> |> > > playback.
> |> > > This includes, but not limited to, the information needed as
per
> |> > > REQ-022 and REQ-023.
> |> > [JRE] This seems a reasonable addition. I wonder if the new
> |> > requirement (first sentence only) is sufficient as a
> |> > **replacement** for REQ-022 and REQ-023. On reading REQ-022 and
> |> > REQ-023 again, it is not so clear what their purpose was, and
they
> |> > seem to be more like a solution than a requirement.
> |> > One purpose would certainly be that covered by Muthu's new
> |> > requirement. Was there any other purpose?
> |> >
> |> > John
> |> >
> |> > >
> |> > > A nitpick:
> |> > > Use Case 8
> |> > > In cases where calls inside or between branches must be
recorded,
> a
> |> > > centralized recording system in data centers together with
> |> > telephony
> |> > > infrastructure (e.g. PBX) me deployed.
> |> > >
> |> > > s/me/may be
> |> > >
> |> > > Muthu
> |> > >
> |> > > |-----Original Message-----
> |> > > |From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org]
> On
> |> > > Behalf Of The IESG
> |> > > |Sent: Wednesday, April 06, 2011 6:20 PM
> |> > > |To: IETF-Announce
> |> > > |Cc: siprec@ietf.org
> |> > > |Subject: [siprec] Last Call: <draft-ietf-siprec-req-09.txt>
> |> > > (Use Cases
> |> > > andRequirements for SIP-based
> |> > > |Media Recording (SIPREC)) toInformational RFC
> |> > > |
> |> > > |
> |> > > |The IESG has received a request from the SIP Recording WG
> |> > (siprec) to
> |> > > |consider the following document:
> |> > > |- 'Use Cases and Requirements for SIP-based Media
> |> > Recording (SIPREC)'
> |> > > |  <draft-ietf-siprec-req-09.txt> as an 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 2011-04-20. 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.
> |> > > |
> |> > > |The file can be obtained via
> |> > > |http://datatracker.ietf.org/doc/draft-ietf-siprec-req/
> |> > > |
> |> > > |IESG discussion can be tracked via
> |> > > |http://datatracker.ietf.org/doc/draft-ietf-siprec-req/
> |> > > |
> |> > > |
> |> > > |
> |> > > |No IPR declarations have been submitted directly on this I-D.
> |> > > |_______________________________________________
> |> > > |siprec mailing list
> |> > > |siprec@ietf.org
> |> > > |https://www.ietf.org/mailman/listinfo/siprec
> |> > > _______________________________________________
> |> > > siprec mailing list
> |> > > siprec@ietf.org
> |> > > https://www.ietf.org/mailman/listinfo/siprec
> |> > >
> |> > _______________________________________________
> |> > siprec mailing list
> |> > siprec@ietf.org
> |> > https://www.ietf.org/mailman/listinfo/siprec
> |> >
> |> _______________________________________________
> |> siprec mailing list
> |> siprec@ietf.org
> |> https://www.ietf.org/mailman/listinfo/siprec
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec

From partr@cisco.com  Thu Apr 14 22:25:43 2011
Return-Path: <partr@cisco.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id EB878E06E1; Thu, 14 Apr 2011 22:25:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.816
X-Spam-Level: 
X-Spam-Status: No, score=-9.816 tagged_above=-999 required=5 tests=[AWL=0.183,  BAYES_00=-2.599, J_CHICKENPOX_55=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3jnbagFuGbM9; Thu, 14 Apr 2011 22:25:42 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfc.amsl.com (Postfix) with ESMTP id C53EBE0668; Thu, 14 Apr 2011 22:25:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=partr@cisco.com; l=11456; q=dns/txt; s=iport; t=1302845142; x=1304054742; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=932S70tBg0lQU29j4pFRSSQ2cFcryBX7H511Ioj2CZ0=; b=j79DPE1lchdAUzevp3KhQF9JRAsN2FM4kLNIIIL5liOP28AtI7qjhqon AoSSsxUyfbVCds1HDVpxQhisbSJFU0LTCR7FSq5WrOw4FIk+Qlp+NV8Jt zIHsXMSAmUZGVLMSQ9FhuqBrXcmj8BCkjfNlx3KGKBqhNrQlAfJXiC+Mg I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtgAAEjWp02Q/khMgWdsb2JhbACYA41/FAEBFiYlqBqdBIIhXYJwBIVejBU
X-IronPort-AV: E=Sophos;i="4.64,216,1301875200"; d="scan'208";a="25796408"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-2.cisco.com with ESMTP; 15 Apr 2011 05:25:40 +0000
Received: from xbh-bgl-411.cisco.com (xbh-bgl-411.cisco.com [72.163.129.201]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p3F5OxTN019517; Fri, 15 Apr 2011 05:25:40 GMT
Received: from xmb-bgl-411.cisco.com ([72.163.129.207]) by xbh-bgl-411.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 15 Apr 2011 10:55:31 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [siprec] LastCall:<draft-ietf-siprec-req-09.txt>(UseCases andRequirementsforSIP-basedMediaRecording	(SIPREC)) toInformational RFC
Date: Fri, 15 Apr 2011 10:55:30 +0530
Message-ID: <A11921905DA1564D9BCF64A6430A62390506BE03@XMB-BGL-411.cisco.com>
In-Reply-To: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C0408A56E@xmb-sjc-234.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] LastCall:<draft-ietf-siprec-req-09.txt>(UseCases andRequirementsforSIP-basedMediaRecording	(SIPREC)) toInformational RFC
Thread-Index: Acv0WYBeRuGjGNBtTZSHeqn78QP5xwGEv6YwAAlHtwAAAvtH0AABcMXAAAdJn6AAAIZ7cAAHjozgAAa08QAACpF8MA==
References: <20110406125020.17538.70016.idtracker@localhost><1D062974A4845E4D8A343C65380492020533BB70@XMB-BGL-414.cisco.com><A444A0F8084434499206E78C106220CA0875EB5A4E@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38AB73D00B@TLVMBX01.nice.com><A444A0F8084434499206E78C106220CA0875EB5B28@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38AB73D110@TLVMBX01.nice.com><35BCE99A477D6A4986FB2216D8CF2CFD06009D00@XMB-BGL-417.cisco.com><1D062974A4845E4D8A343C65380492020533BD38@XMB-BGL-414.cisco.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C0408A56E@xmb-sjc-234.amer.cisco.com>
From: "Parthasarathi R (partr)" <partr@cisco.com>
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, "Muthu ArulMozhi Perumal (mperumal)" <mperumal@cisco.com>, "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>, "Leon Portman" <Leon.Portman@nice.com>, "Elwell, John" <john.elwell@siemens-enterprise.com>, <ietf@ietf.org>
X-OriginalArrivalTime: 15 Apr 2011 05:25:31.0024 (UTC) FILETIME=[89908100:01CBFB2D]
X-Mailman-Approved-At: Fri, 15 Apr 2011 07:54:25 -0700
Cc: siprec@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 Apr 2011 05:25:44 -0000

Charles,

synchronize multiple CS from multiple SRCs to single SRS is outside the
scope of SIPREC. I'm not very clear about the requirement of media
synchronization for multiple CS from single SRC  because each CS have
its own media stream, is there any need to synchronize between multiple
CS?

Muthu,

I'm seeing two requirement here:

1) Timestamp synchronization between metadata and media stream.

This is possible to be achieved by current metadata media stream start&
stop time wherein media packet shall be stored or played back with the
reference to start time of media stream block. Say Media stream start
time as T0 and end time as T1, the first media packet is received at T0+
t[i] wherein t[i] is the time interval between T0 and first media
packet. Here T0+t[i] is always less than T1. Playback shall use T0 as
the reference value. Here there is no need of extra time reference
required.

2) Timestamp synchronization between multiple media stream (audio +
video)

New requirement is to synchronize between media stream and there is need
to identify the detailed requirement. Infact, I'm still not very much
clear which may be due to my lack of specific details about audio+Video
recording.

Please correct in case I'm missing something.

Thanks
Partha

-----Original Message-----
From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf
Of Charles Eckel (eckelcu)
Sent: Friday, April 15, 2011 4:59 AM
To: Muthu ArulMozhi Perumal (mperumal); Ram Mohan R (rmohanr); Leon
Portman; Elwell, John; ietf@ietf.org
Cc: siprec@ietf.org
Subject: Re: [siprec] LastCall:<draft-ietf-siprec-req-09.txt>(Use Cases
andRequirements forSIP-basedMediaRecording (SIPREC)) toInformational RFC

I was thinking we needed a way to synchronize media from multiple CSs,
which may be received by the SRS from one or more SRCs. Is this not a
requirement?

Thanks,
Charles

> -----Original Message-----
> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
Behalf Of Muthu ArulMozhi Perumal
> (mperumal)
> Sent: Thursday, April 14, 2011 1:42 PM
> To: Ram Mohan R (rmohanr); Leon Portman; Elwell, John; ietf@ietf.org
> Cc: siprec@ietf.org
> Subject: Re: [siprec] Last Call:<draft-ietf-siprec-req-09.txt>(Use
Cases andRequirements forSIP-based
> MediaRecording (SIPREC)) toInformational RFC
>=20
> I agree with John that these seem more like part of a solution rather=20
> than actual requirements. In addition, sending the wallclock time at=20
> media start/end alone may not suffice for achieving inter-media=20
> synchronization and playback, instead we may need to send the
wallclock
> time periodically, like RTCP. For e.g, if there is a codec
renegotiation
> in CS the RTP timestamp can restart from a random value. If silence=20
> suppression is enabled there would be gaps in the RTP timestamp.
>=20
> These are things that need to be discussed as part of the solution --=20
> the requirement itself should be generic enough, like what I
described.
> REQ-022 and REQ-023 we have doesn't seem to clearly indicate the=20
> purpose.
>=20
> Muthu
>=20
> |-----Original Message-----
> |From: Ram Mohan R (rmohanr)
> |Sent: Thursday, April 14, 2011 10:13 PM
> |To: Leon Portman; Elwell, John; Muthu ArulMozhi Perumal (mperumal);
> ietf@ietf.org
> |Cc: siprec@ietf.org
> |Subject: RE: [siprec] Last Call: <draft-ietf-siprec-req-09.txt>(Use
> Cases andRequirements for SIP-
> |based MediaRecording (SIPREC)) toInformational RFC
> |
> |We already have  attributes Start-Time / End-time in Media Stream
> block. This is for the same purpose
> |to indicate the wall clock time for start/end of media.
> |
> |Ram
> |
> |> -----Original Message-----
> |> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On=20
> |> Behalf Of Leon Portman
> |> Sent: Thursday, April 14, 2011 9:57 PM
> |> To: Elwell, John; Muthu ArulMozhi Perumal (mperumal); ietf@ietf.org
> |> Cc: siprec@ietf.org
> |> Subject: Re: [siprec] Last Call: <draft-ietf-siprec-req-09.txt>(Use
> |> Cases andRequirements for SIP-based MediaRecording (SIPREC))=20
> |> toInformational RFC
> |>
> |> I am not sure that having wall clock only for CS start is enough,=20
> |> especially for partial metadata update. I will prefer to have on
> media
> |> level
> |>
> |> Leon
> |>
> |> -----Original Message-----
> |> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> |> Sent: Thursday, April 14, 2011 3:58 PM
> |> To: Leon Portman; Muthu ArulMozhi Perumal (mperumal); ietf@ietf.org
> |> Cc: siprec@ietf.org
> |> Subject: RE: [siprec] Last Call: <draft-ietf-siprec-req-09.txt>
(Use
> |> Cases andRequirements for SIP-based Media Recording (SIPREC))=20
> |> toInformational RFC
> |>
> |> Understood, but if we have wall clock time for the start of a CS,=20
> |> wouldn't that be sufficient? The new requirement would cover=20
> |> synchronization of all media start/stops relative to that time.
> |>
> |> John (as individual)
> |>
> |>
> |> > -----Original Message-----
> |> > From: Leon Portman [mailto:Leon.Portman@nice.com]
> |> > Sent: 14 April 2011 13:19
> |> > To: Elwell, John; Muthu ArulMozhi Perumal (mperumal);
ietf@ietf.org
> |> > Cc: siprec@ietf.org
> |> > Subject: RE: [siprec] Last Call:
> |> > <draft-ietf-siprec-req-09.txt> (Use Cases andRequirements for=20
> |> > SIP-based Media Recording (SIPREC)) toInformational RFC
> |> >
> |> > Actually REQ-022 and REQ-023 describing not only requirement to=20
> |> > synchronize between different media streams but more importantly=20
> |> > ability to relate them to real world (wall) clock. It is not only

> |> > important to playback them correctly but also to know when it was

> |> > said.
> |> > One example is continue trading after closing hour (even for one=20
> |> > second is not allowed)
> |> >
> |> > And if these media are synchronized to wall clock then they are
> also
> |> > synchronized between them thus I am not sure if we need this=20
> |> > additional requirement.
> |> >
> |> > Thanks
> |> >
> |> > Leon
> |> >
> |> > -----Original Message-----
> |> > From: siprec-bounces@ietf.org
> |> > [mailto:siprec-bounces@ietf.org] On Behalf Of Elwell, John
> |> > Sent: Thursday, April 14, 2011 1:54 PM
> |> > To: Muthu ArulMozhi Perumal (mperumal); ietf@ietf.org
> |> > Cc: siprec@ietf.org
> |> > Subject: Re: [siprec] Last Call:
> |> > <draft-ietf-siprec-req-09.txt> (Use Cases andRequirements for=20
> |> > SIP-based Media Recording (SIPREC)) toInformational RFC
> |> >
> |> >
> |> >
> |> >
> |> > > -----Original Message-----
> |> > > From: siprec-bounces@ietf.org
> |> > > [mailto:siprec-bounces@ietf.org] On Behalf Of Muthu
> |> > ArulMozhi Perumal
> |> > > (mperumal)
> |> > > Sent: 14 April 2011 07:34
> |> > > To: ietf@ietf.org
> |> > > Cc: siprec@ietf.org
> |> > > Subject: Re: [siprec] Last Call:
> |> > > <draft-ietf-siprec-req-09.txt> (Use Cases andRequirements for=20
> |> > > SIP-based Media Recording (SIPREC)) toInformational RFC
> |> > >
> |> > > I've one major comment. It draft discusses synchronization
> |> > between the
> |> > > recorded media streams and synchronized playback, which
> |> > seem important
> |> > > for certain applications:
> |> > >
> |> > > <snip>
> |> > > Some applications require the recording of more than one
> |> > media stream,
> |> > > possibly of different types. Media are synchronized, either
> |> > at storage
> |> > > or at playback.
> |> > > </snip>
> |> > >
> |> > > However, in the requirements section it doesn't seem REQ-022
and
> |> > > REQ-023 are all that are need and sufficient to achieve this
with
> |> > > needed precision. So, I would suggest adding another
requirement
> as
> |> > > follows:
> |> > > The mechanism MUST provide means for facilitating
> |> > synchronization of
> |> > > the recorded media streams and metadata either at storage or at

> |> > > playback.
> |> > > This includes, but not limited to, the information needed as
per
> |> > > REQ-022 and REQ-023.
> |> > [JRE] This seems a reasonable addition. I wonder if the new=20
> |> > requirement (first sentence only) is sufficient as a
> |> > **replacement** for REQ-022 and REQ-023. On reading REQ-022 and
> |> > REQ-023 again, it is not so clear what their purpose was, and
they
> |> > seem to be more like a solution than a requirement.
> |> > One purpose would certainly be that covered by Muthu's new=20
> |> > requirement. Was there any other purpose?
> |> >
> |> > John
> |> >
> |> > >
> |> > > A nitpick:
> |> > > Use Case 8
> |> > > In cases where calls inside or between branches must be
recorded,
> a
> |> > > centralized recording system in data centers together with
> |> > telephony
> |> > > infrastructure (e.g. PBX) me deployed.
> |> > >
> |> > > s/me/may be
> |> > >
> |> > > Muthu
> |> > >
> |> > > |-----Original Message-----
> |> > > |From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org]
> On
> |> > > Behalf Of The IESG
> |> > > |Sent: Wednesday, April 06, 2011 6:20 PM
> |> > > |To: IETF-Announce
> |> > > |Cc: siprec@ietf.org
> |> > > |Subject: [siprec] Last Call: <draft-ietf-siprec-req-09.txt>
> |> > > (Use Cases
> |> > > andRequirements for SIP-based
> |> > > |Media Recording (SIPREC)) toInformational RFC
> |> > > |
> |> > > |
> |> > > |The IESG has received a request from the SIP Recording WG
> |> > (siprec) to
> |> > > |consider the following document:
> |> > > |- 'Use Cases and Requirements for SIP-based Media
> |> > Recording (SIPREC)'
> |> > > |  <draft-ietf-siprec-req-09.txt> as an 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 2011-04-20. 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.
> |> > > |
> |> > > |The file can be obtained via
> |> > > |http://datatracker.ietf.org/doc/draft-ietf-siprec-req/
> |> > > |
> |> > > |IESG discussion can be tracked via=20
> |> > > |http://datatracker.ietf.org/doc/draft-ietf-siprec-req/
> |> > > |
> |> > > |
> |> > > |
> |> > > |No IPR declarations have been submitted directly on this I-D.
> |> > > |_______________________________________________
> |> > > |siprec mailing list
> |> > > |siprec@ietf.org
> |> > > |https://www.ietf.org/mailman/listinfo/siprec
> |> > > _______________________________________________
> |> > > siprec mailing list
> |> > > siprec@ietf.org
> |> > > https://www.ietf.org/mailman/listinfo/siprec
> |> > >
> |> > _______________________________________________
> |> > siprec mailing list
> |> > siprec@ietf.org
> |> > https://www.ietf.org/mailman/listinfo/siprec
> |> >
> |> _______________________________________________
> |> siprec mailing list
> |> siprec@ietf.org
> |> https://www.ietf.org/mailman/listinfo/siprec
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec
_______________________________________________
siprec mailing list
siprec@ietf.org
https://www.ietf.org/mailman/listinfo/siprec

From henk@uijterwaal.nl  Fri Apr 15 01:03:28 2011
Return-Path: <henk@uijterwaal.nl>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id B5B6FE0693 for <ietf@ietfc.amsl.com>; Fri, 15 Apr 2011 01:03:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.504
X-Spam-Level: 
X-Spam-Status: No, score=-0.504 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BXd+k0SH9+1C for <ietf@ietfc.amsl.com>; Fri, 15 Apr 2011 01:03:28 -0700 (PDT)
Received: from smtp-vbr7.xs4all.nl (smtp-vbr7.xs4all.nl [194.109.24.27]) by ietfc.amsl.com (Postfix) with ESMTP id 2B8E0E0686 for <ietf@ietf.org>; Fri, 15 Apr 2011 01:03:23 -0700 (PDT)
Received: from geir.local (thuis.uijterwaal.nl [82.95.178.49]) (authenticated bits=0) by smtp-vbr7.xs4all.nl (8.13.8/8.13.8) with ESMTP id p3F83Mmn023904 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 15 Apr 2011 10:03:23 +0200 (CEST) (envelope-from henk@uijterwaal.nl)
Message-ID: <4DA7FBCA.2090508@uijterwaal.nl>
Date: Fri, 15 Apr 2011 10:03:22 +0200
From: Henk Uijterwaal <henk@uijterwaal.nl>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB; rv:1.9.2.15) Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IAOC: delegating ex-officio responsibility
References: <2BE582FA-2682-4232-9D83-23A03F01A0DB@NLnetLabs.nl>	<6.2.5.6.2.20110330073936.0e1899d0@resistor.net>	<E2E41FDE-3818-4513-9933-CB1E0326B43E@nlnetlabs.nl>	<6.2.5.6.2.20110330113947.0c948bc0@resistor.net>	<4D942843.4060804@gmail.com>	<6.2.5.6.2.20110331120351.09488990@resistor.net>	<4D955661.8050502@gmail.com>	<9C81C0F6-3ABE-4479-8C5E-C20C486D052A@gmail.com>	<82A347CC-BB19-4A73-8E8A-924FBAA92A5F@NLnetLabs.nl>	<84D6568B-18C9-47B2-A457-C51C2FB3351F@gmail.com>	<5419FA805EF52E79D7822966@PST.JCK.COM> <4DA71408.3090704@gmail.com>	<7220CC90-02B0-45B0-9113-236A933BBD16@vigilsec.com> <8F2607B3-F58E-4786-A60D-4A2758E2C35E@gmail.com>
In-Reply-To: <8F2607B3-F58E-4786-A60D-4A2758E2C35E@gmail.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by XS4ALL Virus Scanner
X-Mailman-Approved-At: Fri, 15 Apr 2011 07:54: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: Fri, 15 Apr 2011 08:03:28 -0000

On 14/04/2011 23:26, Bob Hinden wrote:

> This prompts me to ask a question.  Who would the IETF Chair delegate this
> responsibility to?  The draft doesn't specify.

I would say one of the (nomcom appointed) members of the IESG (or IAB).

> An Area Director is the obvious answer, except from what I understand ADs are
> also extremely busy.  This trades one problem for another.  

The IESG chair definitely has more tasks than any of the AD's and I think it
would be helpful if there were options to distribute work over the IESG,
rather than assume that the chair can do them all.   This is not only a matter
of time, but also of expertise and personal interests.   (The same applies
to the IAB chair).

Henk

-- 
------------------------------------------------------------------------------
Henk Uijterwaal                           Email: henk(at)uijterwaal.nl
RIPE NCC                                  http://www.xs4all.nl/~henku
                                          Phone: +31.6.55861746
------------------------------------------------------------------------------

There appears to have been a collective retreat from reality that day.
                                 (John Glanfield, on an engineering project)

From eckelcu@cisco.com  Fri Apr 15 07:55:32 2011
Return-Path: <eckelcu@cisco.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id AD095E0890; Fri, 15 Apr 2011 07:55:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.105
X-Spam-Level: 
X-Spam-Status: No, score=-10.105 tagged_above=-999 required=5 tests=[AWL=-0.106, BAYES_00=-2.599, J_CHICKENPOX_55=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bobbUuUSNmIo; Fri, 15 Apr 2011 07:55:28 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by ietfc.amsl.com (Postfix) with ESMTP id C689EE06BA; Fri, 15 Apr 2011 07:55:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eckelcu@cisco.com; l=13025; q=dns/txt; s=iport; t=1302879327; x=1304088927; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=Pm8WADuWCEr124yapDRxj+/B6Hps9EVBAueLKwwV3cU=; b=VNyVwmY+/0tCv8mckjlHD06ByXCbQqgzc+0djF5GZOIeHrBX6/k9r4qz 8loLpvux4D1lg1I72yNSzFANsey7Z6buUeH3ZWqEDRQ4/wc1/sjPwGjlQ f5nk0AaDiVLZUH29txtFYSAQpVQ+l/MsXe0s4h9FLWa+6lBX8TncuUsp1 E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmwBABxcqE2rRDoJ/2dsb2JhbACYBI1/d6conHqCIV2CcASFYIwT
X-IronPort-AV: E=Sophos;i="4.64,219,1301875200"; d="scan'208";a="338371160"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by sj-iport-2.cisco.com with ESMTP; 15 Apr 2011 14:55:27 +0000
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p3FEtRFX002425; Fri, 15 Apr 2011 14:55:27 GMT
Received: from xmb-sjc-234.amer.cisco.com ([128.107.191.111]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 15 Apr 2011 07:55:26 -0700
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [siprec] LastCall:<draft-ietf-siprec-req-09.txt>(UseCases andRequirementsforSIP-basedMediaRecording	(SIPREC)) toInformational RFC
Date: Fri, 15 Apr 2011 07:55:26 -0700
Message-ID: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C0408A674@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <A11921905DA1564D9BCF64A6430A62390506BE03@XMB-BGL-411.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] LastCall:<draft-ietf-siprec-req-09.txt>(UseCases andRequirementsforSIP-basedMediaRecording	(SIPREC)) toInformational RFC
Thread-Index: Acv0WYBeRuGjGNBtTZSHeqn78QP5xwGEv6YwAAlHtwAAAvtH0AABcMXAAAdJn6AAAIZ7cAAHjozgAAa08QAACpF8MAAVoayQ
References: <20110406125020.17538.70016.idtracker@localhost><1D062974A4845E4D8A343C65380492020533BB70@XMB-BGL-414.cisco.com><A444A0F8084434499206E78C106220CA0875EB5A4E@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38AB73D00B@TLVMBX01.nice.com><A444A0F8084434499206E78C106220CA0875EB5B28@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38AB73D110@TLVMBX01.nice.com><35BCE99A477D6A4986FB2216D8CF2CFD06009D00@XMB-BGL-417.cisco.com><1D062974A4845E4D8A343C65380492020533BD38@XMB-BGL-414.cisco.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C0408A56E@xmb-sjc-234.amer.cisco.com> <A11921905DA1564D9BCF64A6430A62390506BE03@XMB-BGL-411.cisco.com>
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Parthasarathi R (partr)" <partr@cisco.com>, "Muthu ArulMozhi Perumal (mperumal)" <mperumal@cisco.com>, "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>, "Leon Portman" <Leon.Portman@nice.com>, "Elwell, John" <john.elwell@siemens-enterprise.com>, <ietf@ietf.org>
X-OriginalArrivalTime: 15 Apr 2011 14:55:26.0990 (UTC) FILETIME=[27F2D2E0:01CBFB7D]
X-Mailman-Approved-At: Fri, 15 Apr 2011 08:01:38 -0700
Cc: siprec@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 Apr 2011 14:55:32 -0000

I suppose the most common case of multiple CS from a single SRC is a
conference focus acting as SRC. In this case, the SRC could help
synchronization of the individual CSs as part of sending to RS. Perhaps
it is not required to do so, but it should if it can.
For the case of multiple SRCs which you say is out of scope, I do not
see anything in the requirements that says otherwise, but it was always
my assumption that you could have multiple SRCs. For example, a point to
point call and each sends its stream to RS. I will reread the
requirements more closely.

Cheers,
Charles

> -----Original Message-----
> From: Parthasarathi R (partr)
> Sent: Thursday, April 14, 2011 10:26 PM
> To: Charles Eckel (eckelcu); Muthu ArulMozhi Perumal (mperumal); Ram
Mohan R (rmohanr); Leon Portman;
> Elwell, John; ietf@ietf.org
> Cc: siprec@ietf.org
> Subject: RE: [siprec] LastCall:<draft-ietf-siprec-req-09.txt>(UseCases
andRequirementsforSIP-
> basedMediaRecording (SIPREC)) toInformational RFC
>=20
> Charles,
>=20
> synchronize multiple CS from multiple SRCs to single SRS is outside
the scope of SIPREC. I'm not very
> clear about the requirement of media synchronization for multiple CS
from single SRC  because each CS
> have its own media stream, is there any need to synchronize between
multiple CS?
>=20
> Muthu,
>=20
> I'm seeing two requirement here:
>=20
> 1) Timestamp synchronization between metadata and media stream.
>=20
> This is possible to be achieved by current metadata media stream
start& stop time wherein media packet
> shall be stored or played back with the reference to start time of
media stream block. Say Media
> stream start time as T0 and end time as T1, the first media packet is
received at T0+ t[i] wherein
> t[i] is the time interval between T0 and first media packet. Here
T0+t[i] is always less than T1.
> Playback shall use T0 as the reference value. Here there is no need of
extra time reference required.
>=20
> 2) Timestamp synchronization between multiple media stream (audio +
video)
>=20
> New requirement is to synchronize between media stream and there is
need to identify the detailed
> requirement. Infact, I'm still not very much clear which may be due to
my lack of specific details
> about audio+Video recording.
>=20
> Please correct in case I'm missing something.
>=20
> Thanks
> Partha
>=20
> -----Original Message-----
> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
Behalf Of Charles Eckel (eckelcu)
> Sent: Friday, April 15, 2011 4:59 AM
> To: Muthu ArulMozhi Perumal (mperumal); Ram Mohan R (rmohanr); Leon
Portman; Elwell, John;
> ietf@ietf.org
> Cc: siprec@ietf.org
> Subject: Re: [siprec] LastCall:<draft-ietf-siprec-req-09.txt>(Use
Cases andRequirements forSIP-
> basedMediaRecording (SIPREC)) toInformational RFC
>=20
> I was thinking we needed a way to synchronize media from multiple CSs,
which may be received by the
> SRS from one or more SRCs. Is this not a requirement?
>=20
> Thanks,
> Charles
>=20
> > -----Original Message-----
> > From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> Behalf Of Muthu ArulMozhi Perumal
> > (mperumal)
> > Sent: Thursday, April 14, 2011 1:42 PM
> > To: Ram Mohan R (rmohanr); Leon Portman; Elwell, John; ietf@ietf.org
> > Cc: siprec@ietf.org
> > Subject: Re: [siprec] Last Call:<draft-ietf-siprec-req-09.txt>(Use
> Cases andRequirements forSIP-based
> > MediaRecording (SIPREC)) toInformational RFC
> >
> > I agree with John that these seem more like part of a solution
rather
> > than actual requirements. In addition, sending the wallclock time at
> > media start/end alone may not suffice for achieving inter-media
> > synchronization and playback, instead we may need to send the
> wallclock
> > time periodically, like RTCP. For e.g, if there is a codec
> renegotiation
> > in CS the RTP timestamp can restart from a random value. If silence
> > suppression is enabled there would be gaps in the RTP timestamp.
> >
> > These are things that need to be discussed as part of the solution
--
> > the requirement itself should be generic enough, like what I
> described.
> > REQ-022 and REQ-023 we have doesn't seem to clearly indicate the
> > purpose.
> >
> > Muthu
> >
> > |-----Original Message-----
> > |From: Ram Mohan R (rmohanr)
> > |Sent: Thursday, April 14, 2011 10:13 PM
> > |To: Leon Portman; Elwell, John; Muthu ArulMozhi Perumal (mperumal);
> > ietf@ietf.org
> > |Cc: siprec@ietf.org
> > |Subject: RE: [siprec] Last Call: <draft-ietf-siprec-req-09.txt>(Use
> > Cases andRequirements for SIP-
> > |based MediaRecording (SIPREC)) toInformational RFC
> > |
> > |We already have  attributes Start-Time / End-time in Media Stream
> > block. This is for the same purpose
> > |to indicate the wall clock time for start/end of media.
> > |
> > |Ram
> > |
> > |> -----Original Message-----
> > |> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> > |> Behalf Of Leon Portman
> > |> Sent: Thursday, April 14, 2011 9:57 PM
> > |> To: Elwell, John; Muthu ArulMozhi Perumal (mperumal);
ietf@ietf.org
> > |> Cc: siprec@ietf.org
> > |> Subject: Re: [siprec] Last Call:
<draft-ietf-siprec-req-09.txt>(Use
> > |> Cases andRequirements for SIP-based MediaRecording (SIPREC))
> > |> toInformational RFC
> > |>
> > |> I am not sure that having wall clock only for CS start is enough,
> > |> especially for partial metadata update. I will prefer to have on
> > media
> > |> level
> > |>
> > |> Leon
> > |>
> > |> -----Original Message-----
> > |> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> > |> Sent: Thursday, April 14, 2011 3:58 PM
> > |> To: Leon Portman; Muthu ArulMozhi Perumal (mperumal);
ietf@ietf.org
> > |> Cc: siprec@ietf.org
> > |> Subject: RE: [siprec] Last Call: <draft-ietf-siprec-req-09.txt>
> (Use
> > |> Cases andRequirements for SIP-based Media Recording (SIPREC))
> > |> toInformational RFC
> > |>
> > |> Understood, but if we have wall clock time for the start of a CS,
> > |> wouldn't that be sufficient? The new requirement would cover
> > |> synchronization of all media start/stops relative to that time.
> > |>
> > |> John (as individual)
> > |>
> > |>
> > |> > -----Original Message-----
> > |> > From: Leon Portman [mailto:Leon.Portman@nice.com]
> > |> > Sent: 14 April 2011 13:19
> > |> > To: Elwell, John; Muthu ArulMozhi Perumal (mperumal);
> ietf@ietf.org
> > |> > Cc: siprec@ietf.org
> > |> > Subject: RE: [siprec] Last Call:
> > |> > <draft-ietf-siprec-req-09.txt> (Use Cases andRequirements for
> > |> > SIP-based Media Recording (SIPREC)) toInformational RFC
> > |> >
> > |> > Actually REQ-022 and REQ-023 describing not only requirement to
> > |> > synchronize between different media streams but more
importantly
> > |> > ability to relate them to real world (wall) clock. It is not
only
> > |> > important to playback them correctly but also to know when it
was
> > |> > said.
> > |> > One example is continue trading after closing hour (even for
one
> > |> > second is not allowed)
> > |> >
> > |> > And if these media are synchronized to wall clock then they are
> > also
> > |> > synchronized between them thus I am not sure if we need this
> > |> > additional requirement.
> > |> >
> > |> > Thanks
> > |> >
> > |> > Leon
> > |> >
> > |> > -----Original Message-----
> > |> > From: siprec-bounces@ietf.org
> > |> > [mailto:siprec-bounces@ietf.org] On Behalf Of Elwell, John
> > |> > Sent: Thursday, April 14, 2011 1:54 PM
> > |> > To: Muthu ArulMozhi Perumal (mperumal); ietf@ietf.org
> > |> > Cc: siprec@ietf.org
> > |> > Subject: Re: [siprec] Last Call:
> > |> > <draft-ietf-siprec-req-09.txt> (Use Cases andRequirements for
> > |> > SIP-based Media Recording (SIPREC)) toInformational RFC
> > |> >
> > |> >
> > |> >
> > |> >
> > |> > > -----Original Message-----
> > |> > > From: siprec-bounces@ietf.org
> > |> > > [mailto:siprec-bounces@ietf.org] On Behalf Of Muthu
> > |> > ArulMozhi Perumal
> > |> > > (mperumal)
> > |> > > Sent: 14 April 2011 07:34
> > |> > > To: ietf@ietf.org
> > |> > > Cc: siprec@ietf.org
> > |> > > Subject: Re: [siprec] Last Call:
> > |> > > <draft-ietf-siprec-req-09.txt> (Use Cases andRequirements for
> > |> > > SIP-based Media Recording (SIPREC)) toInformational RFC
> > |> > >
> > |> > > I've one major comment. It draft discusses synchronization
> > |> > between the
> > |> > > recorded media streams and synchronized playback, which
> > |> > seem important
> > |> > > for certain applications:
> > |> > >
> > |> > > <snip>
> > |> > > Some applications require the recording of more than one
> > |> > media stream,
> > |> > > possibly of different types. Media are synchronized, either
> > |> > at storage
> > |> > > or at playback.
> > |> > > </snip>
> > |> > >
> > |> > > However, in the requirements section it doesn't seem REQ-022
> and
> > |> > > REQ-023 are all that are need and sufficient to achieve this
> with
> > |> > > needed precision. So, I would suggest adding another
> requirement
> > as
> > |> > > follows:
> > |> > > The mechanism MUST provide means for facilitating
> > |> > synchronization of
> > |> > > the recorded media streams and metadata either at storage or
at
> > |> > > playback.
> > |> > > This includes, but not limited to, the information needed as
> per
> > |> > > REQ-022 and REQ-023.
> > |> > [JRE] This seems a reasonable addition. I wonder if the new
> > |> > requirement (first sentence only) is sufficient as a
> > |> > **replacement** for REQ-022 and REQ-023. On reading REQ-022 and
> > |> > REQ-023 again, it is not so clear what their purpose was, and
> they
> > |> > seem to be more like a solution than a requirement.
> > |> > One purpose would certainly be that covered by Muthu's new
> > |> > requirement. Was there any other purpose?
> > |> >
> > |> > John
> > |> >
> > |> > >
> > |> > > A nitpick:
> > |> > > Use Case 8
> > |> > > In cases where calls inside or between branches must be
> recorded,
> > a
> > |> > > centralized recording system in data centers together with
> > |> > telephony
> > |> > > infrastructure (e.g. PBX) me deployed.
> > |> > >
> > |> > > s/me/may be
> > |> > >
> > |> > > Muthu
> > |> > >
> > |> > > |-----Original Message-----
> > |> > > |From: siprec-bounces@ietf.org
[mailto:siprec-bounces@ietf.org]
> > On
> > |> > > Behalf Of The IESG
> > |> > > |Sent: Wednesday, April 06, 2011 6:20 PM
> > |> > > |To: IETF-Announce
> > |> > > |Cc: siprec@ietf.org
> > |> > > |Subject: [siprec] Last Call: <draft-ietf-siprec-req-09.txt>
> > |> > > (Use Cases
> > |> > > andRequirements for SIP-based
> > |> > > |Media Recording (SIPREC)) toInformational RFC
> > |> > > |
> > |> > > |
> > |> > > |The IESG has received a request from the SIP Recording WG
> > |> > (siprec) to
> > |> > > |consider the following document:
> > |> > > |- 'Use Cases and Requirements for SIP-based Media
> > |> > Recording (SIPREC)'
> > |> > > |  <draft-ietf-siprec-req-09.txt> as an 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 2011-04-20. 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.
> > |> > > |
> > |> > > |The file can be obtained via
> > |> > > |http://datatracker.ietf.org/doc/draft-ietf-siprec-req/
> > |> > > |
> > |> > > |IESG discussion can be tracked via
> > |> > > |http://datatracker.ietf.org/doc/draft-ietf-siprec-req/
> > |> > > |
> > |> > > |
> > |> > > |
> > |> > > |No IPR declarations have been submitted directly on this
I-D.
> > |> > > |_______________________________________________
> > |> > > |siprec mailing list
> > |> > > |siprec@ietf.org
> > |> > > |https://www.ietf.org/mailman/listinfo/siprec
> > |> > > _______________________________________________
> > |> > > siprec mailing list
> > |> > > siprec@ietf.org
> > |> > > https://www.ietf.org/mailman/listinfo/siprec
> > |> > >
> > |> > _______________________________________________
> > |> > siprec mailing list
> > |> > siprec@ietf.org
> > |> > https://www.ietf.org/mailman/listinfo/siprec
> > |> >
> > |> _______________________________________________
> > |> siprec mailing list
> > |> siprec@ietf.org
> > |> https://www.ietf.org/mailman/listinfo/siprec
> > _______________________________________________
> > siprec mailing list
> > siprec@ietf.org
> > https://www.ietf.org/mailman/listinfo/siprec
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec

From dhc2@dcrocker.net  Fri Apr 15 08:46:56 2011
Return-Path: <dhc2@dcrocker.net>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id B2D51E069F for <ietf@ietfc.amsl.com>; Fri, 15 Apr 2011 08:46:56 -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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zBxQ+EC0NUM2 for <ietf@ietfc.amsl.com>; Fri, 15 Apr 2011 08:46:52 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfc.amsl.com (Postfix) with ESMTP id 59111E088E for <ietf@ietf.org>; Fri, 15 Apr 2011 08:46:52 -0700 (PDT)
Received: from [192.168.1.5] (adsl-67-127-56-68.dsl.pltn13.pacbell.net [67.127.56.68]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p3FFki9T014339 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Fri, 15 Apr 2011 08:46:49 -0700
Message-ID: <4DA8685F.5050504@dcrocker.net>
Date: Fri, 15 Apr 2011 08:46:39 -0700
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Bob Hinden <bob.hinden@gmail.com>
Subject: Re: IAOC: delegating ex-officio responsibility
References: <2BE582FA-2682-4232-9D83-23A03F01A0DB@NLnetLabs.nl>	<6.2.5.6.2.20110330073936.0e1899d0@resistor.net>	<E2E41FDE-3818-4513-9933-CB1E0326B43E@nlnetlabs.nl>	<6.2.5.6.2.20110330113947.0c948bc0@resistor.net>	<4D942843.4060804@gmail.com>	<6.2.5.6.2.20110331120351.09488990@resistor.net>	<4D955661.8050502@gmail.com>	<9C81C0F6-3ABE-4479-8C5E-C20C486D052A@gmail.com>	<82A347CC-BB19-4A73-8E8A-924FBAA92A5F@NLnetLabs.nl>	<84D6568B-18C9-47B2-A457-C51C2FB3351F@gmail.com>	<5419FA805EF52E79D7822966@PST.JCK.COM> <DAC0FFD9-9B3B-4726-B56B-5E9BE5A5F1D1@gmail.com>
In-Reply-To: <DAC0FFD9-9B3B-4726-B56B-5E9BE5A5F1D1@gmail.com>
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]); Fri, 15 Apr 2011 08:46:49 -0700 (PDT)
Cc: IETF Discussion <ietf@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: Fri, 15 Apr 2011 15:46:56 -0000

On 4/14/2011 9:51 AM, Bob Hinden wrote:
> My concern is that this proposed change would likely make the IAOC work
> worse.   That is, I think it would have a negative impact on the operations of
 > the IETF and that is why I am concerned.


Bob,

That is a concrete and basic assertion.  Please put some flesh on its bones so 
that the basis for your view can be understood better.

The implication is that the people sitting in the positions of IAB Chair and 
IETF Chair are essential to the good operation of the IAOC/Trust.  Someone else 
from their groups or even someone else that they appoint from outside cannot 
perform the task of IAOC/Trust member adequately.

Why?

What are the specific contributions (insights and skills) that these roles 
regularly perform, in the conduct of the IAOC/Trust that cannot be performed 
adequately by others?

d/

ps. Reminder: I've just joined the IAOC/Trust, which means I've attended a few 
meetings and seen some operation.  As always, my comments have nothing to do 
with the individuals; this is about organizational design.

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From dhc2@dcrocker.net  Fri Apr 15 08:53:15 2011
Return-Path: <dhc2@dcrocker.net>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 4725713000B for <ietf@ietfc.amsl.com>; Fri, 15 Apr 2011 08:53:15 -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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iKBAzQXXSZ4O for <ietf@ietfc.amsl.com>; Fri, 15 Apr 2011 08:53:11 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfc.amsl.com (Postfix) with ESMTP id C2443130010 for <ietf@ietf.org>; Fri, 15 Apr 2011 08:53:09 -0700 (PDT)
Received: from [192.168.1.5] (adsl-67-127-56-68.dsl.pltn13.pacbell.net [67.127.56.68]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p3FFr3lS014582 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Fri, 15 Apr 2011 08:53:08 -0700
Message-ID: <4DA869DA.9010308@dcrocker.net>
Date: Fri, 15 Apr 2011 08:52:58 -0700
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
Subject: Re: IAOC: delegating ex-officio responsibility
References: <2BE582FA-2682-4232-9D83-23A03F01A0DB@NLnetLabs.nl>	<6.2.5.6.2.20110330073936.0e1899d0@resistor.net>	<E2E41FDE-3818-4513-9933-CB1E0326B43E@nlnetlabs.nl>	<6.2.5.6.2.20110330113947.0c948bc0@resistor.net>	<4D942843.4060804@gmail.com>	<6.2.5.6.2.20110331120351.09488990@resistor.net>	<4D955661.8050502@gmail.com>	<9C81C0F6-3ABE-4479-8C5E-C20C486D052A@gmail.com>	<82A347CC-BB19-4A73-8E8A-924FBAA92A5F@NLnetLabs.nl>	<84D6568B-18C9-47B2-A457-C51C2FB3351F@gmail.com>	<5419FA805EF52E79D7822966@PST.JCK.COM> <4DA71408.3090704@gmail.com> <7220CC90-02B0-45B0-9113-236A933BBD16@vigilsec.com>
In-Reply-To: <7220CC90-02B0-45B0-9113-236A933BBD16@vigilsec.com>
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]); Fri, 15 Apr 2011 08:53:09 -0700 (PDT)
Cc: IETF <ietf@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: Fri, 15 Apr 2011 15:53:15 -0000

Russ,


On 4/14/2011 2:13 PM, Russ Housley wrote:
> The proposed update to BCP 101 permits further delegation of the IAOC voting position.  While I do not see myself taking advantage of this new feature, I do think we should give future IETF Chairs this option.  It is a cohesive part of the work that can be delegated.  Some coordination between the IETF Chair and the delegate would be necessary, but the time commitment would be significantly less than participating in the IAOC and a subset of its committees.


As SM noted, there is an important difference between delegation and 
appointment.  There also is a difference between having the choice made by the 
head of the group, versus the entire group.

Having the new person be delegated by the Chair makes that person an agent of 
the chair and serve at their whim.  It's been noted that this is probably the 
least stable arrangement for continuity of participation.  It's difficult to 
imagine a person working on this basis and having a healthy ability to 
participate and vote in the IAOC/Trust.

Having the new person be appointed for a period of time and chosen by the group 
(IAB or IESG) provides a stronger basis for their working independently and with 
continuity.

Can you clarify the reasons for the choices you made in the proposal?

d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From housley@vigilsec.com  Fri Apr 15 10:38:20 2011
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 07666E06C2 for <ietf@ietfc.amsl.com>; Fri, 15 Apr 2011 10:38: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=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B2md36islHIp for <ietf@ietfc.amsl.com>; Fri, 15 Apr 2011 10:38:19 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfc.amsl.com (Postfix) with ESMTP id 77769E0678 for <ietf@ietf.org>; Fri, 15 Apr 2011 10:38:19 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 9BC0EF240AF; Fri, 15 Apr 2011 13:38:30 -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 k69pEMJYRSjU; Fri, 15 Apr 2011 13:38:14 -0400 (EDT)
Received: from [192.168.147.173] (unknown [74.202.225.34]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 18E88F24056; Fri, 15 Apr 2011 13:38:30 -0400 (EDT)
Subject: Re: IAOC: delegating ex-officio responsibility
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <4DA824FD.5020205@piuha.net>
Date: Fri, 15 Apr 2011 13:37:47 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <75CFBEF3-7850-4B09-90F1-D1FFE62808B8@vigilsec.com>
References: <2BE582FA-2682-4232-9D83-23A03F01A0DB@NLnetLabs.nl>	<6.2.5.6.2.20110330073936.0e1899d0@resistor.net>	<E2E41FDE-3818-4513-9933-CB1E0326B43E@nlnetlabs.nl>	<6.2.5.6.2.20110330113947.0c948bc0@resistor.net>	<4D942843.4060804@gmail.com>	<6.2.5.6.2.20110331120351.09488990@resistor.net>	<4D955661.8050502@gmail.com>	<9C81C0F6-3ABE-4479-8C5E-C20C486D052A@gmail.com>	<82A347CC-BB19-4A73-8E8A-924FBAA92A5F@NLnetLabs.nl>	<84D6568B-18C9-47B2-A457-C51C2FB3351F@gmail.com>	<5419FA805EF52E79D7822966@PST.JCK.COM> <4DA71408.3090704@gmail.com>	<7220CC90-02B0-45B0-9113-236A933BBD16@vigilsec.com>	<8F2607B3-F58E-4786-A60D-4A2758E2C35E@gmail.com> <FC7B14F4-47B7-4FF2-A72F-D9B8F2B4AA08@vigilsec.com> <4DA824FD.5020205@piuha.net>
To: Jari Arkko <jari.arkko@piuha.net>
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: Fri, 15 Apr 2011 17:38:20 -0000

Jari:

> Russ, Olaf, how much do you normally participate the IAOC work? Are =
you in the subcommittees, do you work on details of agreements with our =
service providers?

As I said in my previous note, I participate in some committees, but not =
all of them.  I am very active in the tools-related committees and the =
proposal evaluations.  It is a judgement call since every committee has =
some impact on the IETF and its participants.

Russ=

From housley@vigilsec.com  Fri Apr 15 11:10:43 2011
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 57B9DE08F8 for <ietf@ietfc.amsl.com>; Fri, 15 Apr 2011 11:10: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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dBjj4jaxooGs for <ietf@ietfc.amsl.com>; Fri, 15 Apr 2011 11:10:42 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfc.amsl.com (Postfix) with ESMTP id B8078E0887 for <ietf@ietf.org>; Fri, 15 Apr 2011 11:10:42 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 85235F24068; Fri, 15 Apr 2011 14:10:42 -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 4kQ6221IyPbp; Fri, 15 Apr 2011 14:10:33 -0400 (EDT)
Received: from [192.168.147.173] (unknown [74.202.225.34]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 0A214F2403F; Fri, 15 Apr 2011 14:10:42 -0400 (EDT)
Subject: Re: IAOC: delegating ex-officio responsibility
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <4DA869DA.9010308@dcrocker.net>
Date: Fri, 15 Apr 2011 14:10:10 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <7FD79CFD-70A9-4664-8AFD-C6BE0EA0BA64@vigilsec.com>
References: <2BE582FA-2682-4232-9D83-23A03F01A0DB@NLnetLabs.nl>	<6.2.5.6.2.20110330073936.0e1899d0@resistor.net>	<E2E41FDE-3818-4513-9933-CB1E0326B43E@nlnetlabs.nl>	<6.2.5.6.2.20110330113947.0c948bc0@resistor.net>	<4D942843.4060804@gmail.com>	<6.2.5.6.2.20110331120351.09488990@resistor.net>	<4D955661.8050502@gmail.com>	<9C81C0F6-3ABE-4479-8C5E-C20C486D052A@gmail.com>	<82A347CC-BB19-4A73-8E8A-924FBAA92A5F@NLnetLabs.nl>	<84D6568B-18C9-47B2-A457-C51C2FB3351F@gmail.com>	<5419FA805EF52E79D7822966@PST.JCK.COM> <4DA71408.3090704@gmail.com> <7220CC90-02B0-45B0-9113-236A933BBD16@vigilsec.com> <4DA869DA.9010308@dcrocker.net>
To: dcrocker@bbiw.net
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: Fri, 15 Apr 2011 18:10:43 -0000

Dave:

>> The proposed update to BCP 101 permits further delegation of the IAOC =
voting position.  While I do not see myself taking advantage of this new =
feature, I do think we should give future IETF Chairs this option.  It =
is a cohesive part of the work that can be delegated.  Some coordination =
between the IETF Chair and the delegate would be necessary, but the time =
commitment would be significantly less than participating in the IAOC =
and a subset of its committees.
>=20
> As SM noted, there is an important difference between delegation and =
appointment.  There also is a difference between having the choice made =
by the head of the group, versus the entire group.
>=20
> Having the new person be delegated by the Chair makes that person an =
agent of the chair and serve at their whim.  It's been noted that this =
is probably the least stable arrangement for continuity of =
participation.  It's difficult to imagine a person working on this basis =
and having a healthy ability to participate and vote in the IAOC/Trust.
>=20
> Having the new person be appointed for a period of time and chosen by =
the group (IAB or IESG) provides a stronger basis for their working =
independently and with continuity.
>=20
> Can you clarify the reasons for the choices you made in the proposal?

It never occurred to me that the delegation would be made without the =
consent of the entire group. This was clarified in the current version =
of the document:

   ...  The delegations by
   the IETF chair and the IAB chair need to be confirmed by the IESG and
   IAB respectively.  The terms of delegation is for a longer term for
   instance aligned with the IESG and IAB appointment cycles (roughly
   anual).

Russ=

From kent@bbn.com  Fri Apr 15 11:45:53 2011
Return-Path: <kent@bbn.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id C082AE06B0; Fri, 15 Apr 2011 11:45:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.686
X-Spam-Level: 
X-Spam-Status: No, score=-102.686 tagged_above=-999 required=5 tests=[AWL=-0.088, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ytiYINcEoz9A; Fri, 15 Apr 2011 11:45:52 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by ietfc.amsl.com (Postfix) with ESMTP id 07E8EE065F; Fri, 15 Apr 2011 11:45:51 -0700 (PDT)
Received: from dhcp89-089-062.bbn.com ([128.89.89.62]:49209) by smtp.bbn.com with esmtp (Exim 4.74 (FreeBSD)) (envelope-from <kent@bbn.com>) id 1QAo1f-00068K-2f; Fri, 15 Apr 2011 14:45:51 -0400
Mime-Version: 1.0
Message-Id: <p06240801c9ce424e70b1@[128.89.89.62]>
In-Reply-To: <tslzkp2elyf.fsf@mit.edu>
References: <tslhbbag9m1.fsf@mit.edu> <4D791B26.8020001@vpnc.org> <tsl4o7ag5fw.fsf@mit.edu> <4D79271E.6080707@vpnc.org> <tslzkp2elyf.fsf@mit.edu>
Date: Fri, 15 Apr 2011 14:45:46 -0400
To: Sam Hartman <hartmans-ietf@mit.edu>
From: Stephen Kent <kent@bbn.com>
Subject: Re: [secdir] Secdir review of draft-ietf-sidr-res-certs
Content-Type: multipart/alternative; boundary="============_-909229346==_ma============"
Cc: draft-ietf-sidr-res-certs@tools.ietf.org, 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, 15 Apr 2011 18:45:53 -0000

--============_-909229346==_ma============
Content-Type: text/plain; charset="us-ascii" ; format="flowed"

Sam,

In response to your comments on the res-certs draft, re the 
restrictive nature of the relying party checks in certs, we have 
prepare the following text that will be included as a new section in 
the document.

Steve

-----

Operational Considerations

This profile requires that relying parties reject certificates or 
CRLs that do not conform to the profile. (Through the remainder of 
this section the term "certificate" is used to refer to both 
certificates and CRLs.)
This includes certificates that contain extensions that are 
prohibited, but which are otherwise valid as per RFC 5280. This means 
that any change in the profile (e.g., extensions, permitted 
attributes or optional fields, or field encodings) for certificates 
used in the RPKI will not be backward compatible. In a general PKI 
context this constraint probably would cause serious problems. In the 
RPKI, several factors minimize the difficulty of effecting changes of 
this sort.

Note that the RPKI is unique in that every relying party (RP) 
requires access to every certificate and every CRL issued by the CAs 
in this system. An important update of the certificates and CRLs used 
in the RPKI must be supported by all CAs and RPs in the system, lest 
views of the RPKI data differ across RPs. Thus incremental changes 
require very careful coordination. It would not be appropriate to 
introduce a new extension, or authorize use of an extant, standard 
extension, for a security-relevant purpose on a piecemeal basis.

One might imagine that the "critical" flag in X.509 certificate and 
CRL extensions could be used to ameliorate this problem. However, 
this solution is not comprehensive, and does not address the problem 
of adding a new, security-critical extension. (This is because such 
an extension needs to be supported universally, by all CAs and RPs.) 
Also, while some standard extensions can be marked either critical or 
non-critical, at the discretion of the issuer, not all have this 
property, i.e., some standard extensions are always non-critical. 
Moreover, there is no notion of criticality for attributes within a 
name or optional fields within a field or an extension. Thus the 
critical flag is not a solution to this problem.

In typical PKI deployments there are few CAs and many RPs. However, 
in the RPKI, essentially every CA in the RPKI is also an RP. Thus the 
set of entities that will need to change in order to issue 
certificates under a new format is the same set of entities that will 
need to change to accept these new certificates. To the extent that 
this is literally true it says that CA/RP coordination for a change 
is tightly linked anyway. In reality there is an important exception 
to this general observation. Small ISPs and holders of 
provider-independent allocations are expected to use managed CA 
services, offered by RIRs/NIRs and by large ISPs. (All RIRs already 
offer managed CA services as part of their initial RPKI deployment.) 
This reduces the number of distinct CA implementations that are 
needed, and makes it easier to effect changes for certificate 
issuance. It seems very likely that these entities also will make use 
of RP software provided by their managed CA service provider, which 
reduces the number of distinct RP software implementations. Also note 
that many small ISPs (and holders of provider-independent 
allocations) employ default routes, and thus need not perform RP 
validation of RPKI data, eliminating these entities as RPs.

Widely available PKI RP software does not cache large numbers of 
certificates and CRLs, an essential strategy for the RPKI. It does 
not process manifest or ROA data structures, essential elements of 
the RPKI repository system. Experience shows that such software deals 
poorly with revocation status data. Thus extant RP software is not 
adequate for the RPKI, although some open source tools (e.g., OpenSSL 
and cryptlib) can be used as building blocks for an RPKI RP 
implementation. Thus it is anticipated that RPs will make use of 
software designed specifically for the RPKI environment, and 
available from a limited number of open sources. Several RIRs and two 
companies are providing such software today. Thus it is feasible to 
coordinate change to this software among the small number of 
developers/maintainers.

If the resource certificate format is changed in the future, e.g., by 
adding a new extension or changing the allowed set of name attributes 
or encoding of these attributes, the following procedure will be 
employed to effect deployment in the RPKI. The model is analogous to 
that described in [draft-ietf-sidr-algorithm-agility-00], but is 
simpler.

A new document will be issued as an update to this RFC.  The CP for 
the RPKI [ID-sidr-cp] will be updated to reference the new 
certificate profile. The new CP will define a new policy OID for 
certificates issued under the new certificate profile. The updated CP 
also will define a timeline for transition to the new certificate 
(CRL) format. This timeline will define 3 phases and associated dates:

	1- At the end of phase 1, all RPKI CAs MUST be capable of 
issuing certificates under the new profile, if requested by a 
subject. Any certificate issued under the new format will contain the 
new policy OID.

	2- During phase 2 CAs MUST issue certificates under the new 
profile, and these certificates MUST co-exist with certificates 
issued under the old format. (CAs will continue to issue certificates 
under the old OID/format as well.) The old and new certificates MUST 
be identical, except for the policy OID and any new extensions, 
encodings, etc. Relying parties MAY make use of the old or the new 
certificate formats when processing signed objects retrieved from the 
RPKI repository system. During this phase, a relying party that 
elects to process both formats will acquire the same values for all 
certificate fields that overlap between the old and new formats. Thus 
if either certificate format is verifiable, the relying party accepts 
the data from that certificate. This allows CAs to issue certificates 
under

	3- At the beginning of phase 3, all relying parties MUST be 
capable of processing certificates under the new format. During this 
phase CAs will issue new certificates ONLY under the new format. 
During this phase, certificates issued under the old OID will be 
replaced with certificates containing the new policy OID. The 
repository system will no longer require matching old and new 
certificates under the different formats.

At the end of phase 3, all certificates under the old OID will have 
been replaced. The resource certificate profile RFC will be replaced 
to remove support for the old certificate format, and the CP will be 
replaced to remove reference to the old policy OID and to the old 
resource certificate profile RFC. The system will have returned to a 
new, steady state.
--============_-909229346==_ma============
Content-Type: text/html; charset="us-ascii"

<!doctype html public "-//W3C//DTD W3 HTML//EN">
<html><head><style type="text/css"><!--
blockquote, dl, ul, ol, li { padding-top: 0 ; padding-bottom: 0 }
 --></style><title>Re: [secdir] Secdir review of
draft-ietf-sidr-res-certs</title></head><body>
<div>Sam,</div>
<div><br></div>
<div>In response to your comments on the res-certs draft, re the
restrictive nature of the relying party checks in certs, we have
prepare the following text that will be included as a new section in
the document.</div>
<div><br></div>
<div>Steve</div>
<div><br></div>
<div>-----</div>
<div><br></div>
<div><font color="#000000">Operational Considerations<br>
<br>
This profile requires that relying parties reject certificates or CRLs
that do not conform to the profile. (Through the remainder of this
section the term &quot;certificate&quot; is used to refer to both
certificates and CRLs.)<br>
This includes certificates that contain extensions that are
prohibited, but which are otherwise valid as per RFC 5280. This means
that any change in the profile (e.g., extensions, permitted attributes
or optional fields, or field encodings) for certificates used in the
RPKI will not be backward compatible. In a general PKI context this
constraint probably would cause serious problems. In the RPKI, several
factors minimize the difficulty of effecting changes of this sort.<br>
<br>
Note that the RPKI is unique in that every relying party (RP) requires
access to every certificate and every CRL issued by the CAs in this
system. An important update of the certificates and CRLs used in the
RPKI must be supported by all CAs and RPs in the system, lest views of
the RPKI data differ across RPs. Thus incremental changes require very
careful coordination. It would not be appropriate to introduce a new
extension, or authorize use of an extant, standard extension, for a
security-relevant purpose on a piecemeal basis.<br>
<br>
One might imagine that the &quot;critical&quot; flag in X.509
certificate and CRL extensions could be used to ameliorate this
problem. However, this solution is not comprehensive, and does not
address the problem of adding a new, security-critical extension.
(This is because such an extension needs to be supported universally,
by all CAs and RPs.) Also, while some standard extensions can be
marked either critical or non-critical, at the discretion of the
issuer, not all have this property, i.e., some standard extensions are
always non-critical. Moreover, there is no notion of criticality for
attributes within a name or optional fields within a field or an
extension. Thus the critical flag is not a solution to this
problem.<br>
<br>
In typical PKI deployments there are few CAs and many RPs. However, in
the RPKI, essentially every CA in the RPKI is also an RP. Thus the set
of entities that will need to change in order to issue certificates
under a new format is the same set of entities that will need to
change to accept these new certificates. To the extent that this is
literally true it says that CA/RP coordination for a change is tightly
linked anyway. In reality there is an important exception to this
general observation. Small ISPs and holders of provider-independent
allocations are expected to use managed CA services, offered by
RIRs/NIRs and by large ISPs. (All RIRs already offer managed CA
services as part of their initial RPKI deployment.) This reduces the
number of distinct CA implementations that are needed, and makes it
easier to effect changes for certificate issuance. It seems very
likely that these entities also will make use of RP software provided
by their managed CA service provider, which reduces the number of
distinct RP software implementations. Also note that many small ISPs
(and holders of provider-independent allocations) employ default
routes, and thus need not perform RP validation of RPKI data,
eliminating these entities as RPs.<br>
<br>
Widely available PKI RP software does not cache large numbers of
certificates and CRLs, an essential strategy for the RPKI. It does not
process manifest or ROA data structures, essential elements of the
RPKI repository system. Experience shows that such software deals
poorly with revocation status data. Thus extant RP software is not
adequate for the RPKI, although some open source tools (e.g., OpenSSL
and cryptlib) can be used as building blocks for an RPKI RP
implementation. Thus it is anticipated that RPs will make use of
software designed specifically for the RPKI environment, and available
from a limited number of open sources. Several RIRs and two companies
are providing such software today. Thus it is feasible to coordinate
change to this software among the small number of
developers/maintainers.</font></div>
<div><font color="#000000"><br>
If the resource certificate format is changed in the future, e.g., by&nbsp;
adding a new extension or changing the allowed set of name attributes
or encoding of these attributes, the following procedure will be
employed to effect deployment in the RPKI. The model is analogous to
that described in [draft-ietf-sidr-algorithm-agility-00], but is
simpler.<br>
<br>
A new document will be issued as an update to this RFC.&nbsp; The CP
for the RPKI [ID-sidr-cp] will be updated to reference the new
certificate profile. The new CP will define a new policy OID for
certificates issued under the new certificate profile. The updated CP
also will define a timeline for transition to the new certificate
(CRL) format. This timeline will define 3 phases and associated
dates:</font><br>
<font color="#000000"></font></div>
<div><font
color="#000000"><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</x-tab>1- At the end of phase 1, all RPKI CAs MUST be capable of
issuing certificates under the new profile, if requested by a subject.
Any certificate issued under the new format will contain the new
policy OID.</font></div>
<div><font color="#000000"><br></font></div>
<div><font
color="#000000"><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</x-tab>2- During phase 2 CAs MUST issue certificates under the new
profile, and these certificates MUST co-exist with certificates issued
under the old format. (CAs will continue to issue certificates under
the old OID/format as well.) The old and new certificates MUST be
identical, except for the policy OID and any new extensions,
encodings, etc. Relying parties MAY make use of the old or the new
certificate formats when processing signed objects retrieved from the
RPKI repository system. During this phase, a relying party that elects
to process both formats will acquire the same values for all
certificate fields that overlap between the old and new formats. Thus
if either certificate format is verifiable, the relying party accepts
the data from that certificate. This allows CAs to issue certificates
under</font></div>
<div><font color="#000000"><br></font></div>
<div><font
color="#000000"><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</x-tab>3- At the beginning of phase 3, all relying parties MUST be
capable of processing certificates under the new format. During this
phase CAs will issue new certificates ONLY under the new format.
During this phase, certificates issued under the old OID will be
replaced with certificates containing the new policy OID. The
repository system will no longer require matching old and new
certificates under the different formats.</font></div>
<div><font color="#000000"><br>
At the end of phase 3, all certificates under the old OID will have
been replaced. The resource certificate profile RFC will be replaced
to remove support for the old certificate format, and the CP will be
replaced to remove reference to the old policy OID and to the old
resource certificate profile RFC. The system will have returned to a
new, steady state.</font></div>
</body>
</html>
--============_-909229346==_ma============--

From llynch@civil-tongue.net  Sat Apr 16 07:51:38 2011
Return-Path: <llynch@civil-tongue.net>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id F0286E06B5 for <ietf@ietfc.amsl.com>; Sat, 16 Apr 2011 07:51:38 -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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9OS-ZsduNUNJ for <ietf@ietfc.amsl.com>; Sat, 16 Apr 2011 07:51:38 -0700 (PDT)
Received: from hiroshima.bogus.com (hiroshima.bogus.com [IPv6:2001:418:1::80]) by ietfc.amsl.com (Postfix) with ESMTP id E3E6EE069A for <ietf@ietf.org>; Sat, 16 Apr 2011 07:51:37 -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 p3GEpRBX016178 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 16 Apr 2011 07:51:28 -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 p3GEpQ70016175; Sat, 16 Apr 2011 07:51:27 -0700 (PDT) (envelope-from llynch@civil-tongue.net)
Date: Sat, 16 Apr 2011 07:51:26 -0700 (PDT)
From: Lucy Lynch <llynch@civil-tongue.net>
X-X-Sender: llynch@hiroshima.bogus.com
To: dcrocker@bbiw.net
Subject: Re: IAOC: delegating ex-officio responsibility
In-Reply-To: <4DA8685F.5050504@dcrocker.net>
Message-ID: <alpine.BSF.2.00.1104160711480.14890@hiroshima.bogus.com>
References: <2BE582FA-2682-4232-9D83-23A03F01A0DB@NLnetLabs.nl> <6.2.5.6.2.20110330073936.0e1899d0@resistor.net> <E2E41FDE-3818-4513-9933-CB1E0326B43E@nlnetlabs.nl> <6.2.5.6.2.20110330113947.0c948bc0@resistor.net> <4D942843.4060804@gmail.com> <6.2.5.6.2.20110331120351.09488990@resistor.net> <4D955661.8050502@gmail.com> <9C81C0F6-3ABE-4479-8C5E-C20C486D052A@gmail.com> <82A347CC-BB19-4A73-8E8A-924FBAA92A5F@NLnetLabs.nl> <84D6568B-18C9-47B2-A457-C51C2FB3351F@gmail.com> <5419FA805EF52E79D7822966@PST.JCK.COM> <DAC0FFD9-9B3B-4726-B56B-5E9BE5A5F1D1@gmail.com> <4DA8685F.5050504@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: Bob Hinden <bob.hinden@gmail.com>, 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, 16 Apr 2011 14:51:39 -0000

On Fri, 15 Apr 2011, Dave CROCKER wrote:

>
>
> On 4/14/2011 9:51 AM, Bob Hinden wrote:
>> My concern is that this proposed change would likely make the IAOC work
>> worse.   That is, I think it would have a negative impact on the operations 
>> of
>> the IETF and that is why I am concerned.
>
>
> Bob,
>
> That is a concrete and basic assertion.  Please put some flesh on its bones 
> so that the basis for your view can be understood better.

Let me take a run at this.

Back in the pre-history of BCP 101 we had very little control over many of 
the administrative functions that support the actual work of the IETF. We 
had a single long term relationship with an organization that run the 
meetings and collected fees "on behalf" of the the IETF and performed many 
of the secretariat functions. Over time, this relationship had frayed 
considerably (on both sides) and the community become increasingly 
restive, looking for more autonomy and a better understanding of our own 
internal business processes.

There were a number of drivers for the (extended) discussions about 
process and one of these was overload on the volunteers in the leadership 
roles. Among the solutions crafted up were the creation of the IASA and 
the hiring of our first paid employee (IAD). We also ended our 
relationship with the existing secretariat and moved to a process of 
contracting for services through the IAD with over site from what became 
the IAOC. The termination of our relationship with CNRI then spawned the 
creation of the IETF Trust. All of this took an enormous amount of 
community time and energy and a lot of tough questions had to be asked and 
answered. I'll just highlight a couple:

- an all volunteer organization hired it's first paid employee.
     note that this can be a slippery and expensive slope and there
     was always a risk that this might change the volunteer culture
- the IASA/IAOC/IETF Trust were tasked with stewardship for the
   administrative health of the IETF.
- the Trust formalized the future disposition of IETF assets and
   allowed an orderly transition from claims from previous administrations.

My belief at the time was that the primary concerns in all of this were a 
desire for greater transparency and organizational autonomy. There was a 
clear demand from many that the IETF "own" it's own processes.

> The implication is that the people sitting in the positions of IAB Chair and 
> IETF Chair are essential to the good operation of the IAOC/Trust.  Someone 
> else from their groups or even someone else that they appoint from outside 
> cannot perform the task of IAOC/Trust member adequately.

I think this is the wrong question. I don't think this is about the
people who sit on the IAOC or the Trust, it is about the roles. Their
participation is part of the chain of accountability to the community.
The IAOC was crafted to include both the IAB and IETF Chairs as well
as the ISOC CEO in their respective roles and not as Fred, Harold, and
Lynn (as members of the IETF community).

> Why?
>
> What are the specific contributions (insights and skills) that these roles 
> regularly perform, in the conduct of the IAOC/Trust that cannot be performed 
> adequately by others?

see above.

One more point here: as a former Chair of the IAOC (IAB appointed
member from the community) I'm sympathetic the the overload arguments
but I'll note that absent the IAB/IETF chairs the work of the IAOC
chair and the weight put on that role may increase in unexpected ways.

I agree with many of the points that Bob, Brian, Leslie, and Jari
have made in earlier posts and think that we need to take a broader
view of the problems we're trying to solve here. Role overload is
an on-going problem but I'm not sure we solve this by moving the
administrative accountability we gained through BCP 101 to additional
volunteers.

- Lucy

> d/
>
> ps. Reminder: I've just joined the IAOC/Trust, which means I've attended a 
> few meetings and seen some operation.  As always, my comments have nothing to 
> do with the individuals; this is about organizational design.
>
>

From evnikita2@gmail.com  Sun Apr 17 01:21:38 2011
Return-Path: <evnikita2@gmail.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 3AA74E06DA for <ietf@ietfc.amsl.com>; Sun, 17 Apr 2011 01:21: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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d99V1ostb9kz for <ietf@ietfc.amsl.com>; Sun, 17 Apr 2011 01:21:37 -0700 (PDT)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by ietfc.amsl.com (Postfix) with ESMTP id 34E17E06CD for <ietf@ietf.org>; Sun, 17 Apr 2011 01:21:37 -0700 (PDT)
Received: by bwz13 with SMTP id 13so3693121bwz.31 for <ietf@ietf.org>; Sun, 17 Apr 2011 01:21:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=lwUMinJbJcJugmhf0oY3+QJTpWDf2bHBszmeJB53cME=; b=hPR9sByXr1QcG84uGz1OTwFCbQoEenBl1QxqBXnEk27fGTs0xvwIStsQ6q8S7S2KOd 4sKNWSm+v4rvbO+zG8iu8KIUgn2DX65ZYyIlbv4txPeoxG3H+e66LE1YBcBrh6ClOBiV CmCpq374+SSSGH/3Qaz/SZTHpg2RwWI4hxQRI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=a7QdOYNSDC2qfn6bympVtXDpEthJwgy+MlA0UG/FGWtSMmm2jwy0X5vOY/jbo8/q53 V04cdOLM8L2h7svoUEPHlVVMWBvbQeizBTgYC0LVR3fpSGpxe6/eHx0FEsPpHzf/c8Ct i7lJ+mFDjatxgBMNBwuqpmlc2DYYnCSrHbUL4=
Received: by 10.204.153.207 with SMTP id l15mr3006890bkw.111.1303028495050; Sun, 17 Apr 2011 01:21:35 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id c11sm2478230bkc.14.2011.04.17.01.21.32 (version=SSLv3 cipher=OTHER); Sun, 17 Apr 2011 01:21:33 -0700 (PDT)
Message-ID: <4DAAA335.7080609@gmail.com>
Date: Sun, 17 Apr 2011 11:22:13 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
Subject: Re: draft-housley-two-maturity-levels-05
References: <20110406152226.000AF3A6803@core3.amsl.com> <24582656-5993-46C3-B82A-883E8BA4E9A0@vigilsec.com>
In-Reply-To: <24582656-5993-46C3-B82A-883E8BA4E9A0@vigilsec.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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, 17 Apr 2011 08:21:38 -0000

06.04.2011 18:27, Russ Housley wrote:
> This revision proposes a solution to the issue raised by Brian Carpenter about documents lingering at Draft Standard.  Some people thought it was a problem.  Others thought it did not matter.  The proposed solution leaves the matter in the hands of the IESG.
Russ,

Hello again.  I have another minor comment regarding this document.
>
> 4. Downward References Permitted
This section says nothing about references to documents with no status 
("pre-IETF" RFCs).  Maybe informative references to such RFCs should be 
allowed.  And what about normative ones?  Whether the RFC 3967 procedure 
will be used in such cases, or such references are disallowed in 
Standards Track docs?  I think this should also be mentioned in your draft.

Mykyta Yevstifeyev

> Russ
>
>
> Begin forwarded message:
>
>> From: IETF I-D Submission Tool<idsubmission@ietf.org>
>> Date: April 6, 2011 11:22:25 AM EDT
>> To: housley@vigilsec.com
>> Cc: dcrocker@bbiw.net, eburger@standardstrack.com
>> Subject: New Version Notification for draft-housley-two-maturity-levels-05
>>
>>
>> A new version of I-D, draft-housley-two-maturity-levels-05.txt has been successfully submitted by Russ Housley and posted to the IETF repository.
>>
>> Filename:	 draft-housley-two-maturity-levels
>> Revision:	 05
>> Title:		 Reducing the Standards Track to Two Maturity Levels
>> Creation_date:	 2011-04-06
>> WG ID:		 Independent Submission
>> Number_of_pages: 7
>>
>> Abstract:
>> This document proposes several changes to the Internet Engineering
>> Task Force (IETF) Standards Process defined in RFC 2026, primarily a
>> reduction from three IETF standards track maturity levels to two.
>>
>> {{ RFC Editor: please change "proposes several changes to the" to
>> "changes the". }}
>>
>>
>>
>> The IETF Secretariat.
>>
>>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>


From john-ietf@jck.com  Sun Apr 17 06:27:37 2011
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 137E4E074A; Sun, 17 Apr 2011 06:27: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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J9b-w3dVw+l8; Sun, 17 Apr 2011 06:27:36 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfc.amsl.com (Postfix) with ESMTP id 491F3E0694; Sun, 17 Apr 2011 06:27:36 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QBS0j-000PXc-Lc; Sun, 17 Apr 2011 09:27:33 -0400
Date: Sun, 17 Apr 2011 09:27:32 -0400
From: John C Klensin <john-ietf@jck.com>
To: Stephen Kent <kent@bbn.com>, Sam Hartman <hartmans-ietf@mit.edu>
Subject: Re: [secdir] Secdir review of draft-ietf-sidr-res-certs
Message-ID: <1446DA6A65B664240D8AA4F9@PST.JCK.COM>
In-Reply-To: <p06240801c9ce424e70b1@[128.89.89.62]>
References: <tslhbbag9m1.fsf@mit.edu> <4D791B26.8020001@vpnc.org>	<tsl4o7ag5fw.fsf@mit.edu> <4D79271E.6080707@vpnc.org>	<tslzkp2elyf.fsf@mit.edu> <p06240801c9ce424e70b1@[128.89.89.62]>
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: draft-ietf-sidr-res-certs@tools.ietf.org, 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, 17 Apr 2011 13:27:37 -0000

Steve,
Two things:


(1) Given the variable amount of time it takes to get RFCs
issued/ published after IESG signoff, are you and the WG sure
that you want to tie the phases of the phase-in procedure to RFC
publication?

(2) There is an incomplete sentence at the end of (2): "This
allows CAs to issue certificates under" (more context below).

   john



--On Friday, April 15, 2011 14:45 -0400 Stephen Kent
<kent@bbn.com> wrote:

> 	2- During phase 2 CAs MUST issue certificates under the new
> profile, and these certificates MUST co-exist with
> certificates issued under the old format. (CAs will continue
> to issue certificates under the old OID/format as well.) The
> old and new certificates MUST be identical, except for the
> policy OID and any new extensions, encodings, etc. Relying
> parties MAY make use of the old or the new certificate formats
> when processing signed objects retrieved from the RPKI
> repository system. During this phase, a relying party that
> elects to process both formats will acquire the same values
> for all certificate fields that overlap between the old and
> new formats. Thus if either certificate format is verifiable,
> the relying party accepts the data from that certificate. This
> allows CAs to issue certificates under
> 
> 	3- At the beginning of phase 3, all relying parties MUST be
> capable of processing certificates under the new format.
>...


From llynch@civil-tongue.net  Sun Apr 17 09:14:53 2011
Return-Path: <llynch@civil-tongue.net>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 2BB1CE0775 for <ietf@ietfc.amsl.com>; Sun, 17 Apr 2011 09:14:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.979
X-Spam-Level: 
X-Spam-Status: No, score=-101.979 tagged_above=-999 required=5 tests=[AWL=-0.620, BAYES_00=-2.599, SARE_LWSHORTT=1.24, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eQd8N6U1rj0p for <ietf@ietfc.amsl.com>; Sun, 17 Apr 2011 09:14:52 -0700 (PDT)
Received: from hiroshima.bogus.com (hiroshima.bogus.com [IPv6:2001:418:1::80]) by ietfc.amsl.com (Postfix) with ESMTP id 4CBF4E06EC for <ietf@ietf.org>; Sun, 17 Apr 2011 09:14:52 -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 p3HGEfpg050640 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 17 Apr 2011 09:14:41 -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 p3HGEehr050637; Sun, 17 Apr 2011 09:14:41 -0700 (PDT) (envelope-from llynch@civil-tongue.net)
Date: Sun, 17 Apr 2011 09:14:40 -0700 (PDT)
From: Lucy Lynch <llynch@civil-tongue.net>
X-X-Sender: llynch@hiroshima.bogus.com
To: John C Klensin <john@jck.com>
Subject: Re: IAOC: delegating ex-officio responsibility
In-Reply-To: <ABEF0352D5DCE3BF80AFC232@PST.JCK.COM>
Message-ID: <alpine.BSF.2.00.1104170904420.50389@hiroshima.bogus.com>
References: <2BE582FA-2682-4232-9D83-23A03F01A0DB@NLnetLabs.nl> <6.2.5.6.2.20110330073936.0e1899d0@resistor.net> <E2E41FDE-3818-4513-9933-CB1E0326B43E@nlnetlabs.nl> <6.2.5.6.2.20110330113947.0c948bc0@resistor.net> <4D942843.4060804@gmail.com>  <6.2.5.6.2.20110331120351.09488990@resistor.net> <4D955661.8050502@gmail.com> <9C81C0F6-3ABE-4479-8C5E-C20C486D052A@gmail.com> <82A347CC-BB19-4A73-8E8A-924FBAA92A5F@NLnetLabs.nl> <84D6568B-18C9-47B2-A457-C51C2FB3351F@gmail.com> <5419FA805EF52E79D7822966@PST.JCK.COM> <DAC0FFD9-9B3B-4726-B56B-5E9BE5A5F1D1@gmail.com> <4DA8685F.5050504@dcrocker.net> <alpine.BSF.2.00.1104160711480.14890@hiroshima.bogus.com> <ABEF0352D5DCE3BF80AFC232@PST.JCK.COM>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: Bob Hinden <bob.hinden@gmail.com>, Dave Crocker <dcrocker@bbiw.net>, 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, 17 Apr 2011 16:14:53 -0000

On Sat, 16 Apr 2011, John C Klensin wrote:
<snip>
>
> At the risk of agreeing violently with Dave, I think the series
> of comments above, and referenced above, are missing something.
> None of this familiy of "delegation" or "someone else" proposals
> requires that the IAB or IESG Chairs not serve on the IAOC.  If
> they think that is sensible and they have the time, they are
> free to do that.  We might even strongly encourage it.  However,
> if those people conclude that limited available time is better
> spent in other ways or that, if they take the IAOC position,
> they would not be able to devote adequate attention to it,
> aren't we better off giving them the flexibility and discretion
> to make that decision?  Similarly, if someone tells the
> appointing body "I have the time and resources to take on the
> IAB Chair or IETF Chair position but only if that position does
> not include the responsibility of sitting on the IAOC" isn't it
> better to give those bodies the option of considering that
> person rather than limiting the choices to those who can sign up
> for all of the job?

I'm not arguing that any of the IETF/IAB/etc hat wearers are
inexhaustible resources, I'm saying that the AdminRest process
looked hard at the composition and duties of the IAOC and if
the needs have changed, or the community concerns have shifted,
we should approach the current problems in a holistic manner and not
engineer short term solutions on the fly. I'll point you at your
own last paragraph here;

http://www.ietf.org/mail-archive/web/ietf/current/msg33932.html


> At least from my perspective, broadening the flexibility
> available to already-appointed IAB and IETF Chairs and to the
> bodies that appoint them is the real issue here.  _Requiring_
> that they serve on the IAOC does not create more time or
> resources, it just limits the range of people who can take those
> positions or, more likely, raises the odds of getting someone
> onto the IAOC who won't be able to pay full (or even adequate)
> attention.

certainly one possible outcome

> So. in addition to the questions Dave posed, the question I
> would address to you and Bob is whether, given a hypothetical
> choice of someone sitting on the IAOC ex-officio but not being
> able to really pay attention because he or she concludes that
> there are more pressing priorities and having someone
> representing the IAB or IESG who really can pay attention, which
> one you would pick.  In the worst case, if you prefer to have
> the Chairs nominally present but not paying complete attention,
> then keep insisting that they are the only ones who can possibly
> occupy the IAOC slot.

I would of course prefer full attention and skilled participation.
I'd also like the full confidence of the community in the process.

> As part of that, figure out how you are going to convince the
> Nomcom and the IAB that selecting people for the Chair roles
> should have "will give IAOC first priority regardless of their
> judgment about the importance of other aspects of their roles"
> as an absolute criterion and/or how you are going to convince
> the community to recall anyone in the Chair roles who does not
> give the IAOC that priority.

New/old  problem that may require additional revision on several
fronts - not just the IAOC.

- Lucy

> best,
>  john
>

From dhc2@dcrocker.net  Sun Apr 17 09:45:26 2011
Return-Path: <dhc2@dcrocker.net>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id D5F96E06E5 for <ietf@ietfc.amsl.com>; Sun, 17 Apr 2011 09:45:26 -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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PI+-xINjPCht for <ietf@ietfc.amsl.com>; Sun, 17 Apr 2011 09:45:25 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfc.amsl.com (Postfix) with ESMTP id 92ADCE066B for <ietf@ietf.org>; Sun, 17 Apr 2011 09:45:25 -0700 (PDT)
Received: from [192.168.1.3] (adsl-67-127-56-68.dsl.pltn13.pacbell.net [67.127.56.68]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p3HGjCMK024543 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Sun, 17 Apr 2011 09:45:20 -0700
Message-ID: <4DAB1918.2000000@dcrocker.net>
Date: Sun, 17 Apr 2011 09:45:12 -0700
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Lucy Lynch <llynch@civil-tongue.net>
Subject: Re: IAOC: delegating ex-officio responsibility
References: <2BE582FA-2682-4232-9D83-23A03F01A0DB@NLnetLabs.nl> <6.2.5.6.2.20110330073936.0e1899d0@resistor.net> <E2E41FDE-3818-4513-9933-CB1E0326B43E@nlnetlabs.nl> <6.2.5.6.2.20110330113947.0c948bc0@resistor.net> <4D942843.4060804@gmail.com> <6.2.5.6.2.20110331120351.09488990@resistor.net> <4D955661.8050502@gmail.com> <9C81C0F6-3ABE-4479-8C5E-C20C486D052A@gmail.com> <82A347CC-BB19-4A73-8E8A-924FBAA92A5F@NLnetLabs.nl> <84D6568B-18C9-47B2-A457-C51C2FB3351F@gmail.com> <5419FA805EF52E79D7822966@PST.JCK.COM> <DAC0FFD9-9B3B-4726-B56B-5E9BE5A5F1D1@gmail.com> <4DA8685F.5050504@dcrocker.net> <alpine.BSF.2.00.1104160711480.14890@hiroshima.bogus.com>
In-Reply-To: <alpine.BSF.2.00.1104160711480.14890@hiroshima.bogus.com>
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, 17 Apr 2011 09:45:20 -0700 (PDT)
Cc: Bob Hinden <bob.hinden@gmail.com>, IETF Discussion <ietf@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: Sun, 17 Apr 2011 16:45:27 -0000

On 4/16/2011 7:51 AM, Lucy Lynch wrote:
> On Fri, 15 Apr 2011, Dave CROCKER wrote:
>> That is a concrete and basic assertion. Please put some flesh on its bones so
>> that the basis for your view can be understood better.
>
> Let me take a run at this.
>
> Back in the pre-history of BCP 101 we had very little control over many of the
...

I do not see anything in the extended history you provide that explains Bob's 
assertion of what is needed now.

Perhaps I missed it.  If so, please point to the specific requirements that 
apply now.

Better still, let's let Bob explain his own assertion of the requirement.

(It's of course fine for you to explain your own view, but Bob is the current 
chair of the IAOC and speaks from a different, current vantage point than anyone 
else.)


>> The implication is that the people sitting in the positions of IAB Chair and
>> IETF Chair are essential to the good operation of the IAOC/Trust. Someone else
>> from their groups or even someone else that they appoint from outside cannot
>> perform the task of IAOC/Trust member adequately.
>
> I think this is the wrong question. I don't think this is about the
> people who sit on the IAOC or the Trust, it is about the roles.

That's what I was referring to. No idea how my text appears to say otherwise.

However "roles" do not perform.  People occupying those roles do.


>> Why?
>>
>> What are the specific contributions (insights and skills) that these roles
>> regularly perform, in the conduct of the IAOC/Trust that cannot be performed
>> adequately by others?
>
> see above.

That's unfortunately circular and ambiguous reference.  What text specifically 
provide the answer to this question?


> One more point here: as a former Chair of the IAOC (IAB appointed
> member from the community) I'm sympathetic the the overload arguments
> but I'll note that absent the IAB/IETF chairs the work of the IAOC
> chair and the weight put on that role may increase in unexpected ways.

This is another assertion without providing substance.  My original note asked 
for the substance so that the discussion can include more than expert assertions 
of agreement or disagreement.

Folks need to note some rather basic points:

1.   Things are working fine, except that they aren't.

      This entire thread comes from a proposal from folk who are overloaded and 
who need things to change.

When someone says "I cannot keep doing the task I've been assigned" either they 
are not competent to the task or the nature or terms of task need to change.  I 
don't see any basis for considering the former, which leaves us with the latter.

By any reasonable measure, the IETF has concentrated far too much work onto its 
two Chairs.  For an organization devoted to an industry based on distributed 
control, we have a remarkable dislike to distributing control within the 
organization.  One effect of this is to dramatically reduce the pool of people 
available for those concentrated jobs.  Here we have a request for a particular 
reduction.  If that reduction is not tolerable, we need to understand why?

Separately, of course, we need to consider the details of the change and 
consider tradeoffs for alternative solutions.  To do that, we need to understand 
the requirements that are at issue.  Hence my questions to Bob.


2.   The view that no change should occur without a "holistic" review is a 
consistently effective way to kill any change effort.  We have plenty of 
experience with its effectiveness.

      Note that the most effective enhancements to successful IETF work is by 
incremental change, not "holistic" re-evaluation.

Here we have a proposal from those experiencing the problem.  A proposal states 
the problem and offers a solution.

My original question to Bob was to help us assess the assertion of the problem 
and the assertion of the solution.  (One or another notes implies that I've 
stated an opinion about the proposal, but I haven't.  For now, I'm trying to get 
source data, including performance requirements and the logic behind the 
proposal.)

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From joelja@bogus.com  Mon Apr 18 00:03:56 2011
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id BE697E0660 for <ietf@ietfc.amsl.com>; Mon, 18 Apr 2011 00:03:56 -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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W1jTaA+tmgI4 for <ietf@ietfc.amsl.com>; Mon, 18 Apr 2011 00:03:56 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfc.amsl.com (Postfix) with ESMTP id 1BC21E0655 for <ietf@ietf.org>; Mon, 18 Apr 2011 00:03:56 -0700 (PDT)
Received: from 23173jjaeggli.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 p3I73nJR002796 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Mon, 18 Apr 2011 07:03:51 GMT (envelope-from joelja@bogus.com)
Message-ID: <4DABE255.3080209@bogus.com>
Date: Mon, 18 Apr 2011 00:03:49 -0700
From: Joel Jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.15) Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: IETF-Discussion list <ietf@ietf.org>, i.grok@comcast.net
Subject: Re: audio streaming archive...
References: <201104140254.p3E2sMjk014471@fs4113.wdf.sap.corp>	<4DA67EF0.4050209@bogus.com> <20110415032222.GB22852@odin.ulthar.us>
In-Reply-To: <20110415032222.GB22852@odin.ulthar.us>
X-Enigmail-Version: 1.1.1
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.2 (nagasaki.bogus.com [147.28.0.81]); Mon, 18 Apr 2011 07:03:52 +0000 (UTC)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 07:03:56 -0000

On 4/14/11 8:22 PM, Scott Schmit wrote:
> On Wed, Apr 13, 2011 at 09:58:24PM -0700, Joel Jaeggli wrote:
>> there was a naming convention issue on the channel5 recorder which I
>> thought that we caught all of those by I could be wrong...
>>
>> The contractor has the channel8 recorder and should be able toretrive
>> the file.
> 
> Is there an ETA for the fix to that?

you might want to talk to the secretariate or the contractor (whom I
cced on the previous message) I don't have access to the equipment.

> I listened to both the .mp3 and .mp3.1 file for wed-am ch8, and neither
> sounds like the DANE session to me.
> 


From bernard_aboba@hotmail.com  Mon Apr 18 11:08:32 2011
Return-Path: <bernard_aboba@hotmail.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 0C547E06F8 for <ietf@ietfc.amsl.com>; Mon, 18 Apr 2011 11:08:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.472
X-Spam-Level: 
X-Spam-Status: No, score=-102.472 tagged_above=-999 required=5 tests=[AWL=0.126, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LBAkhTVY54wL for <ietf@ietfc.amsl.com>; Mon, 18 Apr 2011 11:08:29 -0700 (PDT)
Received: from blu0-omc2-s31.blu0.hotmail.com (blu0-omc2-s31.blu0.hotmail.com [65.55.111.106]) by ietfc.amsl.com (Postfix) with ESMTP id B3B90E06A2 for <ietf@ietf.org>; Mon, 18 Apr 2011 11:08:29 -0700 (PDT)
Received: from BLU152-W63 ([65.55.111.73]) by blu0-omc2-s31.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 18 Apr 2011 11:08:29 -0700
Message-ID: <BLU152-w6382721ADDE9576006977D93910@phx.gbl>
Content-Type: multipart/alternative; boundary="_14f509f2-7499-4473-ada3-3d431548c954_"
X-Originating-IP: [98.203.198.61]
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: <ietf@ietf.org>
Subject: Re: Last Call: <draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03.txt> (IPv6 AAAA DNS Whitelisting Implications) to Informational RFC
Date: Mon, 18 Apr 2011 11:08:28 -0700
Importance: Normal
MIME-Version: 1.0
X-OriginalArrivalTime: 18 Apr 2011 18:08:29.0489 (UTC) FILETIME=[9EE52A10:01CBFDF3]
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 18:08:32 -0000

--_14f509f2-7499-4473-ada3-3d431548c954_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Overall=2C I think this is a useful document. =20

My suggestions below mostly relate to potential organizational improvements=
=2C as well as as a bit more detail in some areas.



Section 2

This section talks about how white-listing works=2C but does not talk about=
 potential mechanisms by which the whitelist is determined.  For example=2C=
 in addition to techniques for manually maintaining the whitelist=2C there =
have been some suggestions that would involve automatic determinations (e.g=
. only answering with AAAA RRs if the query comes in over IPv6).   It might=
 be useful to cover some of the proposals=2C since they might have differen=
t implications. =20

Section 2.1

Is the term "IP address" here intended to include both IPv4 and IPv6 addres=
ses?=20

Section 3

   At least one highly-trafficked domain has noted that they have
   received requests to not send DNS responses with AAAA resource
   records to particular resolvers.  In this case=2C the operators of
   those recursive resolvers have expressed a concern that their IPv6
   network infrastructure is not yet ready to handle the large traffic
   volume which may be associated with the hosts in their network
   connecting to the websites of these domains.  This concern is clearly
   a temporary consideration relating to the deployment of IPv6 network
   infrastructure on the part of networks with end user hosts=2C rather
   than a long-term concern.  These end user networks may also have
   other tools at their disposal in order to address this concern=2C
   including applying rules to network equipment such as routers and
   firewalls (this will necessarily vary by the type of network=2C as well
   as the technologies used and the design of a given network)=2C as well
   as configuration of their recursive resolvers (though modifying or
   suppressing AAAA resource records in a DNSSEC-signed domain on a
   Security-Aware Resolver will be problematic Section 10.1).

[BA]  This paragraph seems to be distinguishing "blacklisting" from "whitel=
isting" as well as describing some of the implications of attempting to sup=
press AAAA RRs in the recursive resolver.  It might be worthwhile to introd=
uce the distinction between "blacklisting" and "whitelisting" earlier on.  =
Such a section might also include the following paragraph from Section 7.3.=
7:

   It is unclear when and if it would be appropriate to change from
   whitelisting to blacklisting=2C and whether or how this could feasibly
   be coordinated across the Internet=2C which may be proposed or
   implemented on an ad hoc basis when a majority of networks (or
   allocated IPv6 address blocks) have been whitelisted.  Finally=2C some
   parties implementing DNS whitelisting consider this to be a temporary
   measure.  As such=2C it is not clear how these parties will judge the
   network conditions to have changed sufficiently to justify disabling
   DNS whitelisting and/or what the process and timing will be in order
   to discontinue this practice.

Section 4

   While in Section 1 the level of IPv6-related impairment has been
   estimated to be as high as 0.078% of Internet users=2C which is a
   primary motivation cited for the practice of DNS whitelisting=2C it is
   not clear if the level of IPv4-related impairment is more or less
   that this percentage (which in any case is likely to have declined
   since its original citation).  Indeed=2C as at least one document
   reviewer has pointed out=2C it may simply be that websites are only
   measuring IPv6 impairments and not IPv4 impairments=2C whether because
   IPv6 is new or whether those websites are simply unable to or are
   otherwise not in a position to be able to measure IPv4 impairment
   (since this could result in no Internet access whatsoever).  As a
   result=2C it is worth considering that IPv4-related impairment could
   exceed that of IPv6-related impairment and that such IPv4-related
   impairment may have simply been accepted as "background noise" on the
   Internet for a variety of reasons.  Of course=2C this comparison of the
   level of worldwide IPv6 impairments to IPv4 impairments is
   speculation=2C as the author is not aware of any good measurement of
   IPv4-related impairments which are comparable in nature to the IPv6-
   related impairment measurements which have recently been conducted
   around the world.

[BA] It seems to me that discussion of measurement issues should probably c=
ome earlier in the document=2C possibly in its own section. =20
My suggestion is to move this paragraph as well other paragraphs referring =
to measurement into its own section (Section 1.1?).=20
The following paragraph from Section 3.2 might be a candidate:

   Finally=2C some domains=2C have run IPv6 experiments whereby they added
   AAAA resource records and observed and measured errors [Heise Online
   Experiment]=2C which should be important reading for any domain
   contemplating either the use of DNS whitelisting or simply adding
   IPv6 addressing to their site.

Section 6

This section talks about Adhoc versus universal deployment scenarios.  It s=
trikes me that the underlying distinction is not so much the universality o=
f whitelisting deployment as much as whether the whitelists are shared or i=
ndependent. The document seems to argue that independence is the most likel=
y outcome:

   It is probably unlikely that a single clearinghouse for
   managing whitelisting is possible=3B it will more likely be unique to
   the source content owners and/or domains which implement DNS
   whitelists.

[BA] While a single clearinghouse might be unlikely=2C I'm not sure that th=
is necessarily argues against the likelihood of multiple clearinghouses.  I=
t might be helpful to provide a little more detail on the motivation behind=
 the views on the likelihood of clearinghouses emerging (e.g. is this based=
 on discussions with content providers?).  For example=2C if the concept of=
 IPv6 whitelisting becomes more widespread among smaller content providers=
=2C it would seem that the need for clearinghouses might emerge.

Section 7.3.3

It seems to me that there might be some operational implications that might=
 arise from some potential whitelisting mechanisms such as differentiating =
DNS queries sent over IPv6 versus IPv4. =20

Section 7.6

   At the same time=2C as noted in Section 3=2C some highly-trafficked
   domains may find the prospect of transitioning to IPv6 daunting
   without having some short-term ability to incrementally control the
   amount and source of IPv6 traffic to their domains.

[BA] The issue of traffic control is a distinct problem. This is partially =
discussed in Section 3 (from the point of view of the recursive resolver ow=
ner)=2C
but here it is referring to the problem as experienced by the content owner=
.  Perhaps it would make sense to make the distinction between the=20
"impairment" and "traffic control" problems earlier? (maybe even in Section=
 1=2C referring to a subsequent discussion in Section 3).=20

Section 8.3.1

This section refers to fixes for the "impairment" problem=2C but as noted a=
bove=2C there may also be other potential motivations for whitelisting.=20

Section 9

   World IPv6 Day=2C sponsored by the Internet Society [World IPv6 Day]=2C
   is scheduled to occur on June 8=2C 2011.  This will be an opportunity
   for domains to add AAAA resource records to the DNS without using DNS
   whitelisting.  As a result=2C this is likely an excellent opportunity
   for domains to evaluate the utility or necessity of DNS whitelisting=2C
   even in the short-term.  A major German news website=2C Heise Online=2C
   also ran a similar IPv6 experiment whereby they added AAAA resource
   records and observed and measured any errors [Heise Online
   Experiment]=2C which is important reading for any domain contemplating
   either the use of DNS whitelisting or simply adding IPv6 addressing
   to their site.

[BA] You might consider moving this paragraph into a separate "measurement"=
 section (e.g. Section 1.1).=20

=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
From: The IESG <iesg-secretary@ietf.org>=20

To: IETF-Announce <ietf-announce@ietf.org>=20

Reply-to: iesg-secretary@ietf.org=20

Subject: Last Call:=20
<draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03.txt> (IPv6=20
AAAA DNS Whitelisting Implications) to Informational RFC=20

X-RSN: 1/0/934/8529/9220=20

=20

The IESG has received a request from the IPv6 Operations WG (v6ops) to=20

consider the following document:=20

- 'IPv6 AAAA DNS Whitelisting Implications'=20

  <draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03.txt> as an=20

Informational RFC=20

=20

The IESG plans to make a decision in the next few weeks=2C and solicits=20

final comments on this action. Please send substantive comments to the=20

ietf@ietf.org mailing lists by 2011-04-29. Exceptionally=2C comments may be=
=20

sent to iesg@ietf.org instead. In either case=2C please retain the=20

beginning of the Subject line to allow automated sorting.=20

=20

The file can be obtained via=20

http://datatracker.ietf.org/doc/draft-ietf-v6ops-v6-aaaa-whitelisting-impli=
cations/=20

=20

IESG discussion can be tracked via=20

http://datatracker.ietf.org/doc/draft-ietf-v6ops-v6-aaaa-whitelisting-impli=
cations/=20

=20

=20

=20

No IPR declarations have been submitted directly on this I-D.=20

_______________________________________________=20

IETF-Announce mailing list=20

IETF-Announce@ietf.org=20

https://www.ietf.org/mailman/listinfo/ietf-announce=20
=20

 		 	   		  =

--_14f509f2-7499-4473-ada3-3d431548c954_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Tahoma
}
--></style>
</head>
<body class=3D'hmmessage'>
Overall=2C I think this is a useful document.&nbsp=3B <br><br>My suggestion=
s below mostly relate to potential organizational improvements=2C as well a=
s as a bit more detail in some areas.<br><br><br><br>Section 2<br><br>This =
section talks about how white-listing works=2C but does not talk about pote=
ntial mechanisms by which the whitelist is determined.&nbsp=3B For example=
=2C in addition to techniques for manually maintaining the whitelist=2C the=
re have been some suggestions that would involve automatic determinations (=
e.g. only answering with AAAA RRs if the query comes in over IPv6).&nbsp=3B=
&nbsp=3B It might be useful to cover some of the proposals=2C since they mi=
ght have different implications.&nbsp=3B <br><br>Section 2.1<br><br>Is the =
term "IP address" here intended to include both IPv4 and IPv6 addresses? <b=
r><br>Section 3<br><br><pre>   At least one highly-trafficked domain has no=
ted that they have<br>   received requests to not send DNS responses with A=
AAA resource<br>   records to particular resolvers.  In this case=2C the op=
erators of<br>   those recursive resolvers have expressed a concern that th=
eir IPv6<br>   network infrastructure is not yet ready to handle the large =
traffic<br>   volume which may be associated with the hosts in their networ=
k<br>   connecting to the websites of these domains.  This concern is clear=
ly<br>   a temporary consideration relating to the deployment of IPv6 netwo=
rk<br>   infrastructure on the part of networks with end user hosts=2C rath=
er<br>   than a long-term concern.  These end user networks may also have<b=
r>   other tools at their disposal in order to address this concern=2C<br> =
  including applying rules to network equipment such as routers and<br>   f=
irewalls (this will necessarily vary by the type of network=2C as well<br> =
  as the technologies used and the design of a given network)=2C as well<br=
>   as configuration of their recursive resolvers (though modifying or<br> =
  suppressing AAAA resource records in a DNSSEC-signed domain on a<br>   Se=
curity-Aware Resolver will be problematic Section 10.1).<br></pre><br>[BA]&=
nbsp=3B This paragraph seems to be distinguishing "blacklisting" from "whit=
elisting" as well as describing some of the implications of attempting to s=
uppress AAAA RRs in the recursive resolver.&nbsp=3B It might be worthwhile =
to introduce the distinction between "blacklisting" and "whitelisting" earl=
ier on.&nbsp=3B Such a section might also include the following paragraph f=
rom Section 7.3.7:<br><br><pre>   It is unclear when and if it would be app=
ropriate to change from<br>   whitelisting to blacklisting=2C and whether o=
r how this could feasibly<br>   be coordinated across the Internet=2C which=
 may be proposed or<br>   implemented on an ad hoc basis when a majority of=
 networks (or<br>   allocated IPv6 address blocks) have been whitelisted.  =
Finally=2C some<br>   parties implementing DNS whitelisting consider this t=
o be a temporary<br>   measure.  As such=2C it is not clear how these parti=
es will judge the<br>   network conditions to have changed sufficiently to =
justify disabling<br>   DNS whitelisting and/or what the process and timing=
 will be in order<br>   to discontinue this practice.<br></pre><br>Section =
4<br><br><pre>   While in Section 1 the level of IPv6-related impairment ha=
s been<br>   estimated to be as high as 0.078% of Internet users=2C which i=
s a<br>   primary motivation cited for the practice of DNS whitelisting=2C =
it is<br>   not clear if the level of IPv4-related impairment is more or le=
ss<br>   that this percentage (which in any case is likely to have declined=
<br>   since its original citation).  Indeed=2C as at least one document<br=
>   reviewer has pointed out=2C it may simply be that websites are only<br>=
   measuring IPv6 impairments and not IPv4 impairments=2C whether because<b=
r>   IPv6 is new or whether those websites are simply unable to or are<br> =
  otherwise not in a position to be able to measure IPv4 impairment<br>   (=
since this could result in no Internet access whatsoever).  As a<br>   resu=
lt=2C it is worth considering that IPv4-related impairment could<br>   exce=
ed that of IPv6-related impairment and that such IPv4-related<br>   impairm=
ent may have simply been accepted as "background noise" on the<br>   Intern=
et for a variety of reasons.  Of course=2C this comparison of the<br>   lev=
el of worldwide IPv6 impairments to IPv4 impairments is<br>   speculation=
=2C as the author is not aware of any good measurement of<br>   IPv4-relate=
d impairments which are comparable in nature to the IPv6-<br>   related imp=
airment measurements which have recently been conducted<br>   around the wo=
rld.<br><br>[BA] It seems to me that discussion of measurement issues shoul=
d probably come earlier in the document=2C possibly in its own section.  <b=
r>My suggestion is to move this paragraph as well other paragraphs referrin=
g to measurement into its own section (Section 1.1?). <br>The following par=
agraph from Section 3.2 might be a candidate:<br><br>   Finally=2C some dom=
ains=2C have run IPv6 experiments whereby they added<br>   AAAA resource re=
cords and observed and measured errors [Heise Online<br>   Experiment]=2C w=
hich should be important reading for any domain<br>   contemplating either =
the use of DNS whitelisting or simply adding<br>   IPv6 addressing to their=
 site.<br><br></pre>Section 6<br><br>This section talks about Adhoc versus =
universal deployment scenarios.&nbsp=3B It strikes me that the underlying d=
istinction is not so much the universality of whitelisting deployment as mu=
ch as whether the whitelists are shared or independent. The document seems =
to argue that independence is the most likely outcome:<br><br><pre>   It is=
 probably unlikely that a single clearinghouse for<br>   managing whitelist=
ing is possible=3B it will more likely be unique to<br>   the source conten=
t owners and/or domains which implement DNS<br>   whitelists.</pre>
<br>[BA] While a single clearinghouse might be unlikely=2C I'm not sure tha=
t this necessarily argues against the likelihood of multiple clearinghouses=
.&nbsp=3B It might be helpful to provide a little more detail on the motiva=
tion behind the views on the likelihood of clearinghouses emerging (e.g. is=
 this based on discussions with content providers?).&nbsp=3B For example=2C=
 if the concept of IPv6 whitelisting becomes more widespread among smaller =
content providers=2C it would seem that the need for clearinghouses might e=
merge.<br><br>Section 7.3.3<br><br>It seems to me that there might be some =
operational implications that might arise from some potential whitelisting =
mechanisms such as differentiating DNS queries sent over IPv6 versus IPv4.&=
nbsp=3B <br><br>Section 7.6<br><br><pre>   At the same time=2C as noted in =
Section 3=2C some highly-trafficked<br>   domains may find the prospect of =
transitioning to IPv6 daunting<br>   without having some short-term ability=
 to incrementally control the<br>   amount and source of IPv6 traffic to th=
eir domains.<br><br>[BA] The issue of traffic control is a distinct problem=
. This is partially discussed in Section 3 (from the point of view of the r=
ecursive resolver owner)=2C<br>but here it is referring to the problem as e=
xperienced by the content owner.  Perhaps it would make sense to make the d=
istinction between the <br>"impairment" and "traffic control" problems earl=
ier? (maybe even in Section 1=2C referring to a subsequent discussion in Se=
ction 3). <br><br></pre>Section 8.3.1<br><br>This section refers to fixes f=
or the "impairment" problem=2C but as noted above=2C there may also be othe=
r potential motivations for whitelisting. <br><br>Section 9<br><br><pre>   =
World IPv6 Day=2C sponsored by the Internet Society [World IPv6 Day]=2C<br>=
   is scheduled to occur on June 8=2C 2011.  This will be an opportunity<br=
>   for domains to add AAAA resource records to the DNS without using DNS<b=
r>   whitelisting.  As a result=2C this is likely an excellent opportunity<=
br>   for domains to evaluate the utility or necessity of DNS whitelisting=
=2C<br>   even in the short-term.  A major German news website=2C Heise Onl=
ine=2C<br>   also ran a similar IPv6 experiment whereby they added AAAA res=
ource<br>   records and observed and measured any errors [Heise Online<br> =
  Experiment]=2C which is important reading for any domain contemplating<br=
>   either the use of DNS whitelisting or simply adding IPv6 addressing<br>=
   to their site.<br><br>[BA] You might consider moving this paragraph into=
 a separate "measurement" section (e.g. Section 1.1). <br><br></pre>=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<br>From: The IESG &l=
t=3Biesg-secretary@ietf.org&gt=3B&nbsp=3B<br>
To: IETF-Announce &lt=3Bietf-announce@ietf.org&gt=3B&nbsp=3B<br>
Reply-to: iesg-secretary@ietf.org&nbsp=3B<br>
Subject: Last Call:=20
&lt=3Bdraft-ietf-v6ops-v6-aaaa-whitelisting-implications-03.txt&gt=3B (IPv6=
=20
AAAA DNS Whitelisting Implications) to Informational RFC&nbsp=3B<br>
X-RSN: 1/0/934/8529/9220&nbsp=3B<br>
&nbsp=3B<br>
The IESG has received a request from the IPv6 Operations WG (v6ops) to&nbsp=
=3B<br>
consider the following document:&nbsp=3B<br>
- 'IPv6 AAAA DNS Whitelisting Implications'&nbsp=3B<br>
  &lt=3Bdraft-ietf-v6ops-v6-aaaa-whitelisting-implications-03.txt&gt=3B as =
an&nbsp=3B<br>
Informational RFC&nbsp=3B<br>
&nbsp=3B<br>
The IESG plans to make a decision in the next few weeks=2C and solicits&nbs=
p=3B<br>
final comments on this action. Please send substantive comments to the&nbsp=
=3B<br>
ietf@ietf.org mailing lists by 2011-04-29. Exceptionally=2C comments may be=
&nbsp=3B<br>
sent to iesg@ietf.org instead. In either case=2C please retain the&nbsp=3B<=
br>
beginning of the Subject line to allow automated sorting.&nbsp=3B<br>
&nbsp=3B<br>
The file can be obtained via&nbsp=3B<br>
http://datatracker.ietf.org/doc/draft-ietf-v6ops-v6-aaaa-whitelisting-impli=
cations/&nbsp=3B<br>
&nbsp=3B<br>
IESG discussion can be tracked via&nbsp=3B<br>
http://datatracker.ietf.org/doc/draft-ietf-v6ops-v6-aaaa-whitelisting-impli=
cations/&nbsp=3B<br>
&nbsp=3B<br>
&nbsp=3B<br>
&nbsp=3B<br>
No IPR declarations have been submitted directly on this I-D.&nbsp=3B<br>
_______________________________________________&nbsp=3B<br>
IETF-Announce mailing list&nbsp=3B<br>
IETF-Announce@ietf.org&nbsp=3B<br>
https://www.ietf.org/mailman/listinfo/ietf-announce&nbsp=3B<br>&nbsp=3B
<br> 		 	   		  </body>
</html>=

--_14f509f2-7499-4473-ada3-3d431548c954_--

From bob.hinden@gmail.com  Mon Apr 18 14:25:36 2011
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 07C15E06F5 for <ietf@ietfc.amsl.com>; Mon, 18 Apr 2011 14:25:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.516
X-Spam-Level: 
X-Spam-Status: No, score=-103.516 tagged_above=-999 required=5 tests=[AWL=0.083, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZmA2c0PybP2l for <ietf@ietfc.amsl.com>; Mon, 18 Apr 2011 14:25:35 -0700 (PDT)
Received: from mail-px0-f182.google.com (mail-px0-f182.google.com [209.85.212.182]) by ietfc.amsl.com (Postfix) with ESMTP id 14946E06E1 for <ietf@ietf.org>; Mon, 18 Apr 2011 14:25:31 -0700 (PDT)
Received: by pxi20 with SMTP id 20so3589331pxi.27 for <ietf@ietf.org>; Mon, 18 Apr 2011 14:25:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=5WuGJy8FmVC1zvfS7Zv9EEA9r0BlhAAXPQf+BAZtDw4=; b=O8cH+A1i513TlsP1zYN/ybevT68SJnsCdf/INvDaqe5f1Vx3o8MHho+by+/4e084mg uZis4NoF2EWWHJmM7ikq++ndzvabUOjLboeGwgihxGQSW2Eyz7RZWJDqSjTjWFJTUGy2 AmcdVJ83RpUu/ki/+YlgxsxW2kFtD06v5t9jc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=H5A1aTaKecAghIumlvF1tsmKbQzJQ2/OLA2/j+RJvJFedEMZ4k0cRRq5KBZ2w7h2yP GkDFl0zFxCoUV+W2VBOxDutfUB0PhpHGKELfhXxxZlTaBBKGWzGrh22C+4YKjhcI/4pt xBehr5cEBWgxthPy8pN4QM6ZiI04Uwy6iN268=
Received: by 10.68.29.230 with SMTP id n6mr7853851pbh.130.1303161931415; Mon, 18 Apr 2011 14:25:31 -0700 (PDT)
Received: from [172.16.224.217] ([209.97.127.34]) by mx.google.com with ESMTPS id i9sm2527909pbd.38.2011.04.18.14.25.30 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 18 Apr 2011 14:25:30 -0700 (PDT)
Subject: Re: IAOC: delegating ex-officio responsibility
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: <4DA8685F.5050504@dcrocker.net>
Date: Mon, 18 Apr 2011 14:25:27 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <D0674791-3D7C-4B90-8189-A895715B977A@gmail.com>
References: <2BE582FA-2682-4232-9D83-23A03F01A0DB@NLnetLabs.nl>	<6.2.5.6.2.20110330073936.0e1899d0@resistor.net>	<E2E41FDE-3818-4513-9933-CB1E0326B43E@nlnetlabs.nl>	<6.2.5.6.2.20110330113947.0c948bc0@resistor.net>	<4D942843.4060804@gmail.com>	<6.2.5.6.2.20110331120351.09488990@resistor.net>	<4D955661.8050502@gmail.com>	<9C81C0F6-3ABE-4479-8C5E-C20C486D052A@gmail.com>	<82A347CC-BB19-4A73-8E8A-924FBAA92A5F@NLnetLabs.nl>	<84D6568B-18C9-47B2-A457-C51C2FB3351F@gmail.com>	<5419FA805EF52E79D7822966@PST.JCK.COM> <DAC0FFD9-9B3B-4726-B56B-5E9BE5A5F1D1@gmail.com> <4DA8685F.5050504@dcrocker.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.1084)
Cc: Bob Hinden <bob.hinden@gmail.com>, 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: Mon, 18 Apr 2011 21:25:36 -0000

Dave,

> On 4/14/2011 9:51 AM, Bob Hinden wrote:
>> My concern is that this proposed change would likely make the IAOC =
work
>> worse.   That is, I think it would have a negative impact on the =
operations of
> > the IETF and that is why I am concerned.
>=20
> Bob,
>=20
> That is a concrete and basic assertion.  Please put some flesh on its =
bones so that the basis for your view can be understood better.
>=20
> The implication is that the people sitting in the positions of IAB =
Chair and IETF Chair are essential to the good operation of the =
IAOC/Trust.  Someone else from their groups or even someone else that =
they appoint from outside cannot perform the task of IAOC/Trust member =
adequately.

I didn't say no one else could do the job adequately.  I said "would =
have a negative impact" on the operations of the IETF. =20

Some examples where an I* chair had a significant influence on a =
decision that IAOC made include:

 - The hiring of the Transitional RSE
 - Many of the Beijing meeting issues (prior and post signing the MOU)
 - Specific venue selections (in one case avoiding a less than ideal =
venue)
 - The need for transparency in certain IAOC actions (day passes, venue =
rotation)
 - Discussion of what policy decisions that the IAOC can make vs. the =
IESG vs. community
 - Discussion about when to get community feedback
 - Secretariat contract (RFP, bidders review, selection, etc.)
 - RFC Publisher and Publisher contracts  (RFP, bidders review, =
selection, etc.)

Some of these decision might have been different without one or more I* =
chairs being directly involved in the decision.  Please review the =
minutes for more detail.

If I generalize this, I would say that the I* chairs have been actively =
involved in the most significant decisions the IAOC makes, they tend to =
be less active in many of the day to day operational issues.  For =
example, there are weekly calls in the months before an IETF meeting =
that the host, NOC team, IAD, and a few other people attend.  I don't =
think an I* chair has every been involved at this level.

I think the I* chairs, in my view bring a broad view of the community =
and operational needs based on what's involved in doing their jobs than =
another person would not have. =20

>=20
> Why?
>=20
> What are the specific contributions (insights and skills) that these =
roles regularly perform, in the conduct of the IAOC/Trust that cannot be =
performed adequately by others?

I think it because the role has the individual doing the job getting =
involved in the many related activities that gives them more insight =
than someone else, even a member of the same group.  To cite an example, =
I was on the IAB in the past, but I wouldn't claim to have the same =
total understanding of the IAB (and the things the IAB is responsible =
for) as the IAB chair at the time.  It's not the skill per se, it's =
being involved in the all of the topics that the chair is naturally =
involved in. =20

>=20
> d/
>=20
> ps. Reminder: I've just joined the IAOC/Trust, which means I've =
attended a few meetings and seen some operation.  As always, my comments =
have nothing to do with the individuals; this is about organizational =
design.

My concern is as you say about the "organizational design", not the =
current set of individuals.  I want to make sure this keeps working well =
with the next set of leaders and the set after that.

Bob




From housley@vigilsec.com  Mon Apr 18 15:21:38 2011
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id E31AEE067C for <ietf@ietfc.amsl.com>; Mon, 18 Apr 2011 15:21:38 -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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u1O5qq0GjO0t for <ietf@ietfc.amsl.com>; Mon, 18 Apr 2011 15:21:37 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfc.amsl.com (Postfix) with ESMTP id ED062E066F for <ietf@ietf.org>; Mon, 18 Apr 2011 15:21:36 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 9C6FCF2402E; Mon, 18 Apr 2011 18:21:40 -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 5Ws+vjz0QK4g; Mon, 18 Apr 2011 18:21:36 -0400 (EDT)
Received: from [192.168.2.101] (pool-71-178-218-117.washdc.fios.verizon.net [71.178.218.117]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 29BB2F240D4; Mon, 18 Apr 2011 18:21:40 -0400 (EDT)
Subject: Re: draft-housley-two-maturity-levels-05
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <4DAAA335.7080609@gmail.com>
Date: Mon, 18 Apr 2011 18:21:35 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <3246696A-BBAC-4562-8214-1A08403C1200@vigilsec.com>
References: <20110406152226.000AF3A6803@core3.amsl.com> <24582656-5993-46C3-B82A-883E8BA4E9A0@vigilsec.com> <4DAAA335.7080609@gmail.com>
To: Mykyta Yevstifeyev <evnikita2@gmail.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 Apr 2011 22:21:39 -0000

Mykyta:

>> 4. Downward References Permitted
> This section says nothing about references to documents with no status =
("pre-IETF" RFCs).  Maybe informative references to such RFCs should be =
allowed.  And what about normative ones?  Whether the RFC 3967 procedure =
will be used in such cases, or such references are disallowed in =
Standards Track docs?  I think this should also be mentioned in your =
draft.

What does this have to do with moving from two maturity levels?

Russ=

From sm@resistor.net  Mon Apr 18 17:13:45 2011
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 8FFF2E06EC for <ietf@ietfc.amsl.com>; Mon, 18 Apr 2011 17:13:45 -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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y4w291UZD7-k for <ietf@ietfc.amsl.com>; Mon, 18 Apr 2011 17:13:41 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfc.amsl.com (Postfix) with ESMTP id 02661E0692 for <ietf@ietf.org>; Mon, 18 Apr 2011 17:13:39 -0700 (PDT)
Received: from subman.resistor.net (IDENT:sm@localhost [127.0.0.1]) by mx.elandsys.com (8.14.4/8.14.5.Beta0) with ESMTP id p3J0DXiF024013 for <ietf@ietf.org>; Mon, 18 Apr 2011 17:13:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1303172018; bh=fC4Gy6uhMPRBG0/dEC5T51fqT+NExOYppdgWoSRQt6k=; h=Message-Id:X-Mailer:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type; b=tCefXTBJQ3K5pAOK7I76fQvYIh+S7YOGp3KGgYboRrV2mxwQbwEAmRYAjJ4epJ7yj v9z0kgPMOLHYw+gI6WHqdDUs0kCpTir00xQTyCXjKdRBnTSQm76mn1KSbPdoGDXFbG hvFM+1ksTMonXMvagOI8ppmdlmwhWbwsUZHR9IA8=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1303172018; bh=fC4Gy6uhMPRBG0/dEC5T51fqT+NExOYppdgWoSRQt6k=; h=Message-Id:X-Mailer:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type; b=qWRxQv8TRfzLRAUFCLBIxQCS7464Jsg9/Bam9vzW9ORWiy8xScAbP2D2FLAoCCoXR +3nZX1iKEi4G6U4EEwTYjM9uHkD7rP9uOLLWQSrzgiC4Jzh0ZIpkdVGj2i8gIfMz8X 4/ll+jKMRKNGcm4haDBM2xthtD4i0q4ice+0/jXs=
Message-Id: <6.2.5.6.2.20110418134230.05318b10@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 18 Apr 2011 16:58:44 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03.txt> (IPv6 AAAA DNS Whitelisting Implications) to Informational RFC
In-Reply-To: <20110415205113.13704.48681.idtracker@ietfc.amsl.com>
References: <20110415205113.13704.48681.idtracker@ietfc.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: Tue, 19 Apr 2011 00:13:45 -0000

At 13:51 15-04-2011, The IESG wrote:

>The IESG has received a request from the IPv6 Operations WG (v6ops) to
>consider the following document:
>- 'IPv6 AAAA DNS Whitelisting Implications'
>   <draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03.txt> as an
>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

 From Section 1:

   "The fraction of users with such impaired access has been estimated
    to be roughly 0.078% of total Internet users".

That's probably "web" users.

 From the Abstract:

   "The objective of this document is to describe what the whitelisting
    of DNS AAAA resource records is, hereafter referred to as DNS
    whitelisting, as well as the implications of this emerging practice
    and what alternatives may exist."

The only alternatives listed are a few paragraphs in Section 
8.3.  After reading the draft, it's hard to say whether the problem 
should be addressed at the network level, the DNS level or whether it 
is a chicken and egg problem.  The draft seems to aim to keep 
everyone happy by covering what different parties may view as issues.

Section 3 is about "What Problems Are Implementers Trying To 
Solve".  My naive view is that:

  1. Web browser tries to connect to web site over IPv6
  2. User has to wait for a timeout to get content over IPv4
  3. Content provider sees this as a business case against adopting IPv6

An alternative is to disable IPv6 in the web browser or have a popup 
message that says "IPv6 allows you to access more web sites.  Does 
your ISP support IPv6? Y/N".

Or the workaround can be done through DNS as documented in this 
draft.  It will be interesting to see what 8.8.8.8 will do.

In Section 6:

   "In either of these deployment scenarios, it is possible that
    reputable third parties could create and maintain DNS whitelists, in
    much the same way that blacklists are used for reducing email spam."

I suggest using DNSBLs instead of "blacklists".

As I do meet the religious requirements, I cannot take a position on 
this draft.

Regards,
-sm 


From amorris@amsl.com  Mon Apr 18 23:19:21 2011
Return-Path: <amorris@amsl.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 3DE80E06FD for <ietf@ietfc.amsl.com>; Mon, 18 Apr 2011 23:19:21 -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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q4keVuLwfwdX for <ietf@ietfc.amsl.com>; Mon, 18 Apr 2011 23:19:20 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [64.170.98.20]) by ietfc.amsl.com (Postfix) with ESMTP id 792BBE06F9 for <ietf@ietf.org>; Mon, 18 Apr 2011 23:19:20 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c1a.amsl.com (Postfix) with ESMTP id 3845AE08C3; Mon, 18 Apr 2011 23:19:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c1a.amsl.com ([127.0.0.1]) by localhost (c1a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lG95qngONdaY; Mon, 18 Apr 2011 23:19:20 -0700 (PDT)
Received: from [192.168.0.194] (c-76-102-55-37.hsd1.ca.comcast.net [76.102.55.37]) by c1a.amsl.com (Postfix) with ESMTPSA id 041D1E08A1; Mon, 18 Apr 2011 23:19:19 -0700 (PDT)
Message-Id: <383ECAF1-8D1A-466E-997C-D07BE9E5907D@amsl.com>
From: Alexa Morris <amorris@amsl.com>
To: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <4DABE255.3080209@bogus.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Subject: Re: audio streaming archive...
Date: Mon, 18 Apr 2011 23:19:18 -0700
References: <201104140254.p3E2sMjk014471@fs4113.wdf.sap.corp>	<4DA67EF0.4050209@bogus.com> <20110415032222.GB22852@odin.ulthar.us> <4DABE255.3080209@bogus.com>
X-Mailer: Apple Mail (2.936)
Cc: i.grok@comcast.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: Tue, 19 Apr 2011 06:19:21 -0000

VeriLAN is going to check this computer on Wednesday (it's currently  
located at a warehouse) to verify that all recordings were uploaded.  
We'll know more shortly.

Alexa

On Apr 18, 2011, at 12:03 AM, Joel Jaeggli wrote:

> On 4/14/11 8:22 PM, Scott Schmit wrote:
>> On Wed, Apr 13, 2011 at 09:58:24PM -0700, Joel Jaeggli wrote:
>>> there was a naming convention issue on the channel5 recorder which I
>>> thought that we caught all of those by I could be wrong...
>>>
>>> The contractor has the channel8 recorder and should be able  
>>> toretrive
>>> the file.
>>
>> Is there an ETA for the fix to that?
>
> you might want to talk to the secretariate or the contractor (whom I
> cced on the previous message) I don't have access to the equipment.
>
>> I listened to both the .mp3 and .mp3.1 file for wed-am ch8, and  
>> neither
>> sounds like the DANE session to me.
>>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>

-----------
Alexa Morris / Executive Director / IETF
48377 Fremont Blvd., Suite 117, Fremont, CA  94538
Phone: +1.510.492.4089 / Fax: +1.510.492.4001
Email: amorris@amsl.com

Managed by Association Management Solutions (AMS)
Forum Management, Meeting and Event Planning
www.amsl.com <http://www.amsl.com/>


From john@jck.com  Sat Apr 16 17:09:15 2011
Return-Path: <john@jck.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id A44BFE0763 for <ietf@ietfc.amsl.com>; Sat, 16 Apr 2011 17:09:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.166
X-Spam-Level: 
X-Spam-Status: No, score=-102.166 tagged_above=-999 required=5 tests=[AWL=0.433, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xE62Jjk2JjMk for <ietf@ietfc.amsl.com>; Sat, 16 Apr 2011 17:09:14 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfc.amsl.com (Postfix) with ESMTP id 667EAE066A for <ietf@ietf.org>; Sat, 16 Apr 2011 17:09:14 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QBFXv-000ErK-3M; Sat, 16 Apr 2011 20:08:59 -0400
Date: Sat, 16 Apr 2011 20:08:58 -0400
From: John C Klensin <john@jck.com>
To: Lucy Lynch <llynch@civil-tongue.net>, dcrocker@bbiw.net
Subject: Re: IAOC: delegating ex-officio responsibility
Message-ID: <ABEF0352D5DCE3BF80AFC232@PST.JCK.COM>
In-Reply-To: <alpine.BSF.2.00.1104160711480.14890@hiroshima.bogus.com>
References: <2BE582FA-2682-4232-9D83-23A03F01A0DB@NLnetLabs.nl> <6.2.5.6.2.20110330073936.0e1899d0@resistor.net> <E2E41FDE-3818-4513-9933-CB1E0326B43E@nlnetlabs.nl> <6.2.5.6.2.20110330113947.0c948bc0@resistor.net> <4D942843.4060804@gmail.com> <6.2.5.6.2.20110331120351.09488990@resistor.net> <4D955661.8050502@gmail.com> <9C81C0F6-3ABE-4479-8C5E-C20C486D052A@gmail.com> <82A347CC-BB19-4A73-8E8A-924FBAA92A5F@NLnetLabs.nl> <84D6568B-18C9-47B2-A457-C51C2FB3351F@gmail.com> <5419FA805EF52E79D7822966@PST.JCK.COM> <DAC0FFD9-9B3B-4726-B56B-5E9BE5A5F1D1@gmail.com> <4DA8685F.5050504@dcrocker.net> <alpine.BSF.2.00.1104160711480.14890@hiroshima.bogus.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-Mailman-Approved-At: Tue, 19 Apr 2011 07:28:40 -0700
Cc: Bob Hinden <bob.hinden@gmail.com>, 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, 17 Apr 2011 00:09:15 -0000

--On Saturday, April 16, 2011 07:51 -0700 Lucy Lynch
<llynch@civil-tongue.net> wrote:

>> The implication is that the people sitting in the positions
>> of IAB Chair and  IETF Chair are essential to the good
>> operation of the IAOC/Trust.  Someone  else from their groups
>> or even someone else that they appoint from outside  cannot
>> perform the task of IAOC/Trust member adequately.
> 
> I think this is the wrong question. I don't think this is
> about the
> people who sit on the IAOC or the Trust, it is about the
> roles. Their
> participation is part of the chain of accountability to the
> community.
> The IAOC was crafted to include both the IAB and IETF Chairs
> as well
> as the ISOC CEO in their respective roles and not as Fred,
> Harold, and
> Lynn (as members of the IETF community).
> 
>> Why?
>> 
>> What are the specific contributions (insights and skills)
>> that these roles  regularly perform, in the conduct of the
>> IAOC/Trust that cannot be performed  adequately by others?
> 
> see above.
> 
> One more point here: as a former Chair of the IAOC (IAB
> appointed
> member from the community) I'm sympathetic the the overload
> arguments
> but I'll note that absent the IAB/IETF chairs the work of the
> IAOC
> chair and the weight put on that role may increase in
> unexpected ways.
> 
> I agree with many of the points that Bob, Brian, Leslie, and
> Jari
> have made in earlier posts and think that we need to take a
> broader
> view of the problems we're trying to solve here. Role overload
> is
> an on-going problem but I'm not sure we solve this by moving
> the
> administrative accountability we gained through BCP 101 to
> additional volunteers.

At the risk of agreeing violently with Dave, I think the series
of comments above, and referenced above, are missing something.
None of this familiy of "delegation" or "someone else" proposals
requires that the IAB or IESG Chairs not serve on the IAOC.  If
they think that is sensible and they have the time, they are
free to do that.  We might even strongly encourage it.  However,
if those people conclude that limited available time is better
spent in other ways or that, if they take the IAOC position,
they would not be able to devote adequate attention to it,
aren't we better off giving them the flexibility and discretion
to make that decision?  Similarly, if someone tells the
appointing body "I have the time and resources to take on the
IAB Chair or IETF Chair position but only if that position does
not include the responsibility of sitting on the IAOC" isn't it
better to give those bodies the option of considering that
person rather than limiting the choices to those who can sign up
for all of the job?

At least from my perspective, broadening the flexibility
available to already-appointed IAB and IETF Chairs and to the
bodies that appoint them is the real issue here.  _Requiring_
that they serve on the IAOC does not create more time or
resources, it just limits the range of people who can take those
positions or, more likely, raises the odds of getting someone
onto the IAOC who won't be able to pay full (or even adequate)
attention.

So. in addition to the questions Dave posed, the question I
would address to you and Bob is whether, given a hypothetical
choice of someone sitting on the IAOC ex-officio but not being
able to really pay attention because he or she concludes that
there are more pressing priorities and having someone
representing the IAB or IESG who really can pay attention, which
one you would pick.  In the worst case, if you prefer to have
the Chairs nominally present but not paying complete attention,
then keep insisting that they are the only ones who can possibly
occupy the IAOC slot.  

As part of that, figure out how you are going to convince the
Nomcom and the IAB that selecting people for the Chair roles
should have "will give IAOC first priority regardless of their
judgment about the importance of other aspects of their roles"
as an absolute criterion and/or how you are going to convince
the community to recall anyone in the Chair roles who does not
give the IAOC that priority.    

best,
  john


From slawomir.testowy@gmail.com  Sun Apr 17 23:32:06 2011
Return-Path: <slawomir.testowy@gmail.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id DD482E0758; Sun, 17 Apr 2011 23:32:06 -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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2rqNUcX6xbH9; Sun, 17 Apr 2011 23:32:02 -0700 (PDT)
Received: from mail-px0-f182.google.com (mail-px0-f182.google.com [209.85.212.182]) by ietfc.amsl.com (Postfix) with ESMTP id 9C6FEE05F5; Sun, 17 Apr 2011 23:32:02 -0700 (PDT)
Received: by pxi20 with SMTP id 20so3037819pxi.27 for <multiple recipients>; Sun, 17 Apr 2011 23:32:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=yVFcRCtHvoCUG8ZATAM+kedCXD0+MVBd9Sa7t+QAEZ4=; b=pTTF+Jv0Jp3A1KzTRGLHkStR/cDqddTW+iESVIs87TFrXby6ImL6kSf9EtGQ4uJDVa jkSXFAphR5yXwdIvSXKKWIBKPc8wpusgvbVRA4XvCOKItTpvrDwEKkn+FDYduC0/tb2o HoLFXgQ+PlNY10XAP4HZX2bn+HoS4rgACX/6o=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=ELergUC2CwNhn0v6NT9N6IEYohQWBR4jyZ80uOB6Yjdwwg4xDj23KUaeNmfikbqmB1 l25DdpCz2MHFZLnsp8t1hZi8cTLTsz+Lo2e25124dZAMOfw9iQRY+IarnG+jZ9kJxxfq WJwkLp4luNjgn8EVm4ITHJrnJxIcGktEvPpHw=
MIME-Version: 1.0
Received: by 10.142.214.16 with SMTP id m16mr2501139wfg.218.1303108320014; Sun, 17 Apr 2011 23:32:00 -0700 (PDT)
Received: by 10.142.217.5 with HTTP; Sun, 17 Apr 2011 23:31:59 -0700 (PDT)
In-Reply-To: <20110316191330.15705.6182.idtracker@localhost>
References: <20110316191330.15705.6182.idtracker@localhost>
Date: Mon, 18 Apr 2011 08:31:59 +0200
Message-ID: <BANLkTi=2ULwNxF85crvKMEHmPiyPQogeiw@mail.gmail.com>
Subject: Re: [Speechsc] Last Call: <draft-ietf-speechsc-mrcpv2-24.txt> (Media Resource Control Protocol Version 2 (MRCPv2)) to Proposed Standard
From: Slawomir Testowy <slawomir.testowy@gmail.com>
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Tue, 19 Apr 2011 07:29:02 -0700
Cc: speechsc@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 Apr 2011 06:32:07 -0000

Hello,

my small comment:

The BARGE-IN-OCCURRED method is in few places wrote as BARGE-IN-OCCURED
(note missing "R"). I wonder how this could go through all 24 MRCPv2
revisions....

Regards,
Slawek Testowy

2011/3/16 The IESG <iesg-secretary@ietf.org>:
>
> The IESG has received a request from the Speech Services Control WG
> (speechsc) to consider the following document:
> - 'Media Resource Control Protocol Version 2 (MRCPv2)'
> =A0<draft-ietf-speechsc-mrcpv2-24.txt> as a 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 2011-04-13. (This allows an additional two
> weeks for review since the document is large and the review period overla=
ps
> the Prague IETF meeting). 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.
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-speechsc-mrcpv2/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-speechsc-mrcpv2/
>
>
>
> No IPR declarations have been submitted directly on this I-D.
> _______________________________________________
> Speechsc mailing list
> Speechsc@ietf.org
> https://www.ietf.org/mailman/listinfo/speechsc
> Supplemental web site:
> &lt;http://www.standardstrack.com/ietf/speechsc&gt;
>

From slawomir.testowy@gmail.com  Mon Apr 18 00:11:00 2011
Return-Path: <slawomir.testowy@gmail.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 8C9BFE0769; Mon, 18 Apr 2011 00:11:00 -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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IwIvlp++rqT7; Mon, 18 Apr 2011 00:10:55 -0700 (PDT)
Received: from mail-pv0-f172.google.com (mail-pv0-f172.google.com [74.125.83.172]) by ietfc.amsl.com (Postfix) with ESMTP id 967B6E06C1; Mon, 18 Apr 2011 00:10:55 -0700 (PDT)
Received: by pvh1 with SMTP id 1so2688381pvh.31 for <multiple recipients>; Mon, 18 Apr 2011 00:10:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=xEm/aP+Q4OH4TvbG39/wYEN18UjHhJ6rtbtHyB8eqco=; b=i24bf+oCz4tvU6HZRukvHG2PIpFhSmbRk3NcACZgQOO46f7BMY3Uh235k3gk9gkOm6 AsVu50z7bSZMEkhDRo3Dxp/H2REkJiVMld9MDcmC4D7wyMR7lB6c/WQ5AldU9TSvl5Xr tG33uHbJnr7V/syoy1kGRaEMwxWEBWCXs1ICk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=kr2KqKI58F1i/gMEl0LVvjPENtTcZ0Xho75XJ/knvZUHJKAxgZAROaRfrEm00u+mYC uBwHMV1aoBvwOK+LO6CODJbgqgkNYJ6bMD9u87nb6srT9hInibolJHSFy0LSroz69y50 aMCRAvzHBuRGIWaK8cippwfY6NxGGrbInBi1w=
MIME-Version: 1.0
Received: by 10.142.234.18 with SMTP id g18mr2520404wfh.104.1303110653268; Mon, 18 Apr 2011 00:10:53 -0700 (PDT)
Received: by 10.142.217.5 with HTTP; Mon, 18 Apr 2011 00:10:53 -0700 (PDT)
In-Reply-To: <20110316191330.15705.6182.idtracker@localhost>
References: <20110316191330.15705.6182.idtracker@localhost>
Date: Mon, 18 Apr 2011 09:10:53 +0200
Message-ID: <BANLkTimxON1YJUTtS68BrRWweZRN2GW+6Q@mail.gmail.com>
Subject: Re: [Speechsc] Last Call: <draft-ietf-speechsc-mrcpv2-24.txt> (Media Resource Control Protocol Version 2 (MRCPv2)) to Proposed Standard
From: Slawomir Testowy <slawomir.testowy@gmail.com>
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Tue, 19 Apr 2011 07:29:15 -0700
Cc: speechsc@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 Apr 2011 07:11:00 -0000

Hi!

Some other comments:

> 4.2. Managing Resource Control Channels

> When the client wants to add a media processing resource to the
> session, it issues a SIP re-INVITE transaction.

Is it possible to allocate more than one resource of the same type
during one SIP dialog? Example in 4.2 shows how to allocate
synthesizer and recognizer, but does not specify if there may be e.g.
more than one synthesizer.



>6.2.9. Content-Encoding
>
>
>   The content-encoding entity-header is used as a modifier to the
>   media-type.  When present, its value indicates what additional
>   content encoding has been applied to the entity-body, and thus what
>   decoding mechanisms must be applied in order to obtain the media-type
>   referenced by the content-type header field.  Content-encoding is
>   primarily used to allow a document to be compressed without losing
>   the identity of its underlying media type.  Note that the SDP session
>   can be used to determine accepted encodings (see Section 7).  This
>   header field MAY occur on all messages.

Section 7 describes usage of OPTIONS method of SIP and Accept-Encoding
header is returned by SIP response, not SDP answer, so I guess "Note that
the SDP session can be used" should be changed to "Note that the SIP
session can be used".

>   When a CONTROL request to jump backward is issued to a currently
>  speaking synthesizer resource, and the target jump point is before
>   the start of the current "SPEAK" request, the current "SPEAK" request
>   MUST restart from the beginning of its speech data and the response
>   to the CONTROL request MUST contain this header field with a value of
>   "true" indicating a restart.

Why sometimes requests are surrounded by quotation marks (like "SPEAK")
and sometimes not (like CONTROL request)? This happens through all the
specification. This may be a minor nit, but makes the whole paper look like=
 a
"draft" :)

> 8.4.7. Prosody-Parameters

>  The prosody parameter headers in the "SET-PARAMS" or "SPEAK" request
>  only apply if the speech data is of type text/plain and does not use
>  a speech markup format.

Why is it so? Why it is not true for Voice-Parameters?
Is it true for CONTROL (i.e. current SPEAK must be text/plain)?

Specification does not say anything about it.

> 8.4.16. Load-Lexicon
>
>
>   This header field is used to indicate whether a lexicon has to be
>   loaded or unloaded.  The default value for this header field is
>   "true".  This header field MAY be specified in a DEFINE-LEXICON
>   method.

I propose rewording this paragraph to explicilty state that "true" means
"load lexicon" and "false" means "unload lexicon".



Thanks.
Slawek Testowy




2011/3/16 The IESG <iesg-secretary@ietf.org>:
>
> The IESG has received a request from the Speech Services Control WG
> (speechsc) to consider the following document:
> - 'Media Resource Control Protocol Version 2 (MRCPv2)'
> =A0<draft-ietf-speechsc-mrcpv2-24.txt> as a 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 2011-04-13. (This allows an additional two
> weeks for review since the document is large and the review period overla=
ps
> the Prague IETF meeting). 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.
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-speechsc-mrcpv2/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-speechsc-mrcpv2/
>
>
>
> No IPR declarations have been submitted directly on this I-D.
> _______________________________________________
> Speechsc mailing list
> Speechsc@ietf.org
> https://www.ietf.org/mailman/listinfo/speechsc
> Supplemental web site:
> &lt;http://www.standardstrack.com/ietf/speechsc&gt;
>

From evnikita2@gmail.com  Tue Apr 19 07:42:08 2011
Return-Path: <evnikita2@gmail.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 232C2E06E9 for <ietf@ietfc.amsl.com>; Tue, 19 Apr 2011 07:42: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=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SooRlFpb38Ev for <ietf@ietfc.amsl.com>; Tue, 19 Apr 2011 07:42:07 -0700 (PDT)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by ietfc.amsl.com (Postfix) with ESMTP id 67095E06E6 for <ietf@ietf.org>; Tue, 19 Apr 2011 07:42:07 -0700 (PDT)
Received: by bwz13 with SMTP id 13so5504110bwz.31 for <ietf@ietf.org>; Tue, 19 Apr 2011 07:42:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=XTrG8DZDHpQ5AesciJw3xf6nG7C15z1YGIKQJ71WJeE=; b=w3KdNzDITIwJ9S8eKHHkRasKYn5T/+/gcGfH0x9Pjutcg18ZUobCLn0fmOw7WQbHuF xiolh9AxS1ysvcTGBW5gUu8Xz18OOr2thWPrGnk30yRJwkD5YOuMehF34hFx22rAUaAK kRzVTP8IGOcGFNE52DyyCiIISlVEpFKRI0LtE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=jdgCIWLDOqmxV7tAX9ATeUZBUFfwP+gE4TxbtK5jswROWCsogkwVADGF7SjK65GD08 5uNQkKSsG2lTj2qDK87qfT2L5Rb4IGXsPsJba9fARXXonHPipfGniTgzzlBz+9t/a8GV QSdIW3EDk12AwnrGG+SRslc+0P4wFX2t2XmW8=
Received: by 10.204.85.8 with SMTP id m8mr3370609bkl.139.1303224126573; Tue, 19 Apr 2011 07:42:06 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id v21sm3879433bkt.11.2011.04.19.07.42.04 (version=SSLv3 cipher=OTHER); Tue, 19 Apr 2011 07:42:05 -0700 (PDT)
Message-ID: <4DAD9F65.6000908@gmail.com>
Date: Tue, 19 Apr 2011 17:42:45 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
Subject: Re: draft-housley-two-maturity-levels-05
References: <20110406152226.000AF3A6803@core3.amsl.com> <24582656-5993-46C3-B82A-883E8BA4E9A0@vigilsec.com> <4DAAA335.7080609@gmail.com> <3246696A-BBAC-4562-8214-1A08403C1200@vigilsec.com>
In-Reply-To: <3246696A-BBAC-4562-8214-1A08403C1200@vigilsec.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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, 19 Apr 2011 14:42:08 -0000

19.04.2011 1:21, Russ Housley wrote:
> Mykyta:
>
>>> 4. Downward References Permitted
>> This section says nothing about references to documents with no status ("pre-IETF" RFCs).  Maybe informative references to such RFCs should be allowed.  And what about normative ones?  Whether the RFC 3967 procedure will be used in such cases, or such references are disallowed in Standards Track docs?  I think this should also be mentioned in your draft.
> What does this have to do with moving from two maturity levels?
Mostly nothing, but if you consider that the whole Section 4 is 
appropriate for your document, what I propose is appropriate also.

Mykyta
> Russ


From housley@vigilsec.com  Tue Apr 19 08:57:26 2011
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id BF554E0777 for <ietf@ietfc.amsl.com>; Tue, 19 Apr 2011 08:57:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.569
X-Spam-Level: 
X-Spam-Status: No, score=-102.569 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uBRUqxX6ALWh for <ietf@ietfc.amsl.com>; Tue, 19 Apr 2011 08:57:26 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfc.amsl.com (Postfix) with ESMTP id 4256CE06BE for <ietf@ietf.org>; Tue, 19 Apr 2011 08:57:26 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 4D9D2F2407B; Tue, 19 Apr 2011 11:57:43 -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 Z6AvFmjcgwE0; Tue, 19 Apr 2011 11:57:23 -0400 (EDT)
Received: from [192.168.2.100] (pool-71-178-218-117.washdc.fios.verizon.net [71.178.218.117]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id CA635F2407A; Tue, 19 Apr 2011 11:57:42 -0400 (EDT)
Subject: Re: draft-housley-two-maturity-levels-05
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <4DAD9F65.6000908@gmail.com>
Date: Tue, 19 Apr 2011 11:57:24 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <BFABE881-C47F-4C25-8DD1-B13A67E0B3B7@vigilsec.com>
References: <20110406152226.000AF3A6803@core3.amsl.com> <24582656-5993-46C3-B82A-883E8BA4E9A0@vigilsec.com> <4DAAA335.7080609@gmail.com> <3246696A-BBAC-4562-8214-1A08403C1200@vigilsec.com> <4DAD9F65.6000908@gmail.com>
To: Mykyta Yevstifeyev <evnikita2@gmail.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: Tue, 19 Apr 2011 15:57:26 -0000

Mykyta:

>>>> 4. Downward References Permitted
>>> This section says nothing about references to documents with no =
status ("pre-IETF" RFCs).  Maybe informative references to such RFCs =
should be allowed.  And what about normative ones?  Whether the RFC 3967 =
procedure will be used in such cases, or such references are disallowed =
in Standards Track docs?  I think this should also be mentioned in your =
draft.
>> What does this have to do with moving from two maturity levels?
> Mostly nothing, but if you consider that the whole Section 4 is =
appropriate for your document, what I propose is appropriate also.

I just reviewed RFC 3967.  It does not seem to claim that references to =
those older documents requires special handling.  I'd like to leave this =
topic to an update to RFC 3967 if such an update is needed at all.

Russ=

From stpeter@stpeter.im  Tue Apr 19 09:03:31 2011
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 413CEE06B2 for <ietf@ietfc.amsl.com>; Tue, 19 Apr 2011 09:03:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.579
X-Spam-Level: 
X-Spam-Status: No, score=-102.579 tagged_above=-999 required=5 tests=[AWL=0.020, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QO0fHc3W6fH5 for <ietf@ietfc.amsl.com>; Tue, 19 Apr 2011 09:03:30 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by ietfc.amsl.com (Postfix) with ESMTP id 0EAF6E067F for <ietf@ietf.org>; Tue, 19 Apr 2011 09:03:30 -0700 (PDT)
Received: from dhcp-64-101-72-185.cisco.com (dhcp-64-101-72-185.cisco.com [64.101.72.185]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id BC7F340D6A; Tue, 19 Apr 2011 10:07:02 -0600 (MDT)
Message-ID: <4DADB250.3080407@stpeter.im>
Date: Tue, 19 Apr 2011 10:03:28 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
Subject: Re: draft-housley-two-maturity-levels-05
References: <20110406152226.000AF3A6803@core3.amsl.com>	<24582656-5993-46C3-B82A-883E8BA4E9A0@vigilsec.com>	<4DAAA335.7080609@gmail.com>	<3246696A-BBAC-4562-8214-1A08403C1200@vigilsec.com>	<4DAD9F65.6000908@gmail.com> <BFABE881-C47F-4C25-8DD1-B13A67E0B3B7@vigilsec.com>
In-Reply-To: <BFABE881-C47F-4C25-8DD1-B13A67E0B3B7@vigilsec.com>
X-Enigmail-Version: 1.1.1
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms010906090404000303080004"
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, 19 Apr 2011 16:03:31 -0000

This is a cryptographically signed message in MIME format.

--------------ms010906090404000303080004
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 4/19/11 9:57 AM, Russ Housley wrote:
> Mykyta:
>=20
>>>>> 4. Downward References Permitted
>>>> This section says nothing about references to documents with no stat=
us ("pre-IETF" RFCs).  Maybe informative references to such RFCs should b=
e allowed.  And what about normative ones?  Whether the RFC 3967 procedur=
e will be used in such cases, or such references are disallowed in Standa=
rds Track docs?  I think this should also be mentioned in your draft.
>>> What does this have to do with moving from two maturity levels?
>> Mostly nothing, but if you consider that the whole Section 4 is approp=
riate for your document, what I propose is appropriate also.
>=20
> I just reviewed RFC 3967.  It does not seem to claim that references to=
 those older documents requires special handling.  I'd like to leave this=
 topic to an update to RFC 3967 if such an update is needed at all.

+1. Let's keep this I-D short and focused.

Peter

--=20
Peter Saint-Andre
https://stpeter.im/




--------------ms010906090404000303080004
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIITzjCC
BjQwggQcoAMCAQICASMwDQYJKoZIhvcNAQELBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoT
DVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNp
Z25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3
MTAyNDIxMDMzM1oXDTE3MTAyNDIxMDMzM1owgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1T
dGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu
aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAzIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBALmjSW4SPiDKlAinvVeL
ZOVfItiuP1aRHL530E7QUc9icCwL33+PH+Js1HAh8CgWFl34sOxx1FJyS/C4VLPRsqDfP72j
tzCVUAL0DAxZ7wgzQvFz7x61jGxfhYhqYb1+PPOLkYBbkRIrPMg3dLEdKmXIYJYXDH+mB/V/
jLo73/Kb7h/rNoNg/oHHSv5Jolyvp5IY2btfcTBfW/telEFj5rDTX2juTvZ3Qhf3XQX5ca3Q
7A10zrUV/cWJOJ7F5RltbEIaboZmX5JBUb3FhUiAdBotehAX6DbDOuYoJtVxmGof6GuVGcPo
98K4TJf8FHo+UA9EOVDp/W7fCqKT4sXk/XkCAwEAAaOCAa0wggGpMA8GA1UdEwEB/wQFMAMB
Af8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBR7iZySlyShhEcCy3T8LvSs3DLl8zAfBgNV
HSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRaMFgwJwYIKwYBBQUH
MAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYhaHR0cDovL3d3
dy5zdGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6Ly93d3cu
c3RhcnRzc2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5jb20v
c2ZzY2EuY3JsMIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQELBQADggIBAGpd
SbdLFMhirxK37V4gE00+uW74UdAXtDgQI3AsRZWtaRtKHgAxFBSteqz4kDkeAjH/1b+K8tQR
6cxSI2nho7qOaPW/UpzOfSS/MeKK/9vfM2lfs+uItXH7LWtvS9wD1erfH1a+BXHCrCp4LA1l
fADDhRIiGTSS3i0Zu5xV3INNRHrCCCl6patltQ8RZTqzDMri7ombgIxjN51Zo7xV77EZcThV
0GA8iIN+7T53uHhUJpjfLIztHs/69OclRvHux9hCflfOm7GY5Sc4nqjfES+5XPArGGWiQSEk
ez37QfXqsxO3oCHK4b3DFZysG4uyOuC/WL80ab3muQ3tgwjBhq0D3JZN5kvu5gSuNZPa1WrV
hEgXkd6C7s5stqB6/htVpshG08jRz9DEutGM9oKQ1ncTivbfPNx7pILoHWvvT7N5i/puVoNu
bPUmLXh/2wA6wzAzuuoONiIL14Xpw6jLSnqpaLWElo2yTIFZ/CU/nCvvpW1Dj1457P3Ci9bD
0RPkWSR+CuucpgxrEmaw4UOLxflzuYYaq1RJwygOO5K0s2bAWOcXpgteyUOnQ3d/EjJAWRri
2v0ubiq+4H3KUOMlbznlPAY/1T8YyyJPM88+Ueahe/AW1zoUwZayNcTnuM7cq6yBV8Wr3GOI
LFXhtT0UVuJLChPMJKVKVsa7qNorlLkMMIIGxzCCBa+gAwIBAgICAIswDQYJKoZIhvcNAQEF
BQAwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJT
ZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBD
bGFzcyAzIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTAeFw0xMDEwMTQwMTM2MzRa
Fw0xMjEwMTQxMjAxMDdaMIHAMSAwHgYDVQQNExcyNzQ1ODEtOU5YMDRxeExEYjBvNDY5VDEL
MAkGA1UEBhMCVVMxETAPBgNVBAgTCENvbG9yYWRvMQ8wDQYDVQQHEwZEZW52ZXIxLDAqBgNV
BAsTI1N0YXJ0Q29tIFRydXN0ZWQgQ2VydGlmaWNhdGUgTWVtYmVyMRowGAYDVQQDExFQZXRl
ciBTYWludC1BbmRyZTEhMB8GCSqGSIb3DQEJARYSc3RwZXRlckBzdHBldGVyLmltMIIBIjAN
BgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAuERvnrkpQTx9wbJfgxbNKEYvt0IilecZRUM6
wrbCzIUPCocuYhaAJcQoqIyHaKybPQ7f+DIGIAolAa3dHnNdlsXP2smTft/ZNpj10PIG5bil
NAqLUYwmLJaEaqY7BMW8423U3blW43/luLJk/Pq4OsWcw7AK3LeVh1U/HOgqhin26N3h72X1
nbLEpZFrgcp8egmWtXLCbLBDMqUK3j6wjLldni79muzYEVqU0A5GqSeb8Wc4kIx8VI5yL24J
KzinG2iVRP5ZDEbOZETzBXJabUsV56XSxqPG9DK6ke+ybCiL/wKV1HFqdtFB1y25lfvHgOP2
gyEApBKEDNjgLmKyyQIDAQABo4IC+zCCAvcwCQYDVR0TBAIwADALBgNVHQ8EBAMCBLAwHQYD
VR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMB0GA1UdDgQWBBS2EW2iNB+g0EibKJLBdv8I
eLovVDAfBgNVHSMEGDAWgBR7iZySlyShhEcCy3T8LvSs3DLl8zAdBgNVHREEFjAUgRJzdHBl
dGVyQHN0cGV0ZXIuaW0wggFCBgNVHSAEggE5MIIBNTCCATEGCysGAQQBgbU3AQICMIIBIDAu
BggrBgEFBQcCARYiaHR0cDovL3d3dy5zdGFydHNzbC5jb20vcG9saWN5LnBkZjA0BggrBgEF
BQcCARYoaHR0cDovL3d3dy5zdGFydHNzbC5jb20vaW50ZXJtZWRpYXRlLnBkZjCBtwYIKwYB
BQUHAgIwgaowFBYNU3RhcnRDb20gTHRkLjADAgEBGoGRTGltaXRlZCBMaWFiaWxpdHksIHNl
ZSBzZWN0aW9uICpMZWdhbCBMaW1pdGF0aW9ucyogb2YgdGhlIFN0YXJ0Q29tIENlcnRpZmlj
YXRpb24gQXV0aG9yaXR5IFBvbGljeSBhdmFpbGFibGUgYXQgaHR0cDovL3d3dy5zdGFydHNz
bC5jb20vcG9saWN5LnBkZjBjBgNVHR8EXDBaMCugKaAnhiVodHRwOi8vd3d3LnN0YXJ0c3Ns
LmNvbS9jcnR1My1jcmwuY3JsMCugKaAnhiVodHRwOi8vY3JsLnN0YXJ0c3NsLmNvbS9jcnR1
My1jcmwuY3JsMIGOBggrBgEFBQcBAQSBgTB/MDkGCCsGAQUFBzABhi1odHRwOi8vb2NzcC5z
dGFydHNzbC5jb20vc3ViL2NsYXNzMy9jbGllbnQvY2EwQgYIKwYBBQUHMAKGNmh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2NlcnRzL3N1Yi5jbGFzczMuY2xpZW50LmNhLmNydDAjBgNVHRIE
HDAahhhodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS8wDQYJKoZIhvcNAQEFBQADggEBADVtbXJG
tKAr55xc/OUM546gXUybI72Bank0w739Mv+9BBNtq9rMEvCnLmSKhBi76c1mdXh6zXs8RQDo
6nR/aPabE3llF2T4z80smi9jfnl3y9dpu9TcgDoqDLZ7a2lBlW656XAAQzHjvLp2MC7/mxlg
PYH2axa+q40mAYM20GbNsAEGbWQT1IqIh0BcLLsgbaMJHbyG/57zd9JLyMX3Vry1L1fJRQr3
GeLxMV5RtxN+mBgxrwFz/cOc09COiFExlsHgekpB5O43gqsAU16MXypyoSt4MrSfKTMHIGx6
2RF/M6vqUlvhi28gk2ZUvQ/+OX5+gjcZyooEzAAn4RuOKNswggbHMIIFr6ADAgECAgIAizAN
BgkqhkiG9w0BAQUFADCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4x
KzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMT
L1N0YXJ0Q29tIENsYXNzIDMgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBMB4XDTEw
MTAxNDAxMzYzNFoXDTEyMTAxNDEyMDEwN1owgcAxIDAeBgNVBA0TFzI3NDU4MS05TlgwNHF4
TERiMG80NjlUMQswCQYDVQQGEwJVUzERMA8GA1UECBMIQ29sb3JhZG8xDzANBgNVBAcTBkRl
bnZlcjEsMCoGA1UECxMjU3RhcnRDb20gVHJ1c3RlZCBDZXJ0aWZpY2F0ZSBNZW1iZXIxGjAY
BgNVBAMTEVBldGVyIFNhaW50LUFuZHJlMSEwHwYJKoZIhvcNAQkBFhJzdHBldGVyQHN0cGV0
ZXIuaW0wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC4RG+euSlBPH3Bsl+DFs0o
Ri+3QiKV5xlFQzrCtsLMhQ8Khy5iFoAlxCiojIdorJs9Dt/4MgYgCiUBrd0ec12Wxc/ayZN+
39k2mPXQ8gbluKU0CotRjCYsloRqpjsExbzjbdTduVbjf+W4smT8+rg6xZzDsArct5WHVT8c
6CqGKfbo3eHvZfWdssSlkWuBynx6CZa1csJssEMypQrePrCMuV2eLv2a7NgRWpTQDkapJ5vx
ZziQjHxUjnIvbgkrOKcbaJVE/lkMRs5kRPMFclptSxXnpdLGo8b0MrqR77JsKIv/ApXUcWp2
0UHXLbmV+8eA4/aDIQCkEoQM2OAuYrLJAgMBAAGjggL7MIIC9zAJBgNVHRMEAjAAMAsGA1Ud
DwQEAwIEsDAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwHQYDVR0OBBYEFLYRbaI0
H6DQSJsoksF2/wh4ui9UMB8GA1UdIwQYMBaAFHuJnJKXJKGERwLLdPwu9KzcMuXzMB0GA1Ud
EQQWMBSBEnN0cGV0ZXJAc3RwZXRlci5pbTCCAUIGA1UdIASCATkwggE1MIIBMQYLKwYBBAGB
tTcBAgIwggEgMC4GCCsGAQUFBwIBFiJodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9wb2xpY3ku
cGRmMDQGCCsGAQUFBwIBFihodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9pbnRlcm1lZGlhdGUu
cGRmMIG3BggrBgEFBQcCAjCBqjAUFg1TdGFydENvbSBMdGQuMAMCAQEagZFMaW1pdGVkIExp
YWJpbGl0eSwgc2VlIHNlY3Rpb24gKkxlZ2FsIExpbWl0YXRpb25zKiBvZiB0aGUgU3RhcnRD
b20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgUG9saWN5IGF2YWlsYWJsZSBhdCBodHRwOi8v
d3d3LnN0YXJ0c3NsLmNvbS9wb2xpY3kucGRmMGMGA1UdHwRcMFowK6ApoCeGJWh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2NydHUzLWNybC5jcmwwK6ApoCeGJWh0dHA6Ly9jcmwuc3RhcnRz
c2wuY29tL2NydHUzLWNybC5jcmwwgY4GCCsGAQUFBwEBBIGBMH8wOQYIKwYBBQUHMAGGLWh0
dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9zdWIvY2xhc3MzL2NsaWVudC9jYTBCBggrBgEFBQcw
AoY2aHR0cDovL3d3dy5zdGFydHNzbC5jb20vY2VydHMvc3ViLmNsYXNzMy5jbGllbnQuY2Eu
Y3J0MCMGA1UdEgQcMBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tLzANBgkqhkiG9w0BAQUF
AAOCAQEANW1tcka0oCvnnFz85QznjqBdTJsjvYFqeTTDvf0y/70EE22r2swS8KcuZIqEGLvp
zWZ1eHrNezxFAOjqdH9o9psTeWUXZPjPzSyaL2N+eXfL12m71NyAOioMtntraUGVbrnpcABD
MeO8unYwLv+bGWA9gfZrFr6rjSYBgzbQZs2wAQZtZBPUioiHQFwsuyBtowkdvIb/nvN30kvI
xfdWvLUvV8lFCvcZ4vExXlG3E36YGDGvAXP9w5zT0I6IUTGWweB6SkHk7jeCqwBTXoxfKnKh
K3gytJ8pMwcgbHrZEX8zq+pSW+GLbyCTZlS9D/45fn6CNxnKigTMACfhG44o2zGCA80wggPJ
AgEBMIGTMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UE
CxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRD
b20gQ2xhc3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAgCLMAkGBSsOAwIa
BQCgggIOMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDQx
OTE2MDMyOFowIwYJKoZIhvcNAQkEMRYEFJCF6PdxZodl1DnId3J9teK598QiMF8GCSqGSIb3
DQEJDzFSMFAwCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggq
hkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBpAYJKwYBBAGCNxAEMYGWMIGT
MIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2Vj
dXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xh
c3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAgCLMIGmBgsqhkiG9w0BCRAC
CzGBlqCBkzCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNV
BAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMTL1N0YXJ0
Q29tIENsYXNzIDMgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBAgIAizANBgkqhkiG
9w0BAQEFAASCAQB6oxJmoyF2h5zqbj4K9OacpIdLkgMoipqEP1T7fXslHrKPqCoDeNBtxKkQ
fu0gM0nuchACia9q90nhEIJL1iKfgjOYQQai2Xv20f6I3ga/zR/216+MMb1tvwqYIUPL5v4z
+MnT3zb/B4l+nvP00guh2Z1PqiaC0soJVWsnqP3w43KO2suqpxZqvBY81QKkTcyQqjvZfFP5
r68Yv4nlqENBSyftAkhvjZRHsSwvHubMEyKMjGHbYw/Nbc3m1wC2/Af5+diCtSLrH9BFg4Q0
xmB2atgVjzXk0/MR76/tQa5TiN2XqEcyGjdrMy4snSXfIniuIlU00tVFrPTz+vqPC5BJAAAA
AAAA
--------------ms010906090404000303080004--

From wwwrun@ietfc.amsl.com  Tue Apr 19 09:09:53 2011
Return-Path: <wwwrun@ietfc.amsl.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfc.amsl.com
Received: by ietfc.amsl.com (Postfix, from userid 30) id 23591E07B1; Tue, 19 Apr 2011 09:09:53 -0700 (PDT)
From: IETF Administrative Director <iad@ietf.org>
To: IETF Announcement list <ietf-announce@ietf.org>
Subject: IETF 84 Venue 
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20110419160953.23591E07B1@ietfc.amsl.com>
Date: Tue, 19 Apr 2011 09:09:53 -0700 (PDT)
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: Tue, 19 Apr 2011 16:09:53 -0000

The IAOC is pleased to announce Vancouver,BC, Canada as the site for IETF
84 from July 29 to August 3, 2012.  This will be the IETF's fourth meeting
in Vancouver, the others being 18, 64 and 70.  

Google will be the the Host for this meeting.  Google most recently was
the host for IETF 73 in Minneapolis.  <www.google.com>  Thanks again
Google!

We want to thank our benefactors.  The IETF cannot support its technical
standards efforts, including the Secretariat and RFC Editor, without the
generous support of its hosts and sponsors.

Contact Drew Dvorshak at dvorshak@isoc.org if you are interested in being
a Sponsor for IETF 84, or a Host for a different meeting. 

Hope to see you in Quebec City at IETF 81in 95 days!

Ray Pelletier
IETF Administrative Director

From dhc2@dcrocker.net  Tue Apr 19 10:33:25 2011
Return-Path: <dhc2@dcrocker.net>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 30447E0768 for <ietf@ietfc.amsl.com>; Tue, 19 Apr 2011 10:33:25 -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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SJyqMuuIHatG for <ietf@ietfc.amsl.com>; Tue, 19 Apr 2011 10:33:24 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfc.amsl.com (Postfix) with ESMTP id ED54CE069C for <ietf@ietf.org>; Tue, 19 Apr 2011 10:33:23 -0700 (PDT)
Received: from [192.168.1.3] (adsl-67-127-56-68.dsl.pltn13.pacbell.net [67.127.56.68]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p3JHXF4B030012 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Tue, 19 Apr 2011 10:33:21 -0700
Message-ID: <4DADC758.2080906@dcrocker.net>
Date: Tue, 19 Apr 2011 10:33:12 -0700
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Bob Hinden <bob.hinden@gmail.com>
Subject: Re: IAOC: delegating ex-officio responsibility
References: <2BE582FA-2682-4232-9D83-23A03F01A0DB@NLnetLabs.nl>	<6.2.5.6.2.20110330073936.0e1899d0@resistor.net>	<E2E41FDE-3818-4513-9933-CB1E0326B43E@nlnetlabs.nl>	<6.2.5.6.2.20110330113947.0c948bc0@resistor.net>	<4D942843.4060804@gmail.com>	<6.2.5.6.2.20110331120351.09488990@resistor.net>	<4D955661.8050502@gmail.com>	<9C81C0F6-3ABE-4479-8C5E-C20C486D052A@gmail.com>	<82A347CC-BB19-4A73-8E8A-924FBAA92A5F@NLnetLabs.nl>	<84D6568B-18C9-47B2-A457-C51C2FB3351F@gmail.com>	<5419FA805EF52E79D7822966@PST.JCK.COM> <DAC0FFD9-9B3B-4726-B56B-5E9BE5A5F1D1@gmail.com> <4DA8685F.5050504@dcrocker.net> <D0674791-3D7C-4B90-8189-A895715B977A@gmail.com>
In-Reply-To: <D0674791-3D7C-4B90-8189-A895715B977A@gmail.com>
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]); Tue, 19 Apr 2011 10:33:21 -0700 (PDT)
Cc: IETF Discussion <ietf@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, 19 Apr 2011 17:33:25 -0000

Bob, et al,

On 4/18/2011 2:25 PM, Bob Hinden wrote:
> I didn't say no one else could do the job adequately.  I said "would have a
> negative impact" on the operations of the IETF.

Right. And my second sentence did go farther than I meant.

However rejecting an effort to change the current arrangement -- especially when 
it is initiated by a principal -- means that alternatives are not acceptable, 
which translates roughly to saying the alternatives will not produce adequate 
performance.  Otherwise it looks like a difference between 'adequate' and 
perhaps "perfect"?

There is a core reality, here, that the I* Chairs are overburdened. This is 
obvious from looking at the list of their duties and underscored by the source 
of the current initiative.  We can choose to defer doing anything, under the 
guise of taking a 'holistic' view or we can try to help with the specific burden 
that is the focus of the overburdened folk.  On the average, we do better with 
incremental change and this is the one before us now.


> If I generalize this, I would say that the I* chairs have been actively
> involved in the most significant decisions the IAOC makes, they tend to be
> less active in many of the day to day operational issues.
...
> I think the I* chairs, in my view bring a broad view of the community and
> operational needs based on what's involved in doing their jobs than another
> person would not have.

My own simplistic summary:  For some topics it is extremely helpful to have the 
broader knowledge and insight that can be provided by an I* chair. For many 
topics, this is not needed, but for some it makes a significant difference.

To that end, here's a very simple proposal that resolves the issue cleanly:

      1. ISOC, IAB and IESG each appoint one person currently.  Change this to 
be two each, the same as Nomcom.  Each year, they would appoint one person.

      2. Move the I* Chairs to be non-voting ex-officio participants, the same 
as the IETF Administrative Director.  They are welcome to participate or be 
explicitly invited to all IAOC/Trust activities.

This produces the continuity that is needed for the admin work, but also retains 
access to the expertise of the I* chairs.

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From jmh@joelhalpern.com  Tue Apr 19 10:50:16 2011
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 70F9CE0702; Tue, 19 Apr 2011 10:50:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.481
X-Spam-Level: 
X-Spam-Status: No, score=-102.481 tagged_above=-999 required=5 tests=[AWL=0.118, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LbFDumY++q16; Tue, 19 Apr 2011 10:50:15 -0700 (PDT)
Received: from hermes.out.tigertech.net (hermes.out.tigertech.net [74.114.88.72]) by ietfc.amsl.com (Postfix) with ESMTP id 1FC73E0685; Tue, 19 Apr 2011 10:50:15 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.tigertech.net (Postfix) with ESMTP id 71D6143002C; Tue, 19 Apr 2011 10:50:14 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hermes.tigertech.net
Received: from [10.10.10.101] (pool-71-161-50-206.clppva.btas.verizon.net [71.161.50.206]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by hermes.tigertech.net (Postfix) with ESMTPSA id 724A14300E5; Tue, 19 Apr 2011 10:50:12 -0700 (PDT)
Message-ID: <4DADCB52.1020309@joelhalpern.com>
Date: Tue, 19 Apr 2011 13:50:10 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.15) Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: iesg@ietf.org
Subject: Re: [paws] WG Review: Protocol to Access White Space database (paws)
References: <20110419165634.CD24CE07CF@ietfc.amsl.com>
In-Reply-To: <20110419165634.CD24CE07CF@ietfc.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: paws@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, 19 Apr 2011 17:50:16 -0000

I think this working group is a good idea.
My inclination would be to place it in the Applications area.  It looks 
like a nice application protocol to me.
There is a reasonable argument for placing it in RAI, as that is where 
the relevant GEOLOC work has been done up till now.

Yours,
Joel M. Halpern

On 4/19/2011 12:56 PM, IESG Secretary wrote:
> A new IETF working group has been proposed.  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@ietf.org) by Tuesday, April 26, 2011.
>
>
> Protocol to Access White Space database (paws)
> ------------------------------------------------
> Current Status: Proposed Working Group
> Last updated: 2011-04-14
>
> Chairs:
> TBD
>
> Area Directors:
> TBD
>
> Area Advisor:
> TBD
>
> Mailing lists:
> Address: paws@ietf.org
> To Subscribe: https://www.ietf.org/mailman/listinfo/paws
> Archive: http://www.ietf.org/mail-archive/web/paws/
>
> Description of Working Group:
>
> Governments around the world continue to search for new pieces of radio
> spectrum which can be used by the expanding wireless communications
> industry to provide more services in the usable spectrum. The concept
> of allowing secondary transmissions (licensed or unlicensed) in
> frequencies allocated to a primary user is a technique to "unlock"
> existing spectrum for new use. An obvious requirement is that these
> secondary transmissions do not interfere with the primary use of the
> spectrum. Often, in a given physical location, the primary user(s) may
> not be using the entire band allocated to them. The available spectrum
> for a secondary use would then depend on the location of the secondary
> user. The primary user may have a schedule when it uses the spectrum,
> which may be available for secondary use outside that schedule. The
> fundamental issue is how to determine for a specific location and
> specific time, if any of the primary spectrum is available for secondary
> use. One simple mechanism is to use a geospatial database that records
> protected contours for primary users, and require the secondary users to
> check the database prior to selecting what part of the spectrum they
> use. Such databases could be available on the Internet for query by
> users.
>
> In a typical implementation of geolocation and database to access TV
> white space, a radio is configured with, or has the capability to
> determine its location in latitude and longitude. At power-on, before
> the device can transmit or use any of the spectrum set aside for
> secondary use, the device must identify the relevant database to query,
> contact the database, provide its geolocation and receive in return a
> list of unoccupied or "white space" spectrum (for example, in a TV
> White space implementation, the list of available channels at that
> location). The device can then select one of the channels from the list
> and begin to transmit and receive on the selected channel. The device
> must query the database subsequently on a periodic basis for a list of
> unoccupied channels based on certain conditions, e.g. a fixed amount of
> time has passed or the device has changed location beyond a specified
> threshold.
>
> The databases are expected to be reachable via the Internet and the
> devices querying these databases are expected to have some form of
> Internet connectivity, directly or indirectly. The databases may be
> country specific since the available spectrum and regulations may vary,
> but the fundamental operation of the protocol should be country
> independent, thus extensibility of data structures will be required. The
> solution will not be tied to any specific spectrum, country, or
> phy/mac/air interface but may incorporate relevant aspects of these as
> needed for proper operation.
>
> The proposed working group will :
> - standardize a protocol for querying the database, which includes a
> location sensitive database discovery mechanism and security for the
> protocol, and application services.
> - Standardize the data structure to be carried by the query
> protocol.
>
> The protocol must protect both the channel enablement process and the
> privacy of users. Robust security mechanisms are required to prevent:
> device identity spoofing, modification of device requests, modification
> of channel enablement information, impersonation of registered database
> services and unauthorized disclosure of a users location.
>
> Existing IETF location data structures and privacy mechanisms may be
> considered for use. The WG will also investigate the need for other
> mechanisms and related protocols to the White Space DB.
>
> The Working Group will set up and maintain appropriate contact and
> liaison with other relevant standards bodies and groups, including IEEE
> 802.11af and IEEE 802.22 to begin with. The working group may also
> consider input from regulatory entities that are involved in the
> specification of the rules for secondary use of spectrum in specific
> bands.
>
> Goals and Milestones
>
> Sep 2011  Submit 'Requirements and Framework' to the IESG for
>            publication as Informational
>
> Apr 2012  Submit 'Protocol for Querying a Whitespace Database' to
>            the IESG for publication as Proposed Standard
>
> Apr 2012  Submit 'Data Model for Whitespace query protocol' to the
>            IESG for publication as Proposed Standard
> _______________________________________________
> paws mailing list
> paws@ietf.org
> https://www.ietf.org/mailman/listinfo/paws
>

From sm@resistor.net  Tue Apr 19 11:01:07 2011
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 9EF58E0814 for <ietf@ietfc.amsl.com>; Tue, 19 Apr 2011 11:01:07 -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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YdNSzQvGWddr for <ietf@ietfc.amsl.com>; Tue, 19 Apr 2011 11:01:06 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfc.amsl.com (Postfix) with ESMTP id 3D641E0702 for <ietf@ietf.org>; Tue, 19 Apr 2011 11:01:05 -0700 (PDT)
Received: from subman.resistor.net (IDENT:sm@localhost [127.0.0.1]) by mx.elandsys.com (8.14.4/8.14.5.Beta0) with ESMTP id p3JI0r6U022631;  Tue, 19 Apr 2011 11:00:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1303236061; bh=a6gDSxqdjT2VOUfbHGXv9JKvK02BTadi4nBC7lO26ko=; h=Message-Id:X-Mailer:Date:To:From:Subject:Cc:In-Reply-To: References:Mime-Version:Content-Type; b=FEyditfFnyiYVxFfB0Eklmw6wPbIUc3isRpPATNO5P2tOcVptTyHp6/ohDwjR5lru mnNX4+wXSKi91+e08ALba1SpWw6wJOdT/5tf0iwn6Fy89J/jXGtT/s2w1nQt36Av9g PWMi4FFKPhDg5OAiqmmSR/YaSG6BM+CrFeZTcras=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1303236061; bh=a6gDSxqdjT2VOUfbHGXv9JKvK02BTadi4nBC7lO26ko=; h=Message-Id:X-Mailer:Date:To:From:Subject:Cc:In-Reply-To: References:Mime-Version:Content-Type; b=gQRWAkfVZFhZH65XAaevO7sdTsUnjLtHfTzWsg4ZVShoZgpXKEQ1JD1NJrsxBS0QY XUWY4+/p+mL+5hnI8XP9QrsOnsXDnYrZP4xDw1WbwVR3Wdz3rNBSqxQX2cLfAgWCrq 16IhzPDBKST4vvKuY2mjqpEi92r+0YsAGO5paHxE=
Message-Id: <6.2.5.6.2.20110419080338.0301b940@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 19 Apr 2011 10:58:53 -0700
To: Bob Hinden <bob.hinden@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: IAOC: delegating ex-officio responsibility
In-Reply-To: <D0674791-3D7C-4B90-8189-A895715B977A@gmail.com>
References: <2BE582FA-2682-4232-9D83-23A03F01A0DB@NLnetLabs.nl> <6.2.5.6.2.20110330073936.0e1899d0@resistor.net> <E2E41FDE-3818-4513-9933-CB1E0326B43E@nlnetlabs.nl> <6.2.5.6.2.20110330113947.0c948bc0@resistor.net> <4D942843.4060804@gmail.com> <6.2.5.6.2.20110331120351.09488990@resistor.net> <4D955661.8050502@gmail.com> <9C81C0F6-3ABE-4479-8C5E-C20C486D052A@gmail.com> <82A347CC-BB19-4A73-8E8A-924FBAA92A5F@NLnetLabs.nl> <84D6568B-18C9-47B2-A457-C51C2FB3351F@gmail.com> <5419FA805EF52E79D7822966@PST.JCK.COM> <DAC0FFD9-9B3B-4726-B56B-5E9BE5A5F1D1@gmail.com> <4DA8685F.5050504@dcrocker.net> <D0674791-3D7C-4B90-8189-A895715B977A@gmail.com>
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: Tue, 19 Apr 2011 18:01:07 -0000

Hi Bob,
At 14:25 18-04-2011, Bob Hinden wrote:
>I didn't say no one else could do the job adequately.  I said "would 
>have a negative impact" on the operations of the IETF.
>
>Some examples where an I* chair had a significant influence on a 
>decision that IAOC made include:
>
>  - The hiring of the Transitional RSE
>  - Many of the Beijing meeting issues (prior and post signing the MOU)
>  - Specific venue selections (in one case avoiding a less than ideal venue)
>  - The need for transparency in certain IAOC actions (day passes, 
> venue rotation)
>  - Discussion of what policy decisions that the IAOC can make vs. 
> the IESG vs. community
>  - Discussion about when to get community feedback
>  - Secretariat contract (RFP, bidders review, selection, etc.)
>  - RFC Publisher and Publisher contracts  (RFP, bidders review, 
> selection, etc.)
>
>Some of these decision might have been different without one or more 
>I* chairs being directly involved in the decision.  Please review 
>the minutes for more detail.

 From RFC 4071:

   "The IAOC shall be accountable to the IETF community for the
    effectiveness, efficiency, and transparency of the IASA."

In a personal note that Olaf posted ( 
http://www.ietf.org/mail-archive/web/ietf/current/msg66161.html ), it 
is mentioned that it takes 0.7 FTE.  I do not believe that the 
decisions mentioned above are unimportant.  However, you have to 
consider which decisions require your attention when you have a 
limited amount of time available.

The current members of the IAOC, excluding ex officio, are:

  Eric Burger
  Dave Crocker
  Marshall Eubanks
  Bob Hinden
  Ray Pelletier (non-voting)

None of them are new to the IETF.  If it requires I* Chairs for the 
IAOC to be transparent, something is not right.

>I think the I* chairs, in my view bring a broad view of the 
>community and operational needs based on what's involved in doing 
>their jobs than another person would not have.

If I understand your arguments, it is also about avoiding a 
disconnect between the administrative side of the IETF and the IAB/IESG.

draft-kolkman-iasa-ex-officio-membership-00 argues for a change to 
reduce the workload and make the I* Chair positions more 
attractive.  Would it help if the IAOC Chair has a liaison position 
on the IAB and IESG?  The IAB and IESG Chairs can use their 
discretion to determine which IAOC meetings they should attend.  The 
IAOC Chair gets a broader view.

The above pushes the workload around instead of addressing the 
problem.  If this trend continues, the best fit people will turn down 
I* positions.

Regards,
-sm  


From wwwrun@ietfc.amsl.com  Tue Apr 19 11:26:06 2011
Return-Path: <wwwrun@ietfc.amsl.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfc.amsl.com
Received: by ietfc.amsl.com (Postfix, from userid 30) id 6C8C2E0856; Tue, 19 Apr 2011 11:26:06 -0700 (PDT)
From: IETF Administrative Director <iad@ietf.org>
To: IETF Announcement list <ietf-announce@ietf.org>
Subject: North American Cable Industry to Host IETF 85 
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20110419182606.6C8C2E0856@ietfc.amsl.com>
Date: Tue, 19 Apr 2011 11:26:06 -0700 (PDT)
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: Tue, 19 Apr 2011 18:26:06 -0000

The IAOC is pleased to be able to announce sponsors for IETF 85 in Atlanta
in November 4 - 9, 2012. That meeting will be hosted by the North American
cable industry. The sponsoring companies are Comcast, Time Warner Cable,
CableLabs, the National Cable & Telecommunications Association,
Brighthouse, Cablevision, Charter, and Cox.

Comcast hosted IETF 71 in Philadelphia and has sponsored meeting breaks
and ice cream socials at other meetings, such as recently in Prague.

Thanks to the cable industry!  

Interested in hosting an IETF meeting?  Contact Drew Dvorshak at
dvorshak@isoc.org.

Ray Pelletier
IETF Administrative Director

From bob.hinden@gmail.com  Tue Apr 19 12:53:53 2011
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id A2A1AE069C for <ietf@ietfc.amsl.com>; Tue, 19 Apr 2011 12:53:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.528
X-Spam-Level: 
X-Spam-Status: No, score=-103.528 tagged_above=-999 required=5 tests=[AWL=0.071, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xQ-rHbRM5nRA for <ietf@ietfc.amsl.com>; Tue, 19 Apr 2011 12:53:52 -0700 (PDT)
Received: from mail-pv0-f172.google.com (mail-pv0-f172.google.com [74.125.83.172]) by ietfc.amsl.com (Postfix) with ESMTP id A90BDE0670 for <ietf@ietf.org>; Tue, 19 Apr 2011 12:53:52 -0700 (PDT)
Received: by pvh1 with SMTP id 1so21582pvh.31 for <ietf@ietf.org>; Tue, 19 Apr 2011 12:53:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=/it/3nDiXzoK3dd7DvlIELoTh2fQoFGiaWeJGcir4qU=; b=By7Zm175uxvwpAHQZwXcUz7BSQB0LsSoxupPO8kpz/NTSX/c+N3IfELEQEuHChBzjW XJi9emjIoO+y6RtfvVNYFxvtKhZSs9pwfNjV5tYwfSAnJag13JSb/sxVOmXOr3KS3SaZ kYUtbLpDAmmoyNY5VV1pm+vqAd30RzjvcLzHY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=VBD3bYCnTLQ72MS5UQPIdVwVFte0lHIDnvaNbgG1pUKOGSPmbeZEX8xuFmeq1NnaNB 9I1hJgpfhpdnVd5RtkJWzXwuxkxWdnGc+HrmzCU18JIZ9VaYQ9DNZwEO0mZRItQuHJ49 BU7tO7EHib6RI6k+HYejNwAk7mFwD50rhr8C8=
Received: by 10.68.54.70 with SMTP id h6mr2161394pbp.297.1303242832171; Tue, 19 Apr 2011 12:53:52 -0700 (PDT)
Received: from [172.16.224.217] ([209.97.127.34]) by mx.google.com with ESMTPS id u10sm132000pbb.32.2011.04.19.12.53.51 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 19 Apr 2011 12:53:51 -0700 (PDT)
Subject: Re: IAOC: delegating ex-officio responsibility
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: <4DADC758.2080906@dcrocker.net>
Date: Tue, 19 Apr 2011 12:53:50 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <7D0E8BCB-194D-4FA1-ABDA-2F3175BA9441@gmail.com>
References: <2BE582FA-2682-4232-9D83-23A03F01A0DB@NLnetLabs.nl>	<6.2.5.6.2.20110330073936.0e1899d0@resistor.net>	<E2E41FDE-3818-4513-9933-CB1E0326B43E@nlnetlabs.nl>	<6.2.5.6.2.20110330113947.0c948bc0@resistor.net>	<4D942843.4060804@gmail.com>	<6.2.5.6.2.20110331120351.09488990@resistor.net>	<4D955661.8050502@gmail.com>	<9C81C0F6-3ABE-4479-8C5E-C20C486D052A@gmail.com>	<82A347CC-BB19-4A73-8E8A-924FBAA92A5F@NLnetLabs.nl>	<84D6568B-18C9-47B2-A457-C51C2FB3351F@gmail.com>	<5419FA805EF52E79D7822966@PST.JCK.COM> <DAC0FFD9-9B3B-4726-B56B-5E9BE5A5F1D1@gmail.com> <4DA8685F.5050504@dcrocker.net> <D0674791-3D7C-4B90-8189-A895715B977A@gmail.com> <4DADC758.2080906@dcrocker.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.1084)
Cc: Bob Hinden <bob.hinden@gmail.com>, 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: Tue, 19 Apr 2011 19:53:53 -0000

Dave,

On Apr 19, 2011, at 10:33 AM, Dave CROCKER wrote:

> Bob, et al,
>=20
> On 4/18/2011 2:25 PM, Bob Hinden wrote:
>> I didn't say no one else could do the job adequately.  I said "would =
have a
>> negative impact" on the operations of the IETF.
>=20
> Right. And my second sentence did go farther than I meant.
>=20
> However rejecting an effort to change the current arrangement -- =
especially when it is initiated by a principal -- means that =
alternatives are not acceptable, which translates roughly to saying the =
alternatives will not produce adequate performance.  Otherwise it looks =
like a difference between 'adequate' and perhaps "perfect"?

We don't get perfect :-)

>=20
> There is a core reality, here, that the I* Chairs are overburdened. =
This is obvious from looking at the list of their duties and underscored =
by the source of the current initiative.  We can choose to defer doing =
anything, under the guise of taking a 'holistic' view or we can try to =
help with the specific burden that is the focus of the overburdened =
folk.  On the average, we do better with incremental change and this is =
the one before us now.


Then let's talk about the overall problem and not a point solution.

> If I generalize this, I would say that the I* chairs have been =
actively
>> involved in the most significant decisions the IAOC makes, they tend =
to be
>> less active in many of the day to day operational issues.
> ...
>> I think the I* chairs, in my view bring a broad view of the community =
and
>> operational needs based on what's involved in doing their jobs than =
another
>> person would not have.
>=20
> My own simplistic summary:  For some topics it is extremely helpful to =
have the broader knowledge and insight that can be provided by an I* =
chair. For many topics, this is not needed, but for some it makes a =
significant difference.


I agree, and it is representative of the level of current participation =
of I* chairs.


>=20
> To that end, here's a very simple proposal that resolves the issue =
cleanly:
>=20
>     1. ISOC, IAB and IESG each appoint one person currently.  Change =
this to be two each, the same as Nomcom.  Each year, they would appoint =
one person.
>=20
>     2. Move the I* Chairs to be non-voting ex-officio participants, =
the same as the IETF Administrative Director.  They are welcome to =
participate or be explicitly invited to all IAOC/Trust activities.
>=20
> This produces the continuity that is needed for the admin work, but =
also retains access to the expertise of the I* chairs.


I don't agree.  Appointing two people (or more?) doesn't solve the =
problem I am concerned about, it still doesn't bring the chairs =
perspective.  It also significantly changes the governance model by =
changing the balance between between nomcom, iab, iesg, and ISOC =
appointed members.  Also, adding six people (still counting the chairs) =
will make the IAOC much larger and unwieldy. =20

Bob




From stpeter@stpeter.im  Tue Apr 19 13:08:36 2011
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 489FFE081C; Tue, 19 Apr 2011 13:08:36 -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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HE8oBbv6LOnm; Tue, 19 Apr 2011 13:08:35 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by ietfc.amsl.com (Postfix) with ESMTP id 13521E0811; Tue, 19 Apr 2011 13:08:35 -0700 (PDT)
Received: from dhcp-64-101-72-185.cisco.com (dhcp-64-101-72-185.cisco.com [64.101.72.185]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 7403F40D6A; Tue, 19 Apr 2011 14:12:08 -0600 (MDT)
Message-ID: <4DADEBC0.1060200@stpeter.im>
Date: Tue, 19 Apr 2011 14:08:32 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Paul Lambert <paul@marvell.com>
Subject: Re: [paws] WG Review: Protocol to Access White Space database (paws)
References: <20110419165634.CD24CE07CF@ietfc.amsl.com>	<4DADCB52.1020309@joelhalpern.com> <7BAC95F5A7E67643AAFB2C31BEE662D01406AC564E@SC-VEXCH2.marvell.com>
In-Reply-To: <7BAC95F5A7E67643AAFB2C31BEE662D01406AC564E@SC-VEXCH2.marvell.com>
X-Enigmail-Version: 1.1.1
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms020801000302000909070604"
Cc: "paws@ietf.org" <paws@ietf.org>, "iesg@ietf.org" <iesg@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, 19 Apr 2011 20:08:36 -0000

This is a cryptographically signed message in MIME format.

--------------ms020801000302000909070604
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 4/19/11 1:47 PM, Paul Lambert wrote:
>=20
>=20
> How does the area that the group is assigned impact the choices of
> technology?
>=20
> I'm an advocate for an efficient solution set for PAWS ... it will be
> much like DNS for spectrum in the future and should be viewed as a
> core infrastructural component that needs careful design.  There are
> good reasons that routing protocols don't use XML.
>=20
> Applications now days tend to go for the simple, quick to make a web
> application solutions using XML or the like ...  My concern is that
> "Applications" imply that efficiency does not matter.

A quick look at the specifications for the CORE WG in the Applications
Area will show you that we're able to produce protocols that are quite
slim on the wire.

Peter

--=20
Peter Saint-Andre
https://stpeter.im/




--------------ms020801000302000909070604
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIITzjCC
BjQwggQcoAMCAQICASMwDQYJKoZIhvcNAQELBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoT
DVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNp
Z25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3
MTAyNDIxMDMzM1oXDTE3MTAyNDIxMDMzM1owgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1T
dGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu
aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAzIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBALmjSW4SPiDKlAinvVeL
ZOVfItiuP1aRHL530E7QUc9icCwL33+PH+Js1HAh8CgWFl34sOxx1FJyS/C4VLPRsqDfP72j
tzCVUAL0DAxZ7wgzQvFz7x61jGxfhYhqYb1+PPOLkYBbkRIrPMg3dLEdKmXIYJYXDH+mB/V/
jLo73/Kb7h/rNoNg/oHHSv5Jolyvp5IY2btfcTBfW/telEFj5rDTX2juTvZ3Qhf3XQX5ca3Q
7A10zrUV/cWJOJ7F5RltbEIaboZmX5JBUb3FhUiAdBotehAX6DbDOuYoJtVxmGof6GuVGcPo
98K4TJf8FHo+UA9EOVDp/W7fCqKT4sXk/XkCAwEAAaOCAa0wggGpMA8GA1UdEwEB/wQFMAMB
Af8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBR7iZySlyShhEcCy3T8LvSs3DLl8zAfBgNV
HSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRaMFgwJwYIKwYBBQUH
MAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYhaHR0cDovL3d3
dy5zdGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6Ly93d3cu
c3RhcnRzc2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5jb20v
c2ZzY2EuY3JsMIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQELBQADggIBAGpd
SbdLFMhirxK37V4gE00+uW74UdAXtDgQI3AsRZWtaRtKHgAxFBSteqz4kDkeAjH/1b+K8tQR
6cxSI2nho7qOaPW/UpzOfSS/MeKK/9vfM2lfs+uItXH7LWtvS9wD1erfH1a+BXHCrCp4LA1l
fADDhRIiGTSS3i0Zu5xV3INNRHrCCCl6patltQ8RZTqzDMri7ombgIxjN51Zo7xV77EZcThV
0GA8iIN+7T53uHhUJpjfLIztHs/69OclRvHux9hCflfOm7GY5Sc4nqjfES+5XPArGGWiQSEk
ez37QfXqsxO3oCHK4b3DFZysG4uyOuC/WL80ab3muQ3tgwjBhq0D3JZN5kvu5gSuNZPa1WrV
hEgXkd6C7s5stqB6/htVpshG08jRz9DEutGM9oKQ1ncTivbfPNx7pILoHWvvT7N5i/puVoNu
bPUmLXh/2wA6wzAzuuoONiIL14Xpw6jLSnqpaLWElo2yTIFZ/CU/nCvvpW1Dj1457P3Ci9bD
0RPkWSR+CuucpgxrEmaw4UOLxflzuYYaq1RJwygOO5K0s2bAWOcXpgteyUOnQ3d/EjJAWRri
2v0ubiq+4H3KUOMlbznlPAY/1T8YyyJPM88+Ueahe/AW1zoUwZayNcTnuM7cq6yBV8Wr3GOI
LFXhtT0UVuJLChPMJKVKVsa7qNorlLkMMIIGxzCCBa+gAwIBAgICAIswDQYJKoZIhvcNAQEF
BQAwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJT
ZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBD
bGFzcyAzIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTAeFw0xMDEwMTQwMTM2MzRa
Fw0xMjEwMTQxMjAxMDdaMIHAMSAwHgYDVQQNExcyNzQ1ODEtOU5YMDRxeExEYjBvNDY5VDEL
MAkGA1UEBhMCVVMxETAPBgNVBAgTCENvbG9yYWRvMQ8wDQYDVQQHEwZEZW52ZXIxLDAqBgNV
BAsTI1N0YXJ0Q29tIFRydXN0ZWQgQ2VydGlmaWNhdGUgTWVtYmVyMRowGAYDVQQDExFQZXRl
ciBTYWludC1BbmRyZTEhMB8GCSqGSIb3DQEJARYSc3RwZXRlckBzdHBldGVyLmltMIIBIjAN
BgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAuERvnrkpQTx9wbJfgxbNKEYvt0IilecZRUM6
wrbCzIUPCocuYhaAJcQoqIyHaKybPQ7f+DIGIAolAa3dHnNdlsXP2smTft/ZNpj10PIG5bil
NAqLUYwmLJaEaqY7BMW8423U3blW43/luLJk/Pq4OsWcw7AK3LeVh1U/HOgqhin26N3h72X1
nbLEpZFrgcp8egmWtXLCbLBDMqUK3j6wjLldni79muzYEVqU0A5GqSeb8Wc4kIx8VI5yL24J
KzinG2iVRP5ZDEbOZETzBXJabUsV56XSxqPG9DK6ke+ybCiL/wKV1HFqdtFB1y25lfvHgOP2
gyEApBKEDNjgLmKyyQIDAQABo4IC+zCCAvcwCQYDVR0TBAIwADALBgNVHQ8EBAMCBLAwHQYD
VR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMB0GA1UdDgQWBBS2EW2iNB+g0EibKJLBdv8I
eLovVDAfBgNVHSMEGDAWgBR7iZySlyShhEcCy3T8LvSs3DLl8zAdBgNVHREEFjAUgRJzdHBl
dGVyQHN0cGV0ZXIuaW0wggFCBgNVHSAEggE5MIIBNTCCATEGCysGAQQBgbU3AQICMIIBIDAu
BggrBgEFBQcCARYiaHR0cDovL3d3dy5zdGFydHNzbC5jb20vcG9saWN5LnBkZjA0BggrBgEF
BQcCARYoaHR0cDovL3d3dy5zdGFydHNzbC5jb20vaW50ZXJtZWRpYXRlLnBkZjCBtwYIKwYB
BQUHAgIwgaowFBYNU3RhcnRDb20gTHRkLjADAgEBGoGRTGltaXRlZCBMaWFiaWxpdHksIHNl
ZSBzZWN0aW9uICpMZWdhbCBMaW1pdGF0aW9ucyogb2YgdGhlIFN0YXJ0Q29tIENlcnRpZmlj
YXRpb24gQXV0aG9yaXR5IFBvbGljeSBhdmFpbGFibGUgYXQgaHR0cDovL3d3dy5zdGFydHNz
bC5jb20vcG9saWN5LnBkZjBjBgNVHR8EXDBaMCugKaAnhiVodHRwOi8vd3d3LnN0YXJ0c3Ns
LmNvbS9jcnR1My1jcmwuY3JsMCugKaAnhiVodHRwOi8vY3JsLnN0YXJ0c3NsLmNvbS9jcnR1
My1jcmwuY3JsMIGOBggrBgEFBQcBAQSBgTB/MDkGCCsGAQUFBzABhi1odHRwOi8vb2NzcC5z
dGFydHNzbC5jb20vc3ViL2NsYXNzMy9jbGllbnQvY2EwQgYIKwYBBQUHMAKGNmh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2NlcnRzL3N1Yi5jbGFzczMuY2xpZW50LmNhLmNydDAjBgNVHRIE
HDAahhhodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS8wDQYJKoZIhvcNAQEFBQADggEBADVtbXJG
tKAr55xc/OUM546gXUybI72Bank0w739Mv+9BBNtq9rMEvCnLmSKhBi76c1mdXh6zXs8RQDo
6nR/aPabE3llF2T4z80smi9jfnl3y9dpu9TcgDoqDLZ7a2lBlW656XAAQzHjvLp2MC7/mxlg
PYH2axa+q40mAYM20GbNsAEGbWQT1IqIh0BcLLsgbaMJHbyG/57zd9JLyMX3Vry1L1fJRQr3
GeLxMV5RtxN+mBgxrwFz/cOc09COiFExlsHgekpB5O43gqsAU16MXypyoSt4MrSfKTMHIGx6
2RF/M6vqUlvhi28gk2ZUvQ/+OX5+gjcZyooEzAAn4RuOKNswggbHMIIFr6ADAgECAgIAizAN
BgkqhkiG9w0BAQUFADCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4x
KzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMT
L1N0YXJ0Q29tIENsYXNzIDMgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBMB4XDTEw
MTAxNDAxMzYzNFoXDTEyMTAxNDEyMDEwN1owgcAxIDAeBgNVBA0TFzI3NDU4MS05TlgwNHF4
TERiMG80NjlUMQswCQYDVQQGEwJVUzERMA8GA1UECBMIQ29sb3JhZG8xDzANBgNVBAcTBkRl
bnZlcjEsMCoGA1UECxMjU3RhcnRDb20gVHJ1c3RlZCBDZXJ0aWZpY2F0ZSBNZW1iZXIxGjAY
BgNVBAMTEVBldGVyIFNhaW50LUFuZHJlMSEwHwYJKoZIhvcNAQkBFhJzdHBldGVyQHN0cGV0
ZXIuaW0wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC4RG+euSlBPH3Bsl+DFs0o
Ri+3QiKV5xlFQzrCtsLMhQ8Khy5iFoAlxCiojIdorJs9Dt/4MgYgCiUBrd0ec12Wxc/ayZN+
39k2mPXQ8gbluKU0CotRjCYsloRqpjsExbzjbdTduVbjf+W4smT8+rg6xZzDsArct5WHVT8c
6CqGKfbo3eHvZfWdssSlkWuBynx6CZa1csJssEMypQrePrCMuV2eLv2a7NgRWpTQDkapJ5vx
ZziQjHxUjnIvbgkrOKcbaJVE/lkMRs5kRPMFclptSxXnpdLGo8b0MrqR77JsKIv/ApXUcWp2
0UHXLbmV+8eA4/aDIQCkEoQM2OAuYrLJAgMBAAGjggL7MIIC9zAJBgNVHRMEAjAAMAsGA1Ud
DwQEAwIEsDAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwHQYDVR0OBBYEFLYRbaI0
H6DQSJsoksF2/wh4ui9UMB8GA1UdIwQYMBaAFHuJnJKXJKGERwLLdPwu9KzcMuXzMB0GA1Ud
EQQWMBSBEnN0cGV0ZXJAc3RwZXRlci5pbTCCAUIGA1UdIASCATkwggE1MIIBMQYLKwYBBAGB
tTcBAgIwggEgMC4GCCsGAQUFBwIBFiJodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9wb2xpY3ku
cGRmMDQGCCsGAQUFBwIBFihodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9pbnRlcm1lZGlhdGUu
cGRmMIG3BggrBgEFBQcCAjCBqjAUFg1TdGFydENvbSBMdGQuMAMCAQEagZFMaW1pdGVkIExp
YWJpbGl0eSwgc2VlIHNlY3Rpb24gKkxlZ2FsIExpbWl0YXRpb25zKiBvZiB0aGUgU3RhcnRD
b20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgUG9saWN5IGF2YWlsYWJsZSBhdCBodHRwOi8v
d3d3LnN0YXJ0c3NsLmNvbS9wb2xpY3kucGRmMGMGA1UdHwRcMFowK6ApoCeGJWh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2NydHUzLWNybC5jcmwwK6ApoCeGJWh0dHA6Ly9jcmwuc3RhcnRz
c2wuY29tL2NydHUzLWNybC5jcmwwgY4GCCsGAQUFBwEBBIGBMH8wOQYIKwYBBQUHMAGGLWh0
dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9zdWIvY2xhc3MzL2NsaWVudC9jYTBCBggrBgEFBQcw
AoY2aHR0cDovL3d3dy5zdGFydHNzbC5jb20vY2VydHMvc3ViLmNsYXNzMy5jbGllbnQuY2Eu
Y3J0MCMGA1UdEgQcMBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tLzANBgkqhkiG9w0BAQUF
AAOCAQEANW1tcka0oCvnnFz85QznjqBdTJsjvYFqeTTDvf0y/70EE22r2swS8KcuZIqEGLvp
zWZ1eHrNezxFAOjqdH9o9psTeWUXZPjPzSyaL2N+eXfL12m71NyAOioMtntraUGVbrnpcABD
MeO8unYwLv+bGWA9gfZrFr6rjSYBgzbQZs2wAQZtZBPUioiHQFwsuyBtowkdvIb/nvN30kvI
xfdWvLUvV8lFCvcZ4vExXlG3E36YGDGvAXP9w5zT0I6IUTGWweB6SkHk7jeCqwBTXoxfKnKh
K3gytJ8pMwcgbHrZEX8zq+pSW+GLbyCTZlS9D/45fn6CNxnKigTMACfhG44o2zGCA80wggPJ
AgEBMIGTMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UE
CxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRD
b20gQ2xhc3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAgCLMAkGBSsOAwIa
BQCgggIOMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDQx
OTIwMDgzMlowIwYJKoZIhvcNAQkEMRYEFDZeFQ9KNyBGK3rvYRBiioj5si7cMF8GCSqGSIb3
DQEJDzFSMFAwCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggq
hkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBpAYJKwYBBAGCNxAEMYGWMIGT
MIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2Vj
dXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xh
c3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAgCLMIGmBgsqhkiG9w0BCRAC
CzGBlqCBkzCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNV
BAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMTL1N0YXJ0
Q29tIENsYXNzIDMgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBAgIAizANBgkqhkiG
9w0BAQEFAASCAQA3VODZyDTTlqyP/UmGRJKW5g9JiaZ0Zt7nWnS6zuQhsgeHRyHN6DioD2NO
xXQmc2IXQ2mgyRiIqwILVMxqBUu/ARm1bBTICUGQm2CD5de9lD9FBHZIv96REPfXIfoLt2xp
M2RISL7K650493SeTzvvdKFtpPc8DmlrQG0jrZPuuNM8lhfnolASQ3HPMZ0KnygF81efrNdq
wovTLLHfu3MzO7iGSYlrTK4uww1i6GjyEsr/1CPi9WAlpnn5R4ZzKAo7PYhiGf250MRzKsLc
03JspxrtmVPb5RVkqDZJInLd4xVOCwRkwuIPhcEsvDx8s5qSV78ysw22XSFqVr2GQx1MAAAA
AAAA
--------------ms020801000302000909070604--

From bob.hinden@gmail.com  Tue Apr 19 14:04:32 2011
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id CB35BE076E for <ietf@ietfc.amsl.com>; Tue, 19 Apr 2011 14:04:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.532
X-Spam-Level: 
X-Spam-Status: No, score=-103.532 tagged_above=-999 required=5 tests=[AWL=0.067, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p4JMldJp3GMw for <ietf@ietfc.amsl.com>; Tue, 19 Apr 2011 14:04:32 -0700 (PDT)
Received: from mail-px0-f182.google.com (mail-px0-f182.google.com [209.85.212.182]) by ietfc.amsl.com (Postfix) with ESMTP id 07A09E0717 for <ietf@ietf.org>; Tue, 19 Apr 2011 14:04:31 -0700 (PDT)
Received: by pxi20 with SMTP id 20so77602pxi.27 for <ietf@ietf.org>; Tue, 19 Apr 2011 14:04:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=FfdxtlhfcEz5i2O8bRF2I2fPa2pgQ4+XplLibd0aJcg=; b=e+9WEf2ivfpB126IRFr2OxAm/0hGRKbTQ6m1Y+ZOdu6Qpnv0cLEesz3TT1DnxwvCYy agEfv3nfOV+CFpF1N/FpGGSZwRwNOFy34MhLwkHtPrCbABTsKRtU+ixLZbZK/O62qTR2 rPd8+Pv/p4X5T7o9d4BBZH04n16fRN1AUgbBc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=WHOziYDVGq/LyCFtOTmzjifrhfkLnzCdH8a85pSwhKmIS6lE4K+mCLW0JYoOi5JUth 2Jox/H4yN0LuAdT9P5oE/iH3wA5zH28QYq7UCOL4s2/R5Tq+B3ZANWQ2He1Z2EN6EPH2 K4SLbngr90SzZDT+/s4/hgEQzXY2nX8Xl4XvM=
Received: by 10.68.58.9 with SMTP id m9mr9232325pbq.283.1303247071352; Tue, 19 Apr 2011 14:04:31 -0700 (PDT)
Received: from [172.16.224.217] ([209.97.127.34]) by mx.google.com with ESMTPS id t10sm165020pbh.9.2011.04.19.14.04.29 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 19 Apr 2011 14:04:29 -0700 (PDT)
Subject: Re: IAOC: delegating ex-officio responsibility
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: <6.2.5.6.2.20110419080338.0301b940@resistor.net>
Date: Tue, 19 Apr 2011 14:04:28 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <90F3E256-88F5-4DCF-A64B-EF7FDDE667C8@gmail.com>
References: <2BE582FA-2682-4232-9D83-23A03F01A0DB@NLnetLabs.nl> <6.2.5.6.2.20110330073936.0e1899d0@resistor.net> <E2E41FDE-3818-4513-9933-CB1E0326B43E@nlnetlabs.nl> <6.2.5.6.2.20110330113947.0c948bc0@resistor.net> <4D942843.4060804@gmail.com> <6.2.5.6.2.20110331120351.09488990@resistor.net> <4D955661.8050502@gmail.com> <9C81C0F6-3ABE-4479-8C5E-C20C486D052A@gmail.com> <82A347CC-BB19-4A73-8E8A-924FBAA92A5F@NLnetLabs.nl> <84D6568B-18C9-47B2-A457-C51C2FB3351F@gmail.com> <5419FA805EF52E79D7822966@PST.JCK.COM> <DAC0FFD9-9B3B-4726-B56B-5E9BE5A5F1D1@gmail.com> <4DA8685F.5050504@dcrocker.net> <D0674791-3D7C-4B90-8189-A895715B977A@gmail.com> <6.2.5.6.2.20110419080338.0301b940@resistor.net>
To: SM <sm@resistor.net>
X-Mailer: Apple Mail (2.1084)
Cc: Bob Hinden <bob.hinden@gmail.com>, 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: Tue, 19 Apr 2011 21:04:32 -0000

SM,

> Eric Burger
> Dave Crocker
> Marshall Eubanks
> Bob Hinden
> Ray Pelletier (non-voting)
>=20
> None of them are new to the IETF.  If it requires I* Chairs for the =
IAOC to be transparent, something is not right.

But that may not always be the case that all IAOC members have a lot of =
IETF experience.  We need to have a governance model that works into the =
future. =20

>=20
>> I think the I* chairs, in my view bring a broad view of the community =
and operational needs based on what's involved in doing their jobs than =
another person would not have.
>=20
> If I understand your arguments, it is also about avoiding a disconnect =
between the administrative side of the IETF and the IAB/IESG.

Yes

>=20
> draft-kolkman-iasa-ex-officio-membership-00 argues for a change to =
reduce the workload and make the I* Chair positions more attractive.  =
Would it help if the IAOC Chair has a liaison position on the IAB and =
IESG?  The IAB and IESG Chairs can use their discretion to determine =
which IAOC meetings they should attend.  The IAOC Chair gets a broader =
view.
>=20
> The above pushes the workload around instead of addressing the =
problem.  If this trend continues, the best fit people will turn down I* =
positions.

It would certainly give the IAOC chair a broader view, but still not the =
views of the I* chair.  Also, if the I* chairs (3 of 9 voting members) =
regularly didn't attend, it would be much harder to get a quorum for a =
meeting and pass motions. =20

Bob


From stephen.farrell@cs.tcd.ie  Tue Apr 19 14:28:18 2011
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id DEFC3E06DC; Tue, 19 Apr 2011 14:28:18 -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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zr+IJRVwd1PE; Tue, 19 Apr 2011 14:28:18 -0700 (PDT)
Received: from scss.tcd.ie (hermes.cs.tcd.ie [134.226.32.56]) by ietfc.amsl.com (Postfix) with ESMTP id D649AE06BE; Tue, 19 Apr 2011 14:28:17 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 917BC171C1E; Tue, 19 Apr 2011 22:28: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=1303248494; bh=QZfH1GSTosY99L m11AdI23c5lVaY9tiTj7Xfl5XQNaE=; b=OM/kvkqXApryA+NMH+Cw7ArWAtdbsa PtyQoV+77Wy0WnYWzBXdXy6Q9uHIv7rG+8RvH3OkzM+QW5WeK31mvKVfOPNNLulb vMjPNjYgc/g+ign381QCaLk+IjlDvhK/Cs5qNyd0lbOqBjGpzMKAD6v2zy/LazQ5 ihmYxe1gnMxGhSIg03DWJamhLusD43DB/iNiyHrIJ9erd+WXPZRCTRgXwnbuCPCQ gZOV+xeqVfQ3Z66IFCKRLDG94II+sLuUt3HQqUBi9CXd7MtKAbru3xBNe0Ra61jp K6TYI4vvcRgqbyuzbDU+/r04XJc4ce2b7gpllABvtbkSrOG+nhspYQMw==
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 FBQ5tlgAjSB7; Tue, 19 Apr 2011 22:28:14 +0100 (IST)
Received: from [10.87.48.10] (unknown [86.42.177.204]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 8A32E171C1B; Tue, 19 Apr 2011 22:28:14 +0100 (IST)
Message-ID: <4DADFE6D.3050107@cs.tcd.ie>
Date: Tue, 19 Apr 2011 22:28:13 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.14) Gecko/20110223 Lightning/1.0b2 Thunderbird/3.1.8
MIME-Version: 1.0
To: IETF-Discussion <ietf@ietf.org>
Subject: Re: WG Review: Protocol to Access White Space database (paws)
References: <20110419165634.CD24CE07CF@ietfc.amsl.com>
In-Reply-To: <20110419165634.CD24CE07CF@ietfc.amsl.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: paws@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: Tue, 19 Apr 2011 21:28:19 -0000

I think this is a good and timely thing for the IETF to do.

One part of this where I think it might be useful to get
some broader input (which may have happened already, I'm not
sure) is the following:

On 19/04/11 17:56, IESG Secretary wrote:
> The protocol must protect both the channel enablement process and the
> privacy of users. 

That part is fine but it goes on to say:

> Robust security mechanisms are required to prevent:
> device identity spoofing, modification of device requests, modification
> of channel enablement information, ...

I'm told (and believe) this in response to (at least) US
FCC requirements that call for a device ID and sometimes
serial number to be (securely, for some value of securely)
sent with the query.

Those appear to be real regulatory requirements in the
US, presumably so the regulator can stomp on someone who
messes about in the wrong spectrum at the wrong time.
(The link below [1] may be to the right or wrong bit of
those US regulations, I'm not at all sure, not being
from there;-)

So my questions:

Are there may be similar (or conflicting!) requirements
elsewhere?

Does this bit of the charter text need changes to work
well for other regions?

Separately, I'm not sure how to square those kinds of
regulatory requirements with protecting privacy where the
device is carried by a person and has some FCC device ID
(which lots do I guess) and the person might not want
the database operator to know who's asking. But I think
that's ok as something for the WG to figure out since
the charter already calls for respecting privacy.

I'm more concerned in case e.g. some other regional regulation
called for this protocol to be completely anonymous or
something, in which case the current charter text might
be problematic.

Cheers,
Stephen.

[1]
http://ecfr.gpoaccess.gov/cgi/t/text/text-idx?c=ecfr&sid=3e9c322addf1f7e897d8c84a6c7aca78&rgn=div8&view=text&node=47:1.0.1.1.14.8.243.9&idno=47

From jmh@joelhalpern.com  Tue Apr 19 19:13:29 2011
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 8B1BEE0670; Tue, 19 Apr 2011 19:13:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.487
X-Spam-Level: 
X-Spam-Status: No, score=-102.487 tagged_above=-999 required=5 tests=[AWL=0.112, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aV4rbnj82Dyi; Tue, 19 Apr 2011 19:13:28 -0700 (PDT)
Received: from hermes.out.tigertech.net (hermes.out.tigertech.net [74.114.88.72]) by ietfc.amsl.com (Postfix) with ESMTP id B03DAE0815; Tue, 19 Apr 2011 19:13:16 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.tigertech.net (Postfix) with ESMTP id 02CE243004E; Tue, 19 Apr 2011 19:13:16 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hermes.tigertech.net
Received: from [10.10.10.101] (pool-71-161-50-206.clppva.btas.verizon.net [71.161.50.206]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by hermes.tigertech.net (Postfix) with ESMTPSA id D47BA430052; Tue, 19 Apr 2011 19:13:14 -0700 (PDT)
Message-ID: <4DAE4139.9@joelhalpern.com>
Date: Tue, 19 Apr 2011 22:13:13 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.15) Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: Paul Lambert <paul@marvell.com>
Subject: Re: [paws] WG Review: Protocol to Access White Space database (paws)
References: <20110419165634.CD24CE07CF@ietfc.amsl.com> <4DADCB52.1020309@joelhalpern.com> <7BAC95F5A7E67643AAFB2C31BEE662D01406AC564E@SC-VEXCH2.marvell.com>
In-Reply-To: <7BAC95F5A7E67643AAFB2C31BEE662D01406AC564E@SC-VEXCH2.marvell.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "paws@ietf.org" <paws@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: Wed, 20 Apr 2011 02:13:29 -0000

Clearly, the discussion about whether the application protocol should be 
XML, plain ASCII/UTF8, binary, or some other encoding needs to take 
place.  But that can take place wherever we place the working group.

There is an argument, which you allude to, which would place this WG in 
the Internet Area as part of "infrastructure."  While that does not 
resonate with me, I do see that there is some merit in that perspective.

I tend to think we need to focus on transactional application experience 
(the apps area) or where we have experience with protocols that need to 
communicate geolocation (RAI).

I would hope, and expect, that the ADs for any area would be receptive 
to a proper evaluation of any candidate protocol and encoding.  (The 
arguments get complex, and it takes care to avoid religious assertions.)

Yours,
Joel

On 4/19/2011 3:47 PM, Paul Lambert wrote:
>
>
> How does the area that the group is assigned impact the choices of technology?
>
> I'm an advocate for an efficient solution set for PAWS ... it will be much like DNS for spectrum in the future and should be viewed as a core infrastructural component that needs careful design.  There are good reasons that routing protocols don't use XML.
>
> Applications now days tend to go for the simple, quick to make a web application solutions using XML or the like ...  My concern is that "Applications" imply that efficiency does not matter.
>
> Paul
>
>
>
>> -----Original Message-----
>> From: paws-bounces@ietf.org [mailto:paws-bounces@ietf.org] On Behalf Of
>> Joel M. Halpern
>> Sent: Tuesday, April 19, 2011 10:50 AM
>> To: iesg@ietf.org
>> Cc: paws@ietf.org; IETF discussion list
>> Subject: Re: [paws] WG Review: Protocol to Access White Space database
>> (paws)
>>
>> I think this working group is a good idea.
>> My inclination would be to place it in the Applications area.  It looks
>> like a nice application protocol to me.
>> There is a reasonable argument for placing it in RAI, as that is where
>> the relevant GEOLOC work has been done up till now.
>>
>> Yours,
>> Joel M. Halpern
>>
>> On 4/19/2011 12:56 PM, IESG Secretary wrote:
>>> A new IETF working group has been proposed.  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@ietf.org) by Tuesday, April 26, 2011.
>>>
>>>
>>> Protocol to Access White Space database (paws)
>>> ------------------------------------------------
>>> Current Status: Proposed Working Group
>>> Last updated: 2011-04-14
>>>
>>> Chairs:
>>> TBD
>>>
>>> Area Directors:
>>> TBD
>>>
>>> Area Advisor:
>>> TBD
>>>
>>> Mailing lists:
>>> Address: paws@ietf.org
>>> To Subscribe: https://www.ietf.org/mailman/listinfo/paws
>>> Archive: http://www.ietf.org/mail-archive/web/paws/
>>>
>>> Description of Working Group:
>>>
>>> Governments around the world continue to search for new pieces of
>> radio
>>> spectrum which can be used by the expanding wireless communications
>>> industry to provide more services in the usable spectrum. The concept
>>> of allowing secondary transmissions (licensed or unlicensed) in
>>> frequencies allocated to a primary user is a technique to "unlock"
>>> existing spectrum for new use. An obvious requirement is that these
>>> secondary transmissions do not interfere with the primary use of the
>>> spectrum. Often, in a given physical location, the primary user(s)
>> may
>>> not be using the entire band allocated to them. The available
>> spectrum
>>> for a secondary use would then depend on the location of the
>> secondary
>>> user. The primary user may have a schedule when it uses the spectrum,
>>> which may be available for secondary use outside that schedule. The
>>> fundamental issue is how to determine for a specific location and
>>> specific time, if any of the primary spectrum is available for
>> secondary
>>> use. One simple mechanism is to use a geospatial database that
>> records
>>> protected contours for primary users, and require the secondary users
>> to
>>> check the database prior to selecting what part of the spectrum they
>>> use. Such databases could be available on the Internet for query by
>>> users.
>>>
>>> In a typical implementation of geolocation and database to access TV
>>> white space, a radio is configured with, or has the capability to
>>> determine its location in latitude and longitude. At power-on, before
>>> the device can transmit or use any of the spectrum set aside for
>>> secondary use, the device must identify the relevant database to
>> query,
>>> contact the database, provide its geolocation and receive in return a
>>> list of unoccupied or "white space" spectrum (for example, in a TV
>>> White space implementation, the list of available channels at that
>>> location). The device can then select one of the channels from the
>> list
>>> and begin to transmit and receive on the selected channel. The device
>>> must query the database subsequently on a periodic basis for a list
>> of
>>> unoccupied channels based on certain conditions, e.g. a fixed amount
>> of
>>> time has passed or the device has changed location beyond a specified
>>> threshold.
>>>
>>> The databases are expected to be reachable via the Internet and the
>>> devices querying these databases are expected to have some form of
>>> Internet connectivity, directly or indirectly. The databases may be
>>> country specific since the available spectrum and regulations may
>> vary,
>>> but the fundamental operation of the protocol should be country
>>> independent, thus extensibility of data structures will be required.
>> The
>>> solution will not be tied to any specific spectrum, country, or
>>> phy/mac/air interface but may incorporate relevant aspects of these
>> as
>>> needed for proper operation.
>>>
>>> The proposed working group will :
>>> - standardize a protocol for querying the database, which includes a
>>> location sensitive database discovery mechanism and security for the
>>> protocol, and application services.
>>> - Standardize the data structure to be carried by the query
>>> protocol.
>>>
>>> The protocol must protect both the channel enablement process and the
>>> privacy of users. Robust security mechanisms are required to prevent:
>>> device identity spoofing, modification of device requests,
>> modification
>>> of channel enablement information, impersonation of registered
>> database
>>> services and unauthorized disclosure of a users location.
>>>
>>> Existing IETF location data structures and privacy mechanisms may be
>>> considered for use. The WG will also investigate the need for other
>>> mechanisms and related protocols to the White Space DB.
>>>
>>> The Working Group will set up and maintain appropriate contact and
>>> liaison with other relevant standards bodies and groups, including
>> IEEE
>>> 802.11af and IEEE 802.22 to begin with. The working group may also
>>> consider input from regulatory entities that are involved in the
>>> specification of the rules for secondary use of spectrum in specific
>>> bands.
>>>
>>> Goals and Milestones
>>>
>>> Sep 2011  Submit 'Requirements and Framework' to the IESG for
>>>             publication as Informational
>>>
>>> Apr 2012  Submit 'Protocol for Querying a Whitespace Database' to
>>>             the IESG for publication as Proposed Standard
>>>
>>> Apr 2012  Submit 'Data Model for Whitespace query protocol' to the
>>>             IESG for publication as Proposed Standard
>>> _______________________________________________
>>> paws mailing list
>>> paws@ietf.org
>>> https://www.ietf.org/mailman/listinfo/paws
>>>
>> _______________________________________________
>> paws mailing list
>> paws@ietf.org
>> https://www.ietf.org/mailman/listinfo/paws
>

From jmh@joelhalpern.com  Tue Apr 19 19:17:46 2011
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id DD2CCE0834; Tue, 19 Apr 2011 19:17:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.493
X-Spam-Level: 
X-Spam-Status: No, score=-102.493 tagged_above=-999 required=5 tests=[AWL=0.106, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DKWh3NHWRSgI; Tue, 19 Apr 2011 19:17:45 -0700 (PDT)
Received: from hermes.out.tigertech.net (hermes.out.tigertech.net [74.114.88.72]) by ietfc.amsl.com (Postfix) with ESMTP id 83B62E0814; Tue, 19 Apr 2011 19:17:45 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.tigertech.net (Postfix) with ESMTP id 2382A4300E5; Tue, 19 Apr 2011 19:17:45 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hermes.tigertech.net
Received: from [10.10.10.101] (pool-71-161-50-206.clppva.btas.verizon.net [71.161.50.206]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by hermes.tigertech.net (Postfix) with ESMTPSA id 9B92343004E; Tue, 19 Apr 2011 19:17:43 -0700 (PDT)
Message-ID: <4DAE4246.7080200@joelhalpern.com>
Date: Tue, 19 Apr 2011 22:17:42 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.15) Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: Rex Buddenberg <budden@nps.navy.mil>
Subject: Re: [paws] WG Review: Protocol to Access White Space database (paws)
References: <20110419165634.CD24CE07CF@ietfc.amsl.com>	 <4DADCB52.1020309@joelhalpern.com>	 <7BAC95F5A7E67643AAFB2C31BEE662D01406AC564E@SC-VEXCH2.marvell.com> <1303248099.2209.105.camel@localhost.localdomain>
In-Reply-To: <1303248099.2209.105.camel@localhost.localdomain>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Paul Lambert <paul@marvell.com>, "paws@ietf.org" <paws@ietf.org>, "iesg@ietf.org" <iesg@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: Wed, 20 Apr 2011 02:17:47 -0000

Actually, as far as I can tell, there is very little parallel between 
the PAWS problem and SNMP.
SNMP tends to be initiated by the manager, and used to extract 
information from the device in the network, or set information in teh 
device.
This protocol is used by the client.  It extracts basically stable 
information about what frequencies can be used in this geographic region 
at this time.
There is no "network management" going on.  the interaction does not 
look like SNMP.  And the effect does not look like SNMP.  While Radius 
or Diameter are closer, this protocol is not even a policy decision 
protocol.  There is no "policy".

So no, I do not think this looks anything like network management.
The protocols, the transaction drivers and behavior, the problem space, 
and the underlying data behavior are all very different from any of our 
NM work.

Yours,
Joel

On 4/19/2011 5:21 PM, Rex Buddenberg wrote:
> On Tue, 2011-04-19 at 12:47 -0700, Paul Lambert wrote:
>>
>> How does the area that the group is assigned impact the choices of
>> technology?
>>
>> I'm an advocate for an efficient solution set for PAWS ... it will be
>> much like DNS for spectrum in the future and should be viewed as a
>> core infrastructural component that needs careful design.  There are
>> good reasons that routing protocols don't use XML.
>
> While the DNS analogy works, I was thinking more a parallel -- or
> extension -- of SNMP.
>
> Still remain within 'applications', Joel?
>
>>
>> Applications now days tend to go for the simple, quick to make a web
>> application solutions using XML or the like ...  My concern is that
>> "Applications" imply that efficiency does not matter.
>>
>> Paul
>>
>>
>>
>>> -----Original Message-----
>>> From: paws-bounces@ietf.org [mailto:paws-bounces@ietf.org] On Behalf Of
>>> Joel M. Halpern
>>> Sent: Tuesday, April 19, 2011 10:50 AM
>>> To: iesg@ietf.org
>>> Cc: paws@ietf.org; IETF discussion list
>>> Subject: Re: [paws] WG Review: Protocol to Access White Space database
>>> (paws)
>>>
>>> I think this working group is a good idea.
>>> My inclination would be to place it in the Applications area.  It looks
>>> like a nice application protocol to me.
>>> There is a reasonable argument for placing it in RAI, as that is where
>>> the relevant GEOLOC work has been done up till now.
>>>
>>> Yours,
>>> Joel M. Halpern
>>>
>>> On 4/19/2011 12:56 PM, IESG Secretary wrote:
>>>> A new IETF working group has been proposed.  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@ietf.org) by Tuesday, April 26, 2011.
>>>>
>>>>
>>>> Protocol to Access White Space database (paws)
>>>> ------------------------------------------------
>>>> Current Status: Proposed Working Group
>>>> Last updated: 2011-04-14
>>>>
>>>> Chairs:
>>>> TBD
>>>>
>>>> Area Directors:
>>>> TBD
>>>>
>>>> Area Advisor:
>>>> TBD
>>>>
>>>> Mailing lists:
>>>> Address: paws@ietf.org
>>>> To Subscribe: https://www.ietf.org/mailman/listinfo/paws
>>>> Archive: http://www.ietf.org/mail-archive/web/paws/
>>>>
>>>> Description of Working Group:
>>>>
>>>> Governments around the world continue to search for new pieces of
>>> radio
>>>> spectrum which can be used by the expanding wireless communications
>>>> industry to provide more services in the usable spectrum. The concept
>>>> of allowing secondary transmissions (licensed or unlicensed) in
>>>> frequencies allocated to a primary user is a technique to "unlock"
>>>> existing spectrum for new use. An obvious requirement is that these
>>>> secondary transmissions do not interfere with the primary use of the
>>>> spectrum. Often, in a given physical location, the primary user(s)
>>> may
>>>> not be using the entire band allocated to them. The available
>>> spectrum
>>>> for a secondary use would then depend on the location of the
>>> secondary
>>>> user. The primary user may have a schedule when it uses the spectrum,
>>>> which may be available for secondary use outside that schedule. The
>>>> fundamental issue is how to determine for a specific location and
>>>> specific time, if any of the primary spectrum is available for
>>> secondary
>>>> use. One simple mechanism is to use a geospatial database that
>>> records
>>>> protected contours for primary users, and require the secondary users
>>> to
>>>> check the database prior to selecting what part of the spectrum they
>>>> use. Such databases could be available on the Internet for query by
>>>> users.
>>>>
>>>> In a typical implementation of geolocation and database to access TV
>>>> white space, a radio is configured with, or has the capability to
>>>> determine its location in latitude and longitude. At power-on, before
>>>> the device can transmit or use any of the spectrum set aside for
>>>> secondary use, the device must identify the relevant database to
>>> query,
>>>> contact the database, provide its geolocation and receive in return a
>>>> list of unoccupied or "white space" spectrum (for example, in a TV
>>>> White space implementation, the list of available channels at that
>>>> location). The device can then select one of the channels from the
>>> list
>>>> and begin to transmit and receive on the selected channel. The device
>>>> must query the database subsequently on a periodic basis for a list
>>> of
>>>> unoccupied channels based on certain conditions, e.g. a fixed amount
>>> of
>>>> time has passed or the device has changed location beyond a specified
>>>> threshold.
>>>>
>>>> The databases are expected to be reachable via the Internet and the
>>>> devices querying these databases are expected to have some form of
>>>> Internet connectivity, directly or indirectly. The databases may be
>>>> country specific since the available spectrum and regulations may
>>> vary,
>>>> but the fundamental operation of the protocol should be country
>>>> independent, thus extensibility of data structures will be required.
>>> The
>>>> solution will not be tied to any specific spectrum, country, or
>>>> phy/mac/air interface but may incorporate relevant aspects of these
>>> as
>>>> needed for proper operation.
>>>>
>>>> The proposed working group will :
>>>> - standardize a protocol for querying the database, which includes a
>>>> location sensitive database discovery mechanism and security for the
>>>> protocol, and application services.
>>>> - Standardize the data structure to be carried by the query
>>>> protocol.
>>>>
>>>> The protocol must protect both the channel enablement process and the
>>>> privacy of users. Robust security mechanisms are required to prevent:
>>>> device identity spoofing, modification of device requests,
>>> modification
>>>> of channel enablement information, impersonation of registered
>>> database
>>>> services and unauthorized disclosure of a users location.
>>>>
>>>> Existing IETF location data structures and privacy mechanisms may be
>>>> considered for use. The WG will also investigate the need for other
>>>> mechanisms and related protocols to the White Space DB.
>>>>
>>>> The Working Group will set up and maintain appropriate contact and
>>>> liaison with other relevant standards bodies and groups, including
>>> IEEE
>>>> 802.11af and IEEE 802.22 to begin with. The working group may also
>>>> consider input from regulatory entities that are involved in the
>>>> specification of the rules for secondary use of spectrum in specific
>>>> bands.
>>>>
>>>> Goals and Milestones
>>>>
>>>> Sep 2011  Submit 'Requirements and Framework' to the IESG for
>>>>             publication as Informational
>>>>
>>>> Apr 2012  Submit 'Protocol for Querying a Whitespace Database' to
>>>>             the IESG for publication as Proposed Standard
>>>>
>>>> Apr 2012  Submit 'Data Model for Whitespace query protocol' to the
>>>>             IESG for publication as Proposed Standard
>>>> _______________________________________________
>>>> paws mailing list
>>>> paws@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/paws
>>>>
>>> _______________________________________________
>>> paws mailing list
>>> paws@ietf.org
>>> https://www.ietf.org/mailman/listinfo/paws
>> _______________________________________________
>> paws mailing list
>> paws@ietf.org
>> https://www.ietf.org/mailman/listinfo/paws
>
>
>

From alexey.melnikov@isode.com  Wed Apr 20 02:26:14 2011
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id B01A2E0689; Wed, 20 Apr 2011 02:26:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.472
X-Spam-Level: 
X-Spam-Status: No, score=-102.472 tagged_above=-999 required=5 tests=[AWL=0.127, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0HN4PpF4H5-8; Wed, 20 Apr 2011 02:26:14 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by ietfc.amsl.com (Postfix) with ESMTP id 5EA04E0670; Wed, 20 Apr 2011 02:26:10 -0700 (PDT)
Received: from [192.168.1.124] ((unknown) [62.3.217.253])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <Ta6mrwAB78Xs@rufus.isode.com>; Wed, 20 Apr 2011 10:26:08 +0100
X-SMTP-Protocol-Errors: NORDNS
Message-ID: <4DAEA6A5.6020803@isode.com>
Date: Wed, 20 Apr 2011 10:25:57 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Paul Lambert <paul@marvell.com>
Subject: Re: [paws] WG Review: Protocol to Access White Space database (paws)
References: <20110419165634.CD24CE07CF@ietfc.amsl.com> <4DADCB52.1020309@joelhalpern.com> <7BAC95F5A7E67643AAFB2C31BEE662D01406AC564E@SC-VEXCH2.marvell.com> <4DADEBC0.1060200@stpeter.im>
In-Reply-To: <4DADEBC0.1060200@stpeter.im>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "paws@ietf.org" <paws@ietf.org>, "iesg@ietf.org" <iesg@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: Wed, 20 Apr 2011 09:26:14 -0000

Peter Saint-Andre wrote:

>On 4/19/11 1:47 PM, Paul Lambert wrote:
>  
>
>>How does the area that the group is assigned impact the choices of
>>technology?
>>
>>I'm an advocate for an efficient solution set for PAWS ... it will be
>>much like DNS for spectrum in the future and should be viewed as a
>>core infrastructural component that needs careful design.  There are
>>good reasons that routing protocols don't use XML.
>>
>>Applications now days tend to go for the simple, quick to make a web
>>application solutions using XML or the like ...  My concern is that
>>"Applications" imply that efficiency does not matter.
>>    
>>
Absolutely not. There are several counter examples in Apps, both past 
and present. (E.g. Lemonade WG was about optimized use of bandwidth for 
IMAP.)

>A quick look at the specifications for the CORE WG in the Applications
>Area will show you that we're able to produce protocols that are quite
>slim on the wire.
>
Exactly.


From ajs@shinkuro.com  Wed Apr 20 04:22:50 2011
Return-Path: <ajs@shinkuro.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 09807E0682; Wed, 20 Apr 2011 04:22:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.615
X-Spam-Level: 
X-Spam-Status: No, score=-102.615 tagged_above=-999 required=5 tests=[AWL=-0.016, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tjy1jHK6Su3Q; Wed, 20 Apr 2011 04:22:49 -0700 (PDT)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by ietfc.amsl.com (Postfix) with ESMTP id 746E2E0680; Wed, 20 Apr 2011 04:22:49 -0700 (PDT)
Received: from shinkuro.com (69-196-144-230.dsl.teksavvy.com [69.196.144.230]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id 4BA541ECB408; Wed, 20 Apr 2011 11:22:48 +0000 (UTC)
Date: Wed, 20 Apr 2011 07:21:51 -0400
From: Andrew Sullivan <ajs@shinkuro.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Subject: Re: [paws] WG Review: Protocol to Access White Space database (paws)
Message-ID: <20110420112150.GA5201@crankycanuck.ca>
References: <20110419165634.CD24CE07CF@ietfc.amsl.com> <4DADCB52.1020309@joelhalpern.com> <7BAC95F5A7E67643AAFB2C31BEE662D01406AC564E@SC-VEXCH2.marvell.com> <4DAE4139.9@joelhalpern.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4DAE4139.9@joelhalpern.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: Paul Lambert <paul@marvell.com>, "paws@ietf.org" <paws@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: Wed, 20 Apr 2011 11:22:50 -0000

On Tue, Apr 19, 2011 at 10:13:13PM -0400, Joel M. Halpern wrote:

> There is an argument, which you allude to, which would place this WG
> in the Internet Area as part of "infrastructure."  While that does
> not resonate with me, I do see that there is some merit in that
> perspective.

On the other hand (to continue the analogy with the DNS despite
Richard's shuddering), DNS Extensions is also sort of an awkward fit
in the Internet area (perhaps partly because many applications ought
to be able to use DNS data but aren't, and perhaps partly because it
is in fact an application sitting atop all those other things worked
on in the Internet area).

> encoding.  (The arguments get complex, and it takes care to avoid
> religious assertions.)

Indeed -- particularly when history becomes one of those topics of
religious dispute.

A

-- 
Andrew Sullivan
ajs@shinkuro.com
Shinkuro, Inc.

From vesely@tana.it  Wed Apr 20 04:32:28 2011
Return-Path: <vesely@tana.it>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 779CAE072B for <ietf@ietfc.amsl.com>; Wed, 20 Apr 2011 04:32:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.207
X-Spam-Level: 
X-Spam-Status: No, score=-6.207 tagged_above=-999 required=5 tests=[AWL=0.512,  BAYES_00=-2.599, GB_I_LETTER=-2, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CCTOQdg-Ifwm for <ietf@ietfc.amsl.com>; Wed, 20 Apr 2011 04:32:27 -0700 (PDT)
Received: from wmail.tana.it (mail.tana.it [62.94.243.226]) by ietfc.amsl.com (Postfix) with ESMTP id EE585E0695 for <ietf@ietf.org>; Wed, 20 Apr 2011 04:32:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tana.it; s=test; t=1303299145; bh=mjU2RAiTyESlXyrZVJPzov2uPzwYGCMBR4wMFPOce7c=; l=5100; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Content-Transfer-Encoding; b=WlhXff+70NBn+yH+Z+5OCx++Mnt8rgZSeYpCjlcYGns5GdVxeG/Mj5KN0ptjZbNL0 Y9rJFRZatTLnI6nsy/WVaeOI6QJF7BcTs7zI9qhMGFh09EiB1y7NNlf1RlqjTVv7eo YojsTaLWFy+7m5ZrfDCtFyX+qkHKcZj+0MT506Xs=
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; Wed, 20 Apr 2011 13:32:25 +0200 id 00000000005DC033.000000004DAEC449.00006474
Message-ID: <4DAEC449.1080803@tana.it>
Date: Wed, 20 Apr 2011 13:32:25 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.15) Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Politics and technology, was Call for a Jasmine Revolution
References: <69C307E5-8B96-4604-960B-3270B8D01D8D@softarmor.com>	<4CA7D36B-B8DE-431F-AEEB-57675B6951AD@mnot.net>	<877B733B-F1CB-4087-BE82-0A1B07623D24@softarmor.com>	<DEC3D7BB-0EDE-4584-B5A0-35C6F54CD2CC@mnot.net>	<D44303D5-288B-4A44-BD07-8D5A3059BE45@softarmor.com>	<4D88BEE2.90504@tana.it>	<6.2.5.6.2.20110322211644.0db72cf8@resistor.net>	<D85C5068-0F54-40D3-9A94-058C07894CFB@gmx.net>	<4DA36AEB.5010600@earthlink.net> <BANLkTikyw+CvFHxM3RFpjmvoc7+b+h1YHQ@mail.gmail.com>
In-Reply-To: <BANLkTikyw+CvFHxM3RFpjmvoc7+b+h1YHQ@mail.gmail.com>
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: Wed, 20 Apr 2011 11:32:28 -0000

On 12/Apr/11 18:31, Phillip Hallam-Baker wrote:
> Todd, 
> 
> This is totally confused and you are completely wrong.
>
>    Under the Federal Election Campaign Act
>    <http://en.wikipedia.org/wiki/Federal_Election_Campaign_Act>, an
>    organization becomes a "political committee" by receiving
>    contributions or making expenditures in excess of $1,000 for the
>    purpose of influencing a federal election
>    [Source Wikipedia]
> 
> Since neither the IETF nor ISOC has any interest in influencing a
> federal election, nor does it engage in any activity intended to do
> so, it is not a political committee under the terms of the act.

The way politics is currently being done is not necessarily adequate.

Let me just note that the root problem is that we are sharing this
planet among a few billions individuals.  That is certainly a
political problem.  However, given that communication is potentially
proportional to the square of the communicating parties, it is also a
technical problem.  I claim that it is not possible to neatly discern
between political and technical issues, although only one of those
two aspects appears to be dominant in many specific cases.  To
justify this claim, suffice it to say that the /amount/ of traffic
has a paramount physical limit, time, whose use cannot be regulated
by any single-sided approach --either political or technical, only.
For an example: spam.

Is it an only-technical problem to devise adequate means for politics?
For the reciprocal question, whether politics should intrude into
technology, the ISOC, talking about the IETF and similar bodies,
recommends that politics do not "assert any authority over those
organizations by any mechanism" [1].  So, how do we tackle spam and
similar issues where neither aspect is prevalent?

1. ISOC's response to NTIA request for comments on IANA functions
http://isoc.org/wp/newsletter/files/2011/03/Internet-Society-Response-Docket.pdf
30 March 2011
> On Mon, Apr 11, 2011 at 4:56 PM, todd glassey <tglassey@earthlink.net
> <mailto:tglassey@earthlink.net>> wrote:
> 
>     On 3/23/2011 12:02 AM, Hannes Tschofenig wrote:
> 
>         On Mar 23, 2011, at 6:52 AM, SM wrote:
> 
>             The IETF can only address the technical problems.
> 
>         This is an argument I often hear. I do, however, believe that
>         you cannot see technology in isolation.
> 
>     Yeah - sure you can... if you want to be totally about the
>     original design and practice of the IETF and its vision. It was
>     built to advance protocol standardization and not to decide what
>     protocols it would allow on the Internet and which it wouldn't.
>      But  lately many have forgotten this and are using the IETF as a
>     formal lobby for technological policy advancement and that's a no-no.
> 
>     Bluntly the IETF members are becoming more and more aggressively
>     politically and this statement is based on IAB and other
>     publication on what the IETF does and does not allow through its
>     frameworks. In doing so their statements about allowing protocols
>     or not allowing protocols to be standardized based on their stated
>     perception of "what damages the Internet" or what they personally
>     want to see as a "free access to all information and ideas" model,
>     creates a real serious divergence from the Standards Practice this
>     organization was set up as, and IMHO is one which is designed
>     clearly to destroy global Intellectual Property law and practice.
> 
>         However, in many cases the technology, regulatory environment,
>         business aspects, and the social context gets mixed together.
> 
>     No Hannes  - it doesn't unless the Chair allows it to - meaning
>     that the Chair in this instance has allowed political materials to
>     be fielded (filed in this instance) into the IETF and trust me I
>     am already filing a formal complaint with the Treasury about
>     ISOC's becoming a formal PAC and its locking out protocol efforts
>     based on its own desires therein...
> 
> 
>     http://tools.ietf.org/html/draft-morris-policy-cons-00
> 
> 
>     I suggest that the Chair immediately post a formal statement that
>     the IETF is a-political and will not do anything but standardize
>     technology.  Also that ONLY technology drafts can be accepted
>     since the IETF is part of ISOC and not registered as a political
>     PAC or Lobbying Agency which it clearly has become in direct
>     violation of the NTIA MOU which gave it (ISOC and its ARIN) the
>     real power.
> 
> 
>     Todd Glassey
> 
>     Please have a look at:
>     http://tools.ietf.org/html/draft-morris-policy-cons-00
> 
>         Ciao
>         Hannes
> 
> 
>     Hannes - this is the issue with the IETF and the gross number of
>     flaming idiots inside of it. The IETF is not a Social Reform
>     Agency, nor is it a freaking political action group since its
>     financial filings prevent this.
> 
>     Todd Glassey

From dhc2@dcrocker.net  Wed Apr 20 07:39:22 2011
Return-Path: <dhc2@dcrocker.net>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 9D26EE06C4 for <ietf@ietfc.amsl.com>; Wed, 20 Apr 2011 07:39:22 -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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jG6UC5c+Em0A for <ietf@ietfc.amsl.com>; Wed, 20 Apr 2011 07:39:19 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfc.amsl.com (Postfix) with ESMTP id AD4DAE0613 for <ietf@ietf.org>; Wed, 20 Apr 2011 07:39:19 -0700 (PDT)
Received: from [192.168.1.7] (adsl-67-127-56-68.dsl.pltn13.pacbell.net [67.127.56.68]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p3KEd8O6022628 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Wed, 20 Apr 2011 07:39:14 -0700
Message-ID: <4DAEF008.6040101@dcrocker.net>
Date: Wed, 20 Apr 2011 07:39:04 -0700
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Olaf Kolkman <olaf@nlnetlabs.nl>, Jon Peterson <jon.peterson@neustar.biz>,  Hannes Tschofenig <Hannes.Tschofenig@gmx.net>, Bernard Aboba <bernarda@microsoft.com>
Subject: Review of:  draft-iab-dns-applications-01
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]); Wed, 20 Apr 2011 07:39:14 -0700 (PDT)
Cc: IETF Discussion <ietf@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: Wed, 20 Apr 2011 14:39:22 -0000

Review --

Title:        Architectural Considerations on Application Features in the DNS
By:           Kolkman, Peterson, Tschofenig, Aboba
I-D:          draft-iab-dns-applications-01

Reviewer:     D. Crocker <dcrocker@bbiw.net>
Review Date:  20 April 2011




RFC 882:  DNS Concepts and Facilities (1982)
--------------------------------------------

    Need:
       The number of resources (for example mailboxes), the number of locations
       for resources, and the diversity of such an environment cause formidable
       problems when we wish to create consistent methods for referencing
       particular resources that are similar but scattered throughout the
       environment.
       ...
       The problem for computer mail is more severe.
       ...
       The basic need is for a consistent name space which will be
       used for referring to resources.

    Solution:
       The DOMAIN NAME SPACE, which is a specification for a tree
       structured name space.
       ...
       NAME SERVERS are server programs which hold information about
       the domain tree's structure and set information.
       ...
       RESOLVERS are programs that extract information from name
       servers in response to user requests.




Draft Summary
-------------

The DNS provides critical infrastructure service to the public Internet.
Proposed enhancements must have a "first do no harm" basis, with respect to
existing operations.  However, DNS capabilities and experiences already support
addition of new data and new types of data, so that all enhancements are not
equally suspect.

The draft lays out its goals in terms of a a set of increasing functional
demands being made, considered or possible by applications wishing to use the DNS:

      "Proposals to piggyback more sophisticated application behavior on top
       of the DNS, however, have raised questions about the propriety of
       instantiating some features in that way, especially those with
       security sensitivities."

This establishes the actual focus of the draft on fears of misuse, rather than
on guidance for proper enhancement.

It offers to explore "architectural consequences of installing application
features in the DNS" and to offer guidance for such efforts.  However it does
not explain what it means by "application features in the DNS", and it offers
little discussion and less substance about architecture or guidance.

The draft has four major sections.

    Motivations:

    This summarizes DNS background, goals and earlier enhancements. The section
demonstrates a misunderstanding of the basis and history of the DNS, forming its
premises from a simplistic and narrow assessment of popular DNS usage, rather
than from the service's design, as captured in the above RFC 882 text.  For
example the draft treats some features as unexpected enhancements when they were
part of the original vision.  The draft also appears to be unaware that mnemonic
host names were in use for more than 10 years before the DNS was defined and
that the primary motivations for the DNS were administration and operations
scaling, not merely the creation of symbolic names.  The statement that the
principal "purpose" of the DNS is to translate names to IP Addresses suggests
that the in-addr.arpa use and any use of CNAME do not represent principal
purposes.  The original DNS design discussion is in terms that are more generic
than this draft acknowledges. Hence the original use of "resource" rather than
the draft's focus on "host" and "address".


    Overview of DNS Applications Usages:

    This lays out three basic services, covering service lookup, transforming one
name into another using NAPTR or DDDS, and storage of arbitrary content.  The
draft appears to misunderstand that DDDS is an independent layered service,
which merely has a sub-component that is specified to map onto existing DNS
services.  Rather, the draft discusses it as if DDDS makes a change to the DNS.
It makes no change and there is nothing obvious in the design or operation
of the mapping component that will cause problems for the DNS.


    Challenges for the DNS:

    This lists service needs that might be problematic, covering compound queries
and including requester-specific responses, as well as "metadata about tree
structure", and domain redirection.  The first two have no apparent constituency
in current DNS work and discussion of the latter provides no explanation of the
substantive problems that supposedly would be caused.


    Principles and Guidance:

    This offers advice for the types of services that do and do not make sense
to attempt via the DNS. It postulates use of HTTP as an alternative, but without
any concrete design or operational experience. As always, untested and
unimplemented, hypothetical alternatives fare better in an analysis against
real-world ones, because they are not required to suffer real-world constraints
and costs nor to demonstrate real-world operational superiority.


In general, the document needs to be much more careful with technical terms and
statements. It has various inaccuracies about use of SRV RR, DNSSEC, zone,
authority and delegation concerning overlap dialing, and aspects of the Send-N
proposal.




Review
------

Broadly the document should be extremely careful to distinguish whether a
proposal would make changes to DNS protocol functions, data definitions,
administration, deployment, traffic and/or use.  It should draw clear lines
among these, versus changes that are actually to an application, which is merely
a client of the DNS and that requires nothing of the DNS but the addition of
more data using existing RRs.  This draft generally does not do that, and it is
the essential failure that permeates the draft.

Rather, the draft considers an enhancement that is a new way of using existing
DNS capabilities -- that is, one that makes no technical or operational changes
to the DNS -- to be a change to the DNS.  Although some such simple uses might
have detrimental operational effects, such as overloading a server or destroying
the utility of a cache, the draft makes almost no reference to these issues.
Generally, the draft conflates DNS usage with DNS internals.  It is equivalent
to saying that the DNS is changed by each, specific resource record that is
stored for each new name.

A document intending to give architectural advice needs to provide careful
citation or summary of the architecture and to link the advice it gives to that
architecture.  This draft does not do that.

It also needs to be careful to distinguish between DNS architecture and the
architecture of services that use the DNS, with particular focus on the
separable demands made by the latter on the former.  This draft does not do that.

For example it tends to cast the enhancements that are to be feared as moving
the DNS into being a "database" service, without carefully defining the
functional differences.  Historically, the most basic distinction that is drawn
between the DNS and typical database services is the functionality of the lookup
key.  For the DNS, the query string is used for an exact match.  For databases,
the string can be used for fuzzy searching.

Hence, the DNS is an exact-match mapping service whereas databases are
partial-match searching services. (It is unfortunate that many DNS documents do
use the term "search" since what is meant is simple mapping. There is also the
small confusion added by common resolver implementation behavior of "searching"
variations on a name, such as adding "www".)  The draft does raise the issue of
multi-attribute query key specification; this definitely is a characteristic
present for database services but not the DNS.  However there are no efforts to
make such a fundamental change to the DNS.  At best, the draft confuses schemes
for a layered encoding of multiple attributes into a normal DNS domain name,
with a proposal to change DNS internals.  The former uses existing DNS services
and represents stylized application conventions, not DNS changes.

If the draft is to be pragmatic when raising concerns, it should carefully
distinguish among proposals that have come from significant community effort,
random individuals, or from an abstract analysis that does not yet have any
real-world impetus.  This draft does not do that.  Hence there is no basis for
assessing the actual concern the reader should have; nor why the particular list
of the draft's concerns is included while possible concerns are not.

The draft should explore and substantiate possibilities of damaging the DNS's
models, limits or performance, in terms of the service's details for design,
protocol, data representation, operations or usage.  Will it affect clients or
servers, caches or long-term storage?  And so on.  This draft does not do that.

Finally the brief, summary effort to provide guidance that is at the end of the
draft only offers generic comments lacking technical detail.  It reduces to a
template for each concern in the form of "X might cause problems so be careful
about doing X."  Engineers need more substance to guidance they are given, and
they need it better integrated.




Recommendation
--------------

After writing this review, I was pointed to earlier comments on the previous
version of the draft:

    <http://trac.tools.ietf.org/group/iab/trac/ticket/22>

    <http://trac.tools.ietf.org/group/iab/trac/ticket/23>

Some of my own observations are redundant with theirs.  This means that their
concerns were not fixed in the latest draft, in spite of the trac tickets' being
closed.

Simply put, the draft needs a fresh start, beginning with clearer goals, better
organization, better attention to technical details, and much more substance to
its analyses.

If the primary purpose is to criticize sundry proposals made over the years --
or current ones now in play -- then it should be titled accordingly and it
should ensure that each criticism is substantial, substantiated and much more
carefully distinguishes how the DNS is affected.

If its primary purpose is to provide guidance for enhancement, then it needs
architectural rigor and, again, substantive analysis, including comparison of
tradeoffs.


d/





-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From bernard_aboba@hotmail.com  Wed Apr 20 07:55:52 2011
Return-Path: <bernard_aboba@hotmail.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id CC665E06E1; Wed, 20 Apr 2011 07:55:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.488
X-Spam-Level: 
X-Spam-Status: No, score=-102.488 tagged_above=-999 required=5 tests=[AWL=0.110, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I4l10DSnSVNl; Wed, 20 Apr 2011 07:55:51 -0700 (PDT)
Received: from blu0-omc1-s35.blu0.hotmail.com (blu0-omc1-s35.blu0.hotmail.com [65.55.116.46]) by ietfc.amsl.com (Postfix) with ESMTP id 86964E06AD; Wed, 20 Apr 2011 07:55:51 -0700 (PDT)
Received: from BLU152-W2 ([65.55.116.8]) by blu0-omc1-s35.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 20 Apr 2011 07:55:51 -0700
Message-ID: <BLU152-w2BA09DCB1336E2DDEF33E93930@phx.gbl>
Content-Type: multipart/alternative; boundary="_4df9682d-8165-4654-90d2-699137dbe4e5_"
X-Originating-IP: [98.203.198.61]
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: <scott.probasco@nokia.com>, <stephen.farrell@cs.tcd.ie>, <ietf@ietf.org>
Subject: RE: [paws] WG Review: Protocol to Access White Space database (paws)
Date: Wed, 20 Apr 2011 07:55:50 -0700
Importance: Normal
In-Reply-To: <88BE24FD9280884487DEAE0CE1FD3A5B060F1B@008-AM1MPN1-023.mgdnok.nokia.com>
References: <20110419165634.CD24CE07CF@ietfc.amsl.com>, <4DADFE6D.3050107@cs.tcd.ie>, <88BE24FD9280884487DEAE0CE1FD3A5B060F1B@008-AM1MPN1-023.mgdnok.nokia.com>
MIME-Version: 1.0
X-OriginalArrivalTime: 20 Apr 2011 14:55:51.0094 (UTC) FILETIME=[0A618D60:01CBFF6B]
Cc: paws@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: Wed, 20 Apr 2011 14:55:53 -0000

--_4df9682d-8165-4654-90d2-699137dbe4e5_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


When I hear the term "device identity spoofing"=2C IEEE 802.1ar comes to mi=
nd (see http://standards.ieee.org/getieee802/download/802.1AR.-2009.pdf). =
=20

In addition to the liaisons with IEEE 802.19=2C 802.22 and IEEE 802.11af=2C=
 is there a liaison contemplated to IEEE 802.1 relating to "device identity=
"?

> From: scott.probasco@nokia.com
> To: stephen.farrell@cs.tcd.ie=3B ietf@ietf.org
> Subject: RE: [paws] WG Review: Protocol to Access White Space database (p=
aws)
> Date: Wed=2C 20 Apr 2011 14:41:23 +0000
> CC: paws@ietf.org=3B iesg@ietf.org
>=20
> Hi Stephen=2C All=2C
>=20
> I believe the current wording
> >> Robust security mechanisms are required to prevent:
> >> device identity spoofing=2C modification of device requests=2C modific=
ation
> >> of channel enablement information=2C ...
> is acceptable because "mechanisms are required" means they should be in t=
he protocol=2C it does not mean they cannot be optional. PAWS should suppor=
t Regulator requirements globally=2C and thus I believe there will be proce=
dures or capabilities which are "required" to be in the protocol but will b=
e "optional" during run time. Thus different or conflicting requirements fr=
om different regions of the world can be supported. (Several regulatory gro=
ups around the world are still developing their views and requirements).
>=20
> It's not the time to dig deep into proposed solutions=2C just my opinion =
is the current proposed wording is an acceptable definition to allow a Work=
 Group to get started defining the details.
>=20
> Regards=2C
> Scott
>=20
> -----Original Message-----
> From: paws-bounces@ietf.org [mailto:paws-bounces@ietf.org] On Behalf Of e=
xt Stephen Farrell
> Sent: Tuesday=2C April 19=2C 2011 4:28 PM
> To: IETF-Discussion
> Cc: paws@ietf.org=3B iesg@ietf.org
> Subject: Re: [paws] WG Review: Protocol to Access White Space database (p=
aws)
>=20
>=20
> I think this is a good and timely thing for the IETF to do.
>=20
> One part of this where I think it might be useful to get
> some broader input (which may have happened already=2C I'm not
> sure) is the following:
>=20
> On 19/04/11 17:56=2C IESG Secretary wrote:
> > The protocol must protect both the channel enablement process and the
> > privacy of users.=20
>=20
> That part is fine but it goes on to say:
>=20
> > Robust security mechanisms are required to prevent:
> > device identity spoofing=2C modification of device requests=2C modifica=
tion
> > of channel enablement information=2C ...
>=20
> I'm told (and believe) this in response to (at least) US
> FCC requirements that call for a device ID and sometimes
> serial number to be (securely=2C for some value of securely)
> sent with the query.
>=20
> Those appear to be real regulatory requirements in the
> US=2C presumably so the regulator can stomp on someone who
> messes about in the wrong spectrum at the wrong time.
> (The link below [1] may be to the right or wrong bit of
> those US regulations=2C I'm not at all sure=2C not being
> from there=3B-)
>=20
> So my questions:
>=20
> Are there may be similar (or conflicting!) requirements
> elsewhere?
>=20
> Does this bit of the charter text need changes to work
> well for other regions?
>=20
> Separately=2C I'm not sure how to square those kinds of
> regulatory requirements with protecting privacy where the
> device is carried by a person and has some FCC device ID
> (which lots do I guess) and the person might not want
> the database operator to know who's asking. But I think
> that's ok as something for the WG to figure out since
> the charter already calls for respecting privacy.
>=20
> I'm more concerned in case e.g. some other regional regulation
> called for this protocol to be completely anonymous or
> something=2C in which case the current charter text might
> be problematic.
>=20
> Cheers=2C
> Stephen.
>=20
> [1]
> http://ecfr.gpoaccess.gov/cgi/t/text/text-idx?c=3Decfr&sid=3D3e9c322addf1=
f7e897d8c84a6c7aca78&rgn=3Ddiv8&view=3Dtext&node=3D47:1.0.1.1.14.8.243.9&id=
no=3D47
> _______________________________________________
> paws mailing list
> paws@ietf.org
> https://www.ietf.org/mailman/listinfo/paws
 		 	   		  =

--_4df9682d-8165-4654-90d2-699137dbe4e5_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Tahoma
}
--></style>
</head>
<body class=3D'hmmessage'>
When I hear the term "device identity spoofing"=2C IEEE 802.1ar comes to mi=
nd (see http://standards.ieee.org/getieee802/download/802.1AR.-2009.pdf).&n=
bsp=3B <br><br>In addition to the liaisons with IEEE 802.19=2C 802.22 and I=
EEE 802.11af=2C is there a liaison contemplated to IEEE 802.1 relating to "=
device identity"?<br><br>&gt=3B From: scott.probasco@nokia.com<br>&gt=3B To=
: stephen.farrell@cs.tcd.ie=3B ietf@ietf.org<br>&gt=3B Subject: RE: [paws] =
WG Review: Protocol to Access White Space database (paws)<br>&gt=3B Date: W=
ed=2C 20 Apr 2011 14:41:23 +0000<br>&gt=3B CC: paws@ietf.org=3B iesg@ietf.o=
rg<br>&gt=3B <br>&gt=3B Hi Stephen=2C All=2C<br>&gt=3B <br>&gt=3B I believe=
 the current wording<br>&gt=3B &gt=3B&gt=3B Robust security mechanisms are =
required to prevent:<br>&gt=3B &gt=3B&gt=3B device identity spoofing=2C mod=
ification of device requests=2C modification<br>&gt=3B &gt=3B&gt=3B of chan=
nel enablement information=2C ...<br>&gt=3B is acceptable because "mechanis=
ms are required" means they should be in the protocol=2C it does not mean t=
hey cannot be optional. PAWS should support Regulator requirements globally=
=2C and thus I believe there will be procedures or capabilities which are "=
required" to be in the protocol but will be "optional" during run time. Thu=
s different or conflicting requirements from different regions of the world=
 can be supported. (Several regulatory groups around the world are still de=
veloping their views and requirements).<br>&gt=3B <br>&gt=3B It's not the t=
ime to dig deep into proposed solutions=2C just my opinion is the current p=
roposed wording is an acceptable definition to allow a Work Group to get st=
arted defining the details.<br>&gt=3B <br>&gt=3B Regards=2C<br>&gt=3B Scott=
<br>&gt=3B <br>&gt=3B -----Original Message-----<br>&gt=3B From: paws-bounc=
es@ietf.org [mailto:paws-bounces@ietf.org] On Behalf Of ext Stephen Farrell=
<br>&gt=3B Sent: Tuesday=2C April 19=2C 2011 4:28 PM<br>&gt=3B To: IETF-Dis=
cussion<br>&gt=3B Cc: paws@ietf.org=3B iesg@ietf.org<br>&gt=3B Subject: Re:=
 [paws] WG Review: Protocol to Access White Space database (paws)<br>&gt=3B=
 <br>&gt=3B <br>&gt=3B I think this is a good and timely thing for the IETF=
 to do.<br>&gt=3B <br>&gt=3B One part of this where I think it might be use=
ful to get<br>&gt=3B some broader input (which may have happened already=2C=
 I'm not<br>&gt=3B sure) is the following:<br>&gt=3B <br>&gt=3B On 19/04/11=
 17:56=2C IESG Secretary wrote:<br>&gt=3B &gt=3B The protocol must protect =
both the channel enablement process and the<br>&gt=3B &gt=3B privacy of use=
rs. <br>&gt=3B <br>&gt=3B That part is fine but it goes on to say:<br>&gt=
=3B <br>&gt=3B &gt=3B Robust security mechanisms are required to prevent:<b=
r>&gt=3B &gt=3B device identity spoofing=2C modification of device requests=
=2C modification<br>&gt=3B &gt=3B of channel enablement information=2C ...<=
br>&gt=3B <br>&gt=3B I'm told (and believe) this in response to (at least) =
US<br>&gt=3B FCC requirements that call for a device ID and sometimes<br>&g=
t=3B serial number to be (securely=2C for some value of securely)<br>&gt=3B=
 sent with the query.<br>&gt=3B <br>&gt=3B Those appear to be real regulato=
ry requirements in the<br>&gt=3B US=2C presumably so the regulator can stom=
p on someone who<br>&gt=3B messes about in the wrong spectrum at the wrong =
time.<br>&gt=3B (The link below [1] may be to the right or wrong bit of<br>=
&gt=3B those US regulations=2C I'm not at all sure=2C not being<br>&gt=3B f=
rom there=3B-)<br>&gt=3B <br>&gt=3B So my questions:<br>&gt=3B <br>&gt=3B A=
re there may be similar (or conflicting!) requirements<br>&gt=3B elsewhere?=
<br>&gt=3B <br>&gt=3B Does this bit of the charter text need changes to wor=
k<br>&gt=3B well for other regions?<br>&gt=3B <br>&gt=3B Separately=2C I'm =
not sure how to square those kinds of<br>&gt=3B regulatory requirements wit=
h protecting privacy where the<br>&gt=3B device is carried by a person and =
has some FCC device ID<br>&gt=3B (which lots do I guess) and the person mig=
ht not want<br>&gt=3B the database operator to know who's asking. But I thi=
nk<br>&gt=3B that's ok as something for the WG to figure out since<br>&gt=
=3B the charter already calls for respecting privacy.<br>&gt=3B <br>&gt=3B =
I'm more concerned in case e.g. some other regional regulation<br>&gt=3B ca=
lled for this protocol to be completely anonymous or<br>&gt=3B something=2C=
 in which case the current charter text might<br>&gt=3B be problematic.<br>=
&gt=3B <br>&gt=3B Cheers=2C<br>&gt=3B Stephen.<br>&gt=3B <br>&gt=3B [1]<br>=
&gt=3B http://ecfr.gpoaccess.gov/cgi/t/text/text-idx?c=3Decfr&amp=3Bsid=3D3=
e9c322addf1f7e897d8c84a6c7aca78&amp=3Brgn=3Ddiv8&amp=3Bview=3Dtext&amp=3Bno=
de=3D47:1.0.1.1.14.8.243.9&amp=3Bidno=3D47<br>&gt=3B ______________________=
_________________________<br>&gt=3B paws mailing list<br>&gt=3B paws@ietf.o=
rg<br>&gt=3B https://www.ietf.org/mailman/listinfo/paws<br> 		 	   		  </bo=
dy>
</html>=

--_4df9682d-8165-4654-90d2-699137dbe4e5_--

From jmh@joelhalpern.com  Wed Apr 20 08:41:00 2011
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 5EC4DE07ED; Wed, 20 Apr 2011 08:41:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.498
X-Spam-Level: 
X-Spam-Status: No, score=-102.498 tagged_above=-999 required=5 tests=[AWL=0.101, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rejY80qsxMqn; Wed, 20 Apr 2011 08:40:59 -0700 (PDT)
Received: from hermes.out.tigertech.net (hermes.out.tigertech.net [74.114.88.72]) by ietfc.amsl.com (Postfix) with ESMTP id F3366E06C4; Wed, 20 Apr 2011 08:40:56 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.tigertech.net (Postfix) with ESMTP id 4ECAF430107; Wed, 20 Apr 2011 08:40:56 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hermes.tigertech.net
Received: from [10.10.10.101] (pool-71-161-50-206.clppva.btas.verizon.net [71.161.50.206]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by hermes.tigertech.net (Postfix) with ESMTPSA id 2BCD74300F7; Wed, 20 Apr 2011 08:40:55 -0700 (PDT)
Message-ID: <4DAEFE86.7030000@joelhalpern.com>
Date: Wed, 20 Apr 2011 11:40:54 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.15) Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: Bernard Aboba <bernard_aboba@hotmail.com>
Subject: Re: [paws] WG Review: Protocol to Access White Space database (paws)
References: <20110419165634.CD24CE07CF@ietfc.amsl.com>, <4DADFE6D.3050107@cs.tcd.ie>, <88BE24FD9280884487DEAE0CE1FD3A5B060F1B@008-AM1MPN1-023.mgdnok.nokia.com> <BLU152-w2BA09DCB1336E2DDEF33E93930@phx.gbl>
In-Reply-To: <BLU152-w2BA09DCB1336E2DDEF33E93930@phx.gbl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: paws@ietf.org, "iesg@ietf.org" <iesg@ietf.org>, ietf@ietf.org, scott.probasco@nokia.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: Wed, 20 Apr 2011 15:41:00 -0000

Building from Bernard's note, it strikes me that if we are going to get 
into device identity, we probably need to be communicating with (liaise) 
3GPP/3GPP2, because they have very strong views on that topic.  (Whether 
one agrees or disagrees with their biases, talking to them seems important.)

Yours,
Joel

On 4/20/2011 10:55 AM, Bernard Aboba wrote:
> When I hear the term "device identity spoofing", IEEE 802.1ar comes to
> mind (see http://standards.ieee.org/getieee802/download/802.1AR.-2009.pdf).
>
> In addition to the liaisons with IEEE 802.19, 802.22 and IEEE 802.11af,
> is there a liaison contemplated to IEEE 802.1 relating to "device identity"?
>

From paul@marvell.com  Tue Apr 19 12:54:14 2011
Return-Path: <paul@marvell.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 90A8FE07AD; Tue, 19 Apr 2011 12:54:14 -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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id on8-tvFxv1Fj; Tue, 19 Apr 2011 12:54:13 -0700 (PDT)
Received: from na3sys009aog105.obsmtp.com (na3sys009aog105.obsmtp.com [74.125.149.75]) by ietfc.amsl.com (Postfix) with ESMTP id 7A68CE079D; Tue, 19 Apr 2011 12:54:11 -0700 (PDT)
Received: from SC-OWA01.marvell.com ([65.219.4.129]) (using TLSv1) by na3sys009aob105.postini.com ([74.125.148.12]) with SMTP ID DSNKTa3oSvpUfpiTwaslA3MP0Ix3UND2oA3z@postini.com; Tue, 19 Apr 2011 12:54:12 PDT
Received: from SC-vEXCH2.marvell.com ([10.93.76.134]) by SC-OWA01.marvell.com ([10.93.76.21]) with mapi; Tue, 19 Apr 2011 12:47:43 -0700
From: Paul Lambert <paul@marvell.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>, "iesg@ietf.org" <iesg@ietf.org>,  IETF discussion list <ietf@ietf.org>, "paws@ietf.org" <paws@ietf.org>
Date: Tue, 19 Apr 2011 12:47:41 -0700
Subject: RE: [paws] WG Review: Protocol to Access White Space database (paws)
Thread-Topic: [paws] WG Review: Protocol to Access White Space database (paws)
Thread-Index: Acv+uedonCqyHha9TAGR+HDpqgU76wAECkWg
Message-ID: <7BAC95F5A7E67643AAFB2C31BEE662D01406AC564E@SC-VEXCH2.marvell.com>
References: <20110419165634.CD24CE07CF@ietfc.amsl.com> <4DADCB52.1020309@joelhalpern.com>
In-Reply-To: <4DADCB52.1020309@joelhalpern.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-Mailman-Approved-At: Wed, 20 Apr 2011 08:52:24 -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: Tue, 19 Apr 2011 19:54:14 -0000

How does the area that the group is assigned impact the choices of technolo=
gy?

I'm an advocate for an efficient solution set for PAWS ... it will be much =
like DNS for spectrum in the future and should be viewed as a core infrastr=
uctural component that needs careful design.  There are good reasons that r=
outing protocols don't use XML.

Applications now days tend to go for the simple, quick to make a web applic=
ation solutions using XML or the like ...  My concern is that "Applications=
" imply that efficiency does not matter.

Paul



> -----Original Message-----
> From: paws-bounces@ietf.org [mailto:paws-bounces@ietf.org] On Behalf Of
> Joel M. Halpern
> Sent: Tuesday, April 19, 2011 10:50 AM
> To: iesg@ietf.org
> Cc: paws@ietf.org; IETF discussion list
> Subject: Re: [paws] WG Review: Protocol to Access White Space database
> (paws)
>=20
> I think this working group is a good idea.
> My inclination would be to place it in the Applications area.  It looks
> like a nice application protocol to me.
> There is a reasonable argument for placing it in RAI, as that is where
> the relevant GEOLOC work has been done up till now.
>=20
> Yours,
> Joel M. Halpern
>=20
> On 4/19/2011 12:56 PM, IESG Secretary wrote:
> > A new IETF working group has been proposed.  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@ietf.org) by Tuesday, April 26, 2011.
> >
> >
> > Protocol to Access White Space database (paws)
> > ------------------------------------------------
> > Current Status: Proposed Working Group
> > Last updated: 2011-04-14
> >
> > Chairs:
> > TBD
> >
> > Area Directors:
> > TBD
> >
> > Area Advisor:
> > TBD
> >
> > Mailing lists:
> > Address: paws@ietf.org
> > To Subscribe: https://www.ietf.org/mailman/listinfo/paws
> > Archive: http://www.ietf.org/mail-archive/web/paws/
> >
> > Description of Working Group:
> >
> > Governments around the world continue to search for new pieces of
> radio
> > spectrum which can be used by the expanding wireless communications
> > industry to provide more services in the usable spectrum. The concept
> > of allowing secondary transmissions (licensed or unlicensed) in
> > frequencies allocated to a primary user is a technique to "unlock"
> > existing spectrum for new use. An obvious requirement is that these
> > secondary transmissions do not interfere with the primary use of the
> > spectrum. Often, in a given physical location, the primary user(s)
> may
> > not be using the entire band allocated to them. The available
> spectrum
> > for a secondary use would then depend on the location of the
> secondary
> > user. The primary user may have a schedule when it uses the spectrum,
> > which may be available for secondary use outside that schedule. The
> > fundamental issue is how to determine for a specific location and
> > specific time, if any of the primary spectrum is available for
> secondary
> > use. One simple mechanism is to use a geospatial database that
> records
> > protected contours for primary users, and require the secondary users
> to
> > check the database prior to selecting what part of the spectrum they
> > use. Such databases could be available on the Internet for query by
> > users.
> >
> > In a typical implementation of geolocation and database to access TV
> > white space, a radio is configured with, or has the capability to
> > determine its location in latitude and longitude. At power-on, before
> > the device can transmit or use any of the spectrum set aside for
> > secondary use, the device must identify the relevant database to
> query,
> > contact the database, provide its geolocation and receive in return a
> > list of unoccupied or "white space" spectrum (for example, in a TV
> > White space implementation, the list of available channels at that
> > location). The device can then select one of the channels from the
> list
> > and begin to transmit and receive on the selected channel. The device
> > must query the database subsequently on a periodic basis for a list
> of
> > unoccupied channels based on certain conditions, e.g. a fixed amount
> of
> > time has passed or the device has changed location beyond a specified
> > threshold.
> >
> > The databases are expected to be reachable via the Internet and the
> > devices querying these databases are expected to have some form of
> > Internet connectivity, directly or indirectly. The databases may be
> > country specific since the available spectrum and regulations may
> vary,
> > but the fundamental operation of the protocol should be country
> > independent, thus extensibility of data structures will be required.
> The
> > solution will not be tied to any specific spectrum, country, or
> > phy/mac/air interface but may incorporate relevant aspects of these
> as
> > needed for proper operation.
> >
> > The proposed working group will :
> > - standardize a protocol for querying the database, which includes a
> > location sensitive database discovery mechanism and security for the
> > protocol, and application services.
> > - Standardize the data structure to be carried by the query
> > protocol.
> >
> > The protocol must protect both the channel enablement process and the
> > privacy of users. Robust security mechanisms are required to prevent:
> > device identity spoofing, modification of device requests,
> modification
> > of channel enablement information, impersonation of registered
> database
> > services and unauthorized disclosure of a users location.
> >
> > Existing IETF location data structures and privacy mechanisms may be
> > considered for use. The WG will also investigate the need for other
> > mechanisms and related protocols to the White Space DB.
> >
> > The Working Group will set up and maintain appropriate contact and
> > liaison with other relevant standards bodies and groups, including
> IEEE
> > 802.11af and IEEE 802.22 to begin with. The working group may also
> > consider input from regulatory entities that are involved in the
> > specification of the rules for secondary use of spectrum in specific
> > bands.
> >
> > Goals and Milestones
> >
> > Sep 2011  Submit 'Requirements and Framework' to the IESG for
> >            publication as Informational
> >
> > Apr 2012  Submit 'Protocol for Querying a Whitespace Database' to
> >            the IESG for publication as Proposed Standard
> >
> > Apr 2012  Submit 'Data Model for Whitespace query protocol' to the
> >            IESG for publication as Proposed Standard
> > _______________________________________________
> > paws mailing list
> > paws@ietf.org
> > https://www.ietf.org/mailman/listinfo/paws
> >
> _______________________________________________
> paws mailing list
> paws@ietf.org
> https://www.ietf.org/mailman/listinfo/paws

From budden@nps.edu  Tue Apr 19 14:21:48 2011
Return-Path: <budden@nps.edu>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id BCCB1E086D; Tue, 19 Apr 2011 14:21: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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 08+O1NcnVvdO; Tue, 19 Apr 2011 14:21:47 -0700 (PDT)
Received: from diamond.nps.edu (diamond.nps.edu [205.155.65.226]) by ietfc.amsl.com (Postfix) with ESMTP id 694C7E089C; Tue, 19 Apr 2011 14:21:46 -0700 (PDT)
Received: from virginia.nps.edu ([205.155.65.26]) by diamond.nps.edu with Microsoft SMTPSVC(6.0.3790.4675); Tue, 19 Apr 2011 14:21:44 -0700
Received: from SKYTRAIN.ern.nps.edu ([172.20.24.112]) by virginia.nps.edu with Microsoft SMTPSVC(6.0.3790.4675); Tue, 19 Apr 2011 14:21:44 -0700
Received: from GULFSTREAM.ern.nps.edu (172.20.24.113) by skytrain.ern.nps.edu (172.20.24.112) with Microsoft SMTP Server (TLS) id 14.1.270.1; Tue, 19 Apr 2011 14:21:43 -0700
Received: from [172.20.58.67] (172.20.58.67) by smtp.nps.edu (172.20.24.113) with Microsoft SMTP Server (TLS) id 14.1.270.1; Tue, 19 Apr 2011 14:21:43 -0700
Subject: Re: [paws] WG Review: Protocol to Access White Space database (paws)
From: Rex Buddenberg <budden@nps.navy.mil>
To: Paul Lambert <paul@marvell.com>
In-Reply-To: <7BAC95F5A7E67643AAFB2C31BEE662D01406AC564E@SC-VEXCH2.marvell.com>
References: <20110419165634.CD24CE07CF@ietfc.amsl.com> <4DADCB52.1020309@joelhalpern.com> <7BAC95F5A7E67643AAFB2C31BEE662D01406AC564E@SC-VEXCH2.marvell.com>
Content-Type: text/plain; charset="UTF-8"
Date: Tue, 19 Apr 2011 14:21:39 -0700
Message-ID: <1303248099.2209.105.camel@localhost.localdomain>
MIME-Version: 1.0
X-Mailer: Evolution 2.32.2 (2.32.2-1.fc14) 
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 19 Apr 2011 21:21:44.0319 (UTC) FILETIME=[C85D90F0:01CBFED7]
X-Mailman-Approved-At: Wed, 20 Apr 2011 08:52:24 -0700
Cc: "paws@ietf.org" <paws@ietf.org>, "iesg@ietf.org" <iesg@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, 19 Apr 2011 21:21:48 -0000

On Tue, 2011-04-19 at 12:47 -0700, Paul Lambert wrote:
> 
> How does the area that the group is assigned impact the choices of
> technology?
> 
> I'm an advocate for an efficient solution set for PAWS ... it will be
> much like DNS for spectrum in the future and should be viewed as a
> core infrastructural component that needs careful design.  There are
> good reasons that routing protocols don't use XML.

While the DNS analogy works, I was thinking more a parallel -- or
extension -- of SNMP.  

Still remain within 'applications', Joel?

> 
> Applications now days tend to go for the simple, quick to make a web
> application solutions using XML or the like ...  My concern is that
> "Applications" imply that efficiency does not matter.
> 
> Paul
> 
> 
> 
> > -----Original Message-----
> > From: paws-bounces@ietf.org [mailto:paws-bounces@ietf.org] On Behalf Of
> > Joel M. Halpern
> > Sent: Tuesday, April 19, 2011 10:50 AM
> > To: iesg@ietf.org
> > Cc: paws@ietf.org; IETF discussion list
> > Subject: Re: [paws] WG Review: Protocol to Access White Space database
> > (paws)
> > 
> > I think this working group is a good idea.
> > My inclination would be to place it in the Applications area.  It looks
> > like a nice application protocol to me.
> > There is a reasonable argument for placing it in RAI, as that is where
> > the relevant GEOLOC work has been done up till now.
> > 
> > Yours,
> > Joel M. Halpern
> > 
> > On 4/19/2011 12:56 PM, IESG Secretary wrote:
> > > A new IETF working group has been proposed.  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@ietf.org) by Tuesday, April 26, 2011.
> > >
> > >
> > > Protocol to Access White Space database (paws)
> > > ------------------------------------------------
> > > Current Status: Proposed Working Group
> > > Last updated: 2011-04-14
> > >
> > > Chairs:
> > > TBD
> > >
> > > Area Directors:
> > > TBD
> > >
> > > Area Advisor:
> > > TBD
> > >
> > > Mailing lists:
> > > Address: paws@ietf.org
> > > To Subscribe: https://www.ietf.org/mailman/listinfo/paws
> > > Archive: http://www.ietf.org/mail-archive/web/paws/
> > >
> > > Description of Working Group:
> > >
> > > Governments around the world continue to search for new pieces of
> > radio
> > > spectrum which can be used by the expanding wireless communications
> > > industry to provide more services in the usable spectrum. The concept
> > > of allowing secondary transmissions (licensed or unlicensed) in
> > > frequencies allocated to a primary user is a technique to "unlock"
> > > existing spectrum for new use. An obvious requirement is that these
> > > secondary transmissions do not interfere with the primary use of the
> > > spectrum. Often, in a given physical location, the primary user(s)
> > may
> > > not be using the entire band allocated to them. The available
> > spectrum
> > > for a secondary use would then depend on the location of the
> > secondary
> > > user. The primary user may have a schedule when it uses the spectrum,
> > > which may be available for secondary use outside that schedule. The
> > > fundamental issue is how to determine for a specific location and
> > > specific time, if any of the primary spectrum is available for
> > secondary
> > > use. One simple mechanism is to use a geospatial database that
> > records
> > > protected contours for primary users, and require the secondary users
> > to
> > > check the database prior to selecting what part of the spectrum they
> > > use. Such databases could be available on the Internet for query by
> > > users.
> > >
> > > In a typical implementation of geolocation and database to access TV
> > > white space, a radio is configured with, or has the capability to
> > > determine its location in latitude and longitude. At power-on, before
> > > the device can transmit or use any of the spectrum set aside for
> > > secondary use, the device must identify the relevant database to
> > query,
> > > contact the database, provide its geolocation and receive in return a
> > > list of unoccupied or "white space" spectrum (for example, in a TV
> > > White space implementation, the list of available channels at that
> > > location). The device can then select one of the channels from the
> > list
> > > and begin to transmit and receive on the selected channel. The device
> > > must query the database subsequently on a periodic basis for a list
> > of
> > > unoccupied channels based on certain conditions, e.g. a fixed amount
> > of
> > > time has passed or the device has changed location beyond a specified
> > > threshold.
> > >
> > > The databases are expected to be reachable via the Internet and the
> > > devices querying these databases are expected to have some form of
> > > Internet connectivity, directly or indirectly. The databases may be
> > > country specific since the available spectrum and regulations may
> > vary,
> > > but the fundamental operation of the protocol should be country
> > > independent, thus extensibility of data structures will be required.
> > The
> > > solution will not be tied to any specific spectrum, country, or
> > > phy/mac/air interface but may incorporate relevant aspects of these
> > as
> > > needed for proper operation.
> > >
> > > The proposed working group will :
> > > - standardize a protocol for querying the database, which includes a
> > > location sensitive database discovery mechanism and security for the
> > > protocol, and application services.
> > > - Standardize the data structure to be carried by the query
> > > protocol.
> > >
> > > The protocol must protect both the channel enablement process and the
> > > privacy of users. Robust security mechanisms are required to prevent:
> > > device identity spoofing, modification of device requests,
> > modification
> > > of channel enablement information, impersonation of registered
> > database
> > > services and unauthorized disclosure of a users location.
> > >
> > > Existing IETF location data structures and privacy mechanisms may be
> > > considered for use. The WG will also investigate the need for other
> > > mechanisms and related protocols to the White Space DB.
> > >
> > > The Working Group will set up and maintain appropriate contact and
> > > liaison with other relevant standards bodies and groups, including
> > IEEE
> > > 802.11af and IEEE 802.22 to begin with. The working group may also
> > > consider input from regulatory entities that are involved in the
> > > specification of the rules for secondary use of spectrum in specific
> > > bands.
> > >
> > > Goals and Milestones
> > >
> > > Sep 2011  Submit 'Requirements and Framework' to the IESG for
> > >            publication as Informational
> > >
> > > Apr 2012  Submit 'Protocol for Querying a Whitespace Database' to
> > >            the IESG for publication as Proposed Standard
> > >
> > > Apr 2012  Submit 'Data Model for Whitespace query protocol' to the
> > >            IESG for publication as Proposed Standard
> > > _______________________________________________
> > > paws mailing list
> > > paws@ietf.org
> > > https://www.ietf.org/mailman/listinfo/paws
> > >
> > _______________________________________________
> > paws mailing list
> > paws@ietf.org
> > https://www.ietf.org/mailman/listinfo/paws
> _______________________________________________
> paws mailing list
> paws@ietf.org
> https://www.ietf.org/mailman/listinfo/paws



From scott.probasco@nokia.com  Wed Apr 20 07:41:40 2011
Return-Path: <scott.probasco@nokia.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 80C48E070D; Wed, 20 Apr 2011 07:41:40 -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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tMCKg8CryHS9; Wed, 20 Apr 2011 07:41:39 -0700 (PDT)
Received: from mgw-sa01.nokia.com (smtp.nokia.com [147.243.1.47]) by ietfc.amsl.com (Postfix) with ESMTP id 49632E0705; Wed, 20 Apr 2011 07:41:38 -0700 (PDT)
Received: from vaebh104.NOE.Nokia.com (vaebh104.europe.nokia.com [10.160.244.30]) by mgw-sa01.nokia.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p3KEfS9D020329; Wed, 20 Apr 2011 17:41:34 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.7]) by vaebh104.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 20 Apr 2011 17:41:33 +0300
Received: from 008-AM1MMR1-001.mgdnok.nokia.com (65.54.30.56) by NOK-AM1MHUB-03.mgdnok.nokia.com (65.54.30.7) with Microsoft SMTP Server (TLS) id 8.2.255.0; Wed, 20 Apr 2011 16:41:24 +0200
Received: from 008-AM1MPN1-023.mgdnok.nokia.com ([169.254.3.210]) by 008-AM1MMR1-001.mgdnok.nokia.com ([65.54.30.56]) with mapi id 14.01.0289.008; Wed, 20 Apr 2011 16:41:24 +0200
From: <scott.probasco@nokia.com>
To: <stephen.farrell@cs.tcd.ie>, <ietf@ietf.org>
Subject: RE: [paws] WG Review: Protocol to Access White Space database (paws)
Thread-Topic: [paws] WG Review: Protocol to Access White Space database (paws)
Thread-Index: AQHL/rLA5Czj0i0wfE+ujEk1m1AO2ZRlknOAgAE/lXA=
Date: Wed, 20 Apr 2011 14:41:23 +0000
Message-ID: <88BE24FD9280884487DEAE0CE1FD3A5B060F1B@008-AM1MPN1-023.mgdnok.nokia.com>
References: <20110419165634.CD24CE07CF@ietfc.amsl.com> <4DADFE6D.3050107@cs.tcd.ie>
In-Reply-To: <4DADFE6D.3050107@cs.tcd.ie>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-titus-version: 3.2.55
x-tituslabs-classifications-30: TLPropertyRoot=Trial License;Classification=Personal;
x-putclassificationandsendinfointox-header: Classification: Personal Project: Subject: RE: [paws] WG Review: Protocol to Access White Space database (paws) Sender Name: Probasco Scott (Nokia-CIC/Dallas) Sender Email: scott.probasco@nokia.com Send Date: Wednesday, April 20, 2011 Send Time: 9:41:21 AM
x-originating-ip: [172.19.60.53]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 20 Apr 2011 14:41:33.0088 (UTC) FILETIME=[0AF83A00:01CBFF69]
X-Nokia-AV: Clean
X-Mailman-Approved-At: Wed, 20 Apr 2011 08:52:24 -0700
Cc: paws@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 Apr 2011 14:41:40 -0000

Hi Stephen, All,

I believe the current wording
>> Robust security mechanisms are required to prevent:
>> device identity spoofing, modification of device requests, modification
>> of channel enablement information, ...
is acceptable because "mechanisms are required" means they should be in the=
 protocol, it does not mean they cannot be optional. PAWS should support Re=
gulator requirements globally, and thus I believe there will be procedures =
or capabilities which are "required" to be in the protocol but will be "opt=
ional" during run time. Thus different or conflicting requirements from dif=
ferent regions of the world can be supported. (Several regulatory groups ar=
ound the world are still developing their views and requirements).

It's not the time to dig deep into proposed solutions, just my opinion is t=
he current proposed wording is an acceptable definition to allow a Work Gro=
up to get started defining the details.

Regards,
Scott

-----Original Message-----
From: paws-bounces@ietf.org [mailto:paws-bounces@ietf.org] On Behalf Of ext=
 Stephen Farrell
Sent: Tuesday, April 19, 2011 4:28 PM
To: IETF-Discussion
Cc: paws@ietf.org; iesg@ietf.org
Subject: Re: [paws] WG Review: Protocol to Access White Space database (paw=
s)


I think this is a good and timely thing for the IETF to do.

One part of this where I think it might be useful to get
some broader input (which may have happened already, I'm not
sure) is the following:

On 19/04/11 17:56, IESG Secretary wrote:
> The protocol must protect both the channel enablement process and the
> privacy of users.=20

That part is fine but it goes on to say:

> Robust security mechanisms are required to prevent:
> device identity spoofing, modification of device requests, modification
> of channel enablement information, ...

I'm told (and believe) this in response to (at least) US
FCC requirements that call for a device ID and sometimes
serial number to be (securely, for some value of securely)
sent with the query.

Those appear to be real regulatory requirements in the
US, presumably so the regulator can stomp on someone who
messes about in the wrong spectrum at the wrong time.
(The link below [1] may be to the right or wrong bit of
those US regulations, I'm not at all sure, not being
from there;-)

So my questions:

Are there may be similar (or conflicting!) requirements
elsewhere?

Does this bit of the charter text need changes to work
well for other regions?

Separately, I'm not sure how to square those kinds of
regulatory requirements with protecting privacy where the
device is carried by a person and has some FCC device ID
(which lots do I guess) and the person might not want
the database operator to know who's asking. But I think
that's ok as something for the WG to figure out since
the charter already calls for respecting privacy.

I'm more concerned in case e.g. some other regional regulation
called for this protocol to be completely anonymous or
something, in which case the current charter text might
be problematic.

Cheers,
Stephen.

[1]
http://ecfr.gpoaccess.gov/cgi/t/text/text-idx?c=3Decfr&sid=3D3e9c322addf1f7=
e897d8c84a6c7aca78&rgn=3Ddiv8&view=3Dtext&node=3D47:1.0.1.1.14.8.243.9&idno=
=3D47
_______________________________________________
paws mailing list
paws@ietf.org
https://www.ietf.org/mailman/listinfo/paws

From sm@resistor.net  Wed Apr 20 09:11:48 2011
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 99724E0745 for <ietf@ietfc.amsl.com>; Wed, 20 Apr 2011 09:11:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.064
X-Spam-Level: 
X-Spam-Status: No, score=-102.064 tagged_above=-999 required=5 tests=[AWL=-0.534, BAYES_00=-2.599, DATE_IN_PAST_06_12=1.069, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id znqVb2-fTFOq for <ietf@ietfc.amsl.com>; Wed, 20 Apr 2011 09:11:46 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfc.amsl.com (Postfix) with ESMTP id 96CC2E0681 for <ietf@ietf.org>; Wed, 20 Apr 2011 09:11:45 -0700 (PDT)
Received: from sm-THINK.resistor.net (IDENT:sm@localhost [127.0.0.1]) by mx.elandsys.com (8.14.4/8.14.5.Beta0) with ESMTP id p3KGBVnw020245;  Wed, 20 Apr 2011 09:11:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1303315897; bh=FXeIlHhvTetB8i+E3DT9fNUmGKONfsk55+EAeGPYVrU=; h=Message-Id:X-Mailer:Date:To:From:Subject:Cc:In-Reply-To: References:Mime-Version:Content-Type; b=u7NN0/eG4sq0HMuBgEEEM2a9AsL2X9OBJTpajBMDrD1L1cUc9fdqcXNfXq9ev+wVf z4TS/rfmf6vLdj8fUq8C5hb//+IzN0tEk7JvDMdCoe2t2fI4i86ZwdAEqD/dXr752y VMOmuGaKa71N6EWO6okWzTCbTOuAXdBl4mveh8AI=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1303315897; bh=FXeIlHhvTetB8i+E3DT9fNUmGKONfsk55+EAeGPYVrU=; h=Message-Id:X-Mailer:Date:To:From:Subject:Cc:In-Reply-To: References:Mime-Version:Content-Type; b=xSWPXrf9KjkZcanjwixnI5MN0+CiSTBCoiexVOr1Z1ywcl5Ma9pDRUEoIbUpm9UqI 2uExhA6WvckifSW3tcTFxBONjF130F7A0ZRuJ5sP6QhsNVDrsfH/ckEKdYY6m6Jy7t UjlpWWqTyR3B07/+FtfpakxxLhxSBltuTDTwcfyw=
Message-Id: <6.2.5.6.2.20110419161215.03d496a0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 20 Apr 2011 02:13:14 -0700
To: Bob Hinden <bob.hinden@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: IAOC: delegating ex-officio responsibility
In-Reply-To: <90F3E256-88F5-4DCF-A64B-EF7FDDE667C8@gmail.com>
References: <2BE582FA-2682-4232-9D83-23A03F01A0DB@NLnetLabs.nl> <6.2.5.6.2.20110330073936.0e1899d0@resistor.net> <E2E41FDE-3818-4513-9933-CB1E0326B43E@nlnetlabs.nl> <6.2.5.6.2.20110330113947.0c948bc0@resistor.net> <4D942843.4060804@gmail.com> <6.2.5.6.2.20110331120351.09488990@resistor.net> <4D955661.8050502@gmail.com> <9C81C0F6-3ABE-4479-8C5E-C20C486D052A@gmail.com> <82A347CC-BB19-4A73-8E8A-924FBAA92A5F@NLnetLabs.nl> <84D6568B-18C9-47B2-A457-C51C2FB3351F@gmail.com> <5419FA805EF52E79D7822966@PST.JCK.COM> <DAC0FFD9-9B3B-4726-B56B-5E9BE5A5F1D1@gmail.com> <4DA8685F.5050504@dcrocker.net> <D0674791-3D7C-4B90-8189-A895715B977A@gmail.com> <6.2.5.6.2.20110419080338.0301b940@resistor.net> <90F3E256-88F5-4DCF-A64B-EF7FDDE667C8@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: Bob Hinden <bob.hinden@gmail.com>, 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, 20 Apr 2011 16:11:48 -0000

Hi Bob,
At 14:04 19-04-2011, Bob Hinden wrote:
>But that may not always be the case that all IAOC members have a lot 
>of IETF experience.  We need to have a governance model that works 
>into the future.

Yes, it may happen that some IAOC members may not have a lot of IETF 
experience.  How do you ensure that the IAOC members have a lot of 
IETF experience?  You can tweak the governance model.  The IETF 
community also have to be convinced that it is the better model or 
else it will be changed.  There are some safeguards in the IETF model 
that I won't get into.  It's merely a matter of time for that to 
change.  I'll list the names of the people who have participated on 
this thread:

  Dave Crocker
  Lucy Lynch
  John Klensin
  Russ Housley
  Jari Arkko
  Olaf Kolkman
  Brian Carpenter
  Henk Uijterwaal
  Leslie Daigle
  Ole Jacobsen
  Marshall Eubanks
  Joe Touch
  Joel Jaeggli
  Steve Crocker
  Michael Richardson
  Barry Leiba
  Spencer Dawkins
  Bert Wijnen

The people listed below were part of NomCom:

  Gregory Cauchie
  Mehmet Ersue
  Dorothy Gellert
  Tony Hansen
  Suresh Krishnan
  Dirk Kroeselberg
  Jan Seedorf
  Pete St. Pierre
  Rolf Winter

You may notice that there isn't any intersection with the previous list.

>It would certainly give the IAOC chair a broader view, but still not 
>the views of the I* chair.  Also, if the I* chairs (3 of 9 voting 
>members) regularly didn't attend, it would be much harder to get a 
>quorum for a meeting and pass motions.

I did not comment on getting a quorum previously as it's only adding 
one more problem to the mix.  "The IAOC decides the details about its 
decision-making rules, including its rules for quorum, conflict of 
interest, and breaking of ties".

I agree with you that the views of the I* Chairs are important.  It 
also helps avoid back and forth discussion between I* bodies; e.g. is 
this an IESG decision or can the IAOC decide.  I don't think that the 
IAB or the IESG can be absolved from the responsibility if the IAOC 
takes a negative turn as each of them chooses an IAOC member.

If the ex-IAB Chair and the IESG Chair ask for a change to the model 
due to the workload, is it on a whim?  This is where people walk away 
from a problem because they tried and got stone-walled.  If the IETF 
believes that it is appropriate to mince everything they can get out 
of a person in the name of good governance, so be it.

Regards,
-sm 


From dhc2@dcrocker.net  Wed Apr 20 09:37:28 2011
Return-Path: <dhc2@dcrocker.net>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id A54C4E0756 for <ietf@ietfc.amsl.com>; Wed, 20 Apr 2011 09:37:28 -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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bgHyXSpv-tSf for <ietf@ietfc.amsl.com>; Wed, 20 Apr 2011 09:37:27 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfc.amsl.com (Postfix) with ESMTP id B1C90E074C for <ietf@ietf.org>; Wed, 20 Apr 2011 09:37:27 -0700 (PDT)
Received: from [192.168.1.7] (adsl-67-127-56-68.dsl.pltn13.pacbell.net [67.127.56.68]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p3KGbJiI017314 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Wed, 20 Apr 2011 09:37:25 -0700
Message-ID: <4DAF0BBB.4060001@dcrocker.net>
Date: Wed, 20 Apr 2011 09:37:15 -0700
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Bob Hinden <bob.hinden@gmail.com>
Subject: Re: IAOC: delegating ex-officio responsibility
References: <2BE582FA-2682-4232-9D83-23A03F01A0DB@NLnetLabs.nl>	<6.2.5.6.2.20110330073936.0e1899d0@resistor.net>	<E2E41FDE-3818-4513-9933-CB1E0326B43E@nlnetlabs.nl>	<6.2.5.6.2.20110330113947.0c948bc0@resistor.net>	<4D942843.4060804@gmail.com>	<6.2.5.6.2.20110331120351.09488990@resistor.net>	<4D955661.8050502@gmail.com>	<9C81C0F6-3ABE-4479-8C5E-C20C486D052A@gmail.com>	<82A347CC-BB19-4A73-8E8A-924FBAA92A5F@NLnetLabs.nl>	<84D6568B-18C9-47B2-A457-C51C2FB3351F@gmail.com>	<5419FA805EF52E79D7822966@PST.JCK.COM> <DAC0FFD9-9B3B-4726-B56B-5E9BE5A5F1D1@gmail.com> <4DA8685F.5050504@dcrocker.net> <D0674791-3D7C-4B90-8189-A895715B977A@gmail.com> <4DADC758.2080906@dcrocker.net> <7D0E8BCB-194D-4FA1-ABDA-2F3175BA9441@gmail.com>
In-Reply-To: <7D0E8BCB-194D-4FA1-ABDA-2F3175BA9441@gmail.com>
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]); Wed, 20 Apr 2011 09:37:25 -0700 (PDT)
Cc: IETF Discussion <ietf@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: Wed, 20 Apr 2011 16:37:28 -0000

On 4/19/2011 12:53 PM, Bob Hinden wrote:
>> 1. ISOC, IAB and IESG each appoint one person currently.  Change this to be
>> two each, the same as Nomcom.  Each year, they would appoint one person.
>>
>> 2. Move the I* Chairs to be non-voting ex-officio participants, the same as
>> the IETF Administrative Director.  They are welcome to participate or be
>> explicitly invited to all IAOC/Trust activities.
>>
>> This produces the continuity that is needed for the admin work, but also
>> retains access to the expertise of the I* chairs.
>
> I don't agree.  Appointing two people (or more?) doesn't solve the problem I
> am concerned about, it still doesn't bring the chairs perspective.  It also
> significantly changes the governance model by changing the balance between
> between nomcom, iab, iesg, and ISOC appointed members.  Also, adding six
> people (still counting the chairs) will make the IAOC much larger and
> unwieldy.


For clarification:

1.  The IAB, IESG and ISOC each put two voting people onto the IAOC/Trust today. 
  My proposal preserves that.

2. The intent behind moving the I* Chairs to non-voting status, like the IAD, is 
to ensure that they can continue to participate but remove from the the 
requirement for daily IAOC/Trust activities.  The presumption is that they dive 
in for the big stuff, of the sort you cited, but do not have the burden of 
regular participation.

For emphasis:

As SM notes, my starting point is two of these folk saying they have to have a 
change.  Looking at the list of their duties, no one should be surprised that 
they feel (and are) overloaded.  So, they looked over their current duties and 
decided this is the one they'd like to change.  I don't have -- and haven't 
heard anyone else suggest -- that some other change in their duties would be 
more appropriate.  So I see the relevant question as how to make a change, not 
whether.

d/

ps. As for the broader concern about having a sufficient base of experience on 
the IAOC/Trust, that applies for all appointments to all of our management 
groups.  Worse, we have a continuing challenge to select for the right kinds of 
experience.  For example, merely hanging around the IETF for a long time does 
not mean one knows how to manage an area or manage a budget.  (I'm stating the 
obvious.  The reason is that I don't see the current effort to change I* Chair 
participation in the IAOC/Trust as changing this issue.)

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From john@jlc.net  Wed Apr 20 10:17:00 2011
Return-Path: <john@jlc.net>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id E546FE06B2 for <ietf@ietfc.amsl.com>; Wed, 20 Apr 2011 10:17:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.327
X-Spam-Level: 
X-Spam-Status: No, score=-106.327 tagged_above=-999 required=5 tests=[AWL=0.272, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LX7Yygi+IaLX for <ietf@ietfc.amsl.com>; Wed, 20 Apr 2011 10:17:00 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfc.amsl.com (Postfix) with ESMTP id D0998E0677 for <ietf@ietf.org>; Wed, 20 Apr 2011 10:16:59 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 9F84733C25; Wed, 20 Apr 2011 13:16:59 -0400 (EDT)
Date: Wed, 20 Apr 2011 13:16:59 -0400
From: John Leslie <john@jlc.net>
To: dcrocker@bbiw.net
Subject: Re: IAOC: delegating ex-officio responsibility
Message-ID: <20110420171659.GK64981@verdi>
References: <9C81C0F6-3ABE-4479-8C5E-C20C486D052A@gmail.com> <82A347CC-BB19-4A73-8E8A-924FBAA92A5F@NLnetLabs.nl> <84D6568B-18C9-47B2-A457-C51C2FB3351F@gmail.com> <5419FA805EF52E79D7822966@PST.JCK.COM> <DAC0FFD9-9B3B-4726-B56B-5E9BE5A5F1D1@gmail.com> <4DA8685F.5050504@dcrocker.net> <D0674791-3D7C-4B90-8189-A895715B977A@gmail.com> <4DADC758.2080906@dcrocker.net> <7D0E8BCB-194D-4FA1-ABDA-2F3175BA9441@gmail.com> <4DAF0BBB.4060001@dcrocker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4DAF0BBB.4060001@dcrocker.net>
User-Agent: Mutt/1.4.1i
Cc: Bob Hinden <bob.hinden@gmail.com>, 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, 20 Apr 2011 17:17:01 -0000

Dave CROCKER <dhc2@dcrocker.net> wrote:
> On 4/19/2011 12:53 PM, Bob Hinden wrote:
>> [Dave CROCKER <dhc2@dcrocker.net> wrote:]
>> 
>>> 1. ISOC, IAB and IESG each appoint one person currently.  Change this
>>>    to be two each, the same as Nomcom.  Each year, they would appoint
>>>    one person.
>>>
>>> 2. Move the I* Chairs to be non-voting ex-officio participants, the
>>>    same as the IETF Administrative Director. They are welcome to
>>>    participate or be explicitly invited to all IAOC/Trust activities.
>>>
>>> This produces the continuity that is needed for the admin work, but
>>> also retains access to the expertise of the I* chairs.

   I always respect Dave's suggestions. (Of course, I don't always agree
with them... ;^)

>> I don't agree. Appointing two people (or more?) doesn't solve the
>> problem I am concerned about, it still doesn't bring the chairs
>> perspective.

   I usually respect Bob's suggestions, but I don't always understand
them. (In particular, he's lost me here.)

>> It also significantly changes the governance model by changing the
>> balance between between nomcom, iab, iesg, and ISOC appointed members.

   The change in "balance" seems rather minimal -- but that could
certainly be fine-tuned.

>> Also, adding six people (still counting the chairs) will make the
>> IAOC much larger and unwieldy.

   That I understand. Perhaps we shouldn't be adding any...

   However, Russ & Olaf seem to think there's work they have been
expected to do. How will that work get done? Is the proposal first
floated simply telling them the work is their responsibility -- and
they need to find volunteers to do it?

   Us hoi-polloi aren't getting these details!

> For clarification:
> 
> 1.  The IAB, IESG and ISOC each put two voting people onto the IAOC/Trust 
> today. My proposal preserves that.
> 
> 2. The intent behind moving the I* Chairs to non-voting status, like the 
> IAD, is to ensure that they can continue to participate but remove from
> the the requirement for daily IAOC/Trust activities. The presumption is
> that they dive in for the big stuff, of the sort you cited, but do not
> have the burden of regular participation.

   I have a slightly different view: that the IAOC is entitled to try to
entice them into participation, but they would have the right to say "No".

> For emphasis:
> 
> As SM notes, my starting point is two of these folk saying they have to 
> have a change. Looking at the list of their duties, no one should be 
> surprised that they feel (and are) overloaded. So, they looked over
> their current duties and decided this is the one they'd like to change.
> I don't have -- and haven't heard anyone else suggest -- that some other
> change in their duties would be more appropriate. So I see the relevant
> question as how to make a change, not whether.

   I agree. Hopefully most of us can agree.

   Charging them to find someone to do the work feels wrong to me.

   Moving them to non-voting status feels right.

   Enabling them to participate in areas they feel critical feels right.

   Adding other individuals with voting status seems reasonable, but
not-exactly-right.

   Perhaps the most important change would be simply not counting them
for purposes of quorum...

--
John Leslie <john@jlc.net>

From behcetsarikaya@yahoo.com  Wed Apr 20 10:18:50 2011
Return-Path: <behcetsarikaya@yahoo.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id A47CBE06C9 for <ietf@ietfc.amsl.com>; Wed, 20 Apr 2011 10:18:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.588
X-Spam-Level: 
X-Spam-Status: No, score=-1.588 tagged_above=-999 required=5 tests=[AWL=1.011,  BAYES_00=-2.599]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NhoXP8z-Z5UD for <ietf@ietfc.amsl.com>; Wed, 20 Apr 2011 10:18:50 -0700 (PDT)
Received: from nm15-vm0.bullet.mail.sp2.yahoo.com (nm15-vm0.bullet.mail.sp2.yahoo.com [98.139.91.208]) by ietfc.amsl.com (Postfix) with SMTP id DFEA7E06B2 for <ietf@ietf.org>; Wed, 20 Apr 2011 10:18:49 -0700 (PDT)
Received: from [98.139.91.68] by nm15.bullet.mail.sp2.yahoo.com with NNFMP; 20 Apr 2011 17:18:46 -0000
Received: from [98.139.91.38] by tm8.bullet.mail.sp2.yahoo.com with NNFMP; 20 Apr 2011 17:18:46 -0000
Received: from [127.0.0.1] by omp1038.mail.sp2.yahoo.com with NNFMP; 20 Apr 2011 17:18:46 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 697078.32080.bm@omp1038.mail.sp2.yahoo.com
Received: (qmail 54562 invoked by uid 60001); 20 Apr 2011 17:18:46 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1303319926; bh=l91q3AYbk0GGBEufYPIZuQ5nRRLqGORjNUDX/z78I5Y=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=IFbKWVr/yMcEn8BergmUpaFDjEbD9TG44SX1trit8QR4pe4UpMFUYVqgpI4jCojPKL/iJjQGBEOj3ss2c6rTIPv01Jo30juJynBj21BoHAhsWWpqev7i/3VNa1TXC+JJauYQJe1cukjBg3lveNg82VA6njj6m/3FDnyjB2XZiG8=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=RwWsi/Ci/Ffh6MQ7dqd9gKLrbfyfhp1563fealZz+UOmEOMzliQoZ4hxnRKmRF/7iRT8LYVxNVvAIbus7cjGNvhZB0frRc7eFU2pN1Tt57pm1ENwc4cZZLoqUViegn/Nz8r3bFedA0xKeDjUzvNNOuMMSswPTvU6EAT+DIsuwPo=;
Message-ID: <3035.52653.qm@web111412.mail.gq1.yahoo.com>
X-YMail-OSG: Y8PVRjsVM1lbF2IVhzTdEOLW_mssfOEdFUOqI43wrs3Rn.U LuEVP85PQxOlqkVLWY7LgJSuHWP78bmap4UdladKfhMRiL6.sI70afQgs0tY FX3UhjT8R1DEWlil.hLLdoJm6ghkTvGQTnQX0qYO_WyEt4ck_8POE4EkOHy4 rhwfdWEurLj1VdUEE_ECsn3ftMZXLBSRHOU7PYmcvH_4KFqLtug2l0hKvupD Ok69I5RF7bAoyLxh7vnAAZGNbPRpBtZDr2TnGH06KjirO.N8Yq84UrkobmQG 4t891HuuLEC2qBE0HXPBUFTGMvBLvvDRFNc1dxXoTXxdqwbU3Sb883TcfJJx yuDtvulUNEqPDo8xzi_zBoyYnb3.KpoPCj19_fls63lAtVlGnjYAPaMTO.fI 30ucP7N7XHAVFAA--
Received: from [206.16.17.212] by web111412.mail.gq1.yahoo.com via HTTP; Wed, 20 Apr 2011 10:18:45 PDT
X-Mailer: YahooMailRC/559 YahooMailWebService/0.8.109.295617
Date: Wed, 20 Apr 2011 10:18:45 -0700 (PDT)
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
Subject: Revising I-Ds became painful
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Behcet Sarikaya <sarikaya@ieee.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, 20 Apr 2011 17:18:50 -0000

Hi,
  It seems like I-D submission for a revised draft (after expiration) encounters 
so many new hurdles:

1. Version number. Submission page complains about the version number even 
though it is correct. This seems to be because the system keeps the expiration 
message in html format as the new version to be submitted. 

Is there a way to get around this?

2. RFC XML has changed. It seem like 
xml.resource.org has a new xml compiler. I had a lot of trouble in compiling my 
existing xml files. I am OK with improving RFC XML but why not keep upward 
compatibility?

Regards,

Behcet


From daedulus@btconnect.com  Wed Apr 20 11:20:37 2011
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id DB1BCE06A6; Wed, 20 Apr 2011 11:20:37 -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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rD6e8AkuZS-f; Wed, 20 Apr 2011 11:20:36 -0700 (PDT)
Received: from mail.btconnect.com (c2bthomr09.btconnect.com [213.123.20.127]) by ietfc.amsl.com (Postfix) with ESMTP id C39D5E067D; Wed, 20 Apr 2011 11:20:35 -0700 (PDT)
Received: from host86-134-204-18.range86-134.btcentralplus.com (HELO pc6) ([86.134.204.18]) by c2bthomr09.btconnect.com with SMTP id CQA03480; Wed, 20 Apr 2011 19:20:28 +0100 (BST)
Message-ID: <01d701cbff7f$1c913940$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
References: <20110419165634.CD24CE07CF@ietfc.amsl.com>	<4DADCB52.1020309@joelhalpern.com>	<7BAC95F5A7E67643AAFB2C31BEE662D01406AC564E@SC-VEXCH2.marvell.com><1303248099.2209.105.camel@localhost.localdomain> <4DAE4246.7080200@joelhalpern.com>
Subject: Re: [paws] WG Review: Protocol to Access White Space database (paws)
Date: Wed, 20 Apr 2011 19:19:26 +0200
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-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0301.4DAF23EB.008B, actions=tag
X-Junkmail-Premium-Raw: score=26/50, refid=2.7.2:2011.4.20.173315:17:26.894, ip=86.134.204.18, rules=__HAS_MSGID, __OUTLOOK_MSGID_1, __SANE_MSGID, __TO_MALFORMED_2, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __MIME_VERSION, __CT, __CT_TEXT_PLAIN, __CTE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __HAS_X_MAILER, USER_AGENT_OE, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, __FRAUD_CONTACT_ADDY_B, __CP_URI_IN_BODY, __INT_PROD_TV, BODY_SIZE_10000_PLUS, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, __URI_NS, SXL_IP_DYNAMIC[18.204.134.86.fur], RDNS_SUSP_GENERIC, __OUTLOOK_MUA, RDNS_SUSP
X-Junkmail-Status: score=38/50, host=c2bthomr09.btconnect.com
X-Junkmail-Signature-Raw: score=suspect(3), refid=str=0001.0A0B0206.4DAF23EE.0092,ss=2,fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=multiengine
X-Junkmail-IWF: false
Cc: Paul Lambert <paul@marvell.com>, paws@ietf.org, iesg@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: Wed, 20 Apr 2011 18:20:38 -0000

----- Original Message -----
From: "Joel M. Halpern" <jmh@joelhalpern.com>
To: "Rex Buddenberg" <budden@nps.navy.mil>
Cc: "Paul Lambert" <paul@marvell.com>; <paws@ietf.org>; <iesg@ietf.org>; "IETF
discussion list" <ietf@ietf.org>
Sent: Wednesday, April 20, 2011 4:17 AM
Subject: Re: [paws] WG Review: Protocol to Access White Space database (paws)


> Actually, as far as I can tell, there is very little parallel between
> the PAWS problem and SNMP.
> SNMP tends to be initiated by the manager, and used to extract
> information from the device in the network, or set information in teh
> device.

Joel

I see one small parallel with SNMP. All the recent work on SNMP has
been on security, and while setting up a secure channel is easy, TLS or SSH,
knowing that it goes where you want it to as opposed to via a MITM is
more difficult, both when the device calls home to send an alert, or
when home calls the device to solicit information.

And the credentials used by the transport need binding securely to
the identity at a higher layer.  This was troublesome and I will
be interested to see how this is solved.  By comparison  I expect
that the application will fall out in the wash.

Channel binding anyone?  One for the security area?

Tom Petch





> This protocol is used by the client.  It extracts basically stable
> information about what frequencies can be used in this geographic region
> at this time.
> There is no "network management" going on.  the interaction does not
> look like SNMP.  And the effect does not look like SNMP.  While Radius
> or Diameter are closer, this protocol is not even a policy decision
> protocol.  There is no "policy".
>
> So no, I do not think this looks anything like network management.
> The protocols, the transaction drivers and behavior, the problem space,
> and the underlying data behavior are all very different from any of our
> NM work.
>
> Yours,
> Joel
>
> On 4/19/2011 5:21 PM, Rex Buddenberg wrote:
> > On Tue, 2011-04-19 at 12:47 -0700, Paul Lambert wrote:
> >>
> >> How does the area that the group is assigned impact the choices of
> >> technology?
> >>
> >> I'm an advocate for an efficient solution set for PAWS ... it will be
> >> much like DNS for spectrum in the future and should be viewed as a
> >> core infrastructural component that needs careful design.  There are
> >> good reasons that routing protocols don't use XML.
> >
> > While the DNS analogy works, I was thinking more a parallel -- or
> > extension -- of SNMP.
> >
> > Still remain within 'applications', Joel?
> >
> >>
> >> Applications now days tend to go for the simple, quick to make a web
> >> application solutions using XML or the like ...  My concern is that
> >> "Applications" imply that efficiency does not matter.
> >>
> >> Paul
> >>
> >>
> >>
> >>> -----Original Message-----
> >>> From: paws-bounces@ietf.org [mailto:paws-bounces@ietf.org] On Behalf Of
> >>> Joel M. Halpern
> >>> Sent: Tuesday, April 19, 2011 10:50 AM
> >>> To: iesg@ietf.org
> >>> Cc: paws@ietf.org; IETF discussion list
> >>> Subject: Re: [paws] WG Review: Protocol to Access White Space database
> >>> (paws)
> >>>
> >>> I think this working group is a good idea.
> >>> My inclination would be to place it in the Applications area.  It looks
> >>> like a nice application protocol to me.
> >>> There is a reasonable argument for placing it in RAI, as that is where
> >>> the relevant GEOLOC work has been done up till now.
> >>>
> >>> Yours,
> >>> Joel M. Halpern
> >>>
> >>> On 4/19/2011 12:56 PM, IESG Secretary wrote:
> >>>> A new IETF working group has been proposed.  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@ietf.org) by Tuesday, April 26, 2011.
> >>>>
> >>>>
> >>>> Protocol to Access White Space database (paws)
> >>>> ------------------------------------------------
> >>>> Current Status: Proposed Working Group
> >>>> Last updated: 2011-04-14
> >>>>
> >>>> Chairs:
> >>>> TBD
> >>>>
> >>>> Area Directors:
> >>>> TBD
> >>>>
> >>>> Area Advisor:
> >>>> TBD
> >>>>
> >>>> Mailing lists:
> >>>> Address: paws@ietf.org
> >>>> To Subscribe: https://www.ietf.org/mailman/listinfo/paws
> >>>> Archive: http://www.ietf.org/mail-archive/web/paws/
> >>>>
> >>>> Description of Working Group:
> >>>>
> >>>> Governments around the world continue to search for new pieces of
> >>> radio
> >>>> spectrum which can be used by the expanding wireless communications
> >>>> industry to provide more services in the usable spectrum. The concept
> >>>> of allowing secondary transmissions (licensed or unlicensed) in
> >>>> frequencies allocated to a primary user is a technique to "unlock"
> >>>> existing spectrum for new use. An obvious requirement is that these
> >>>> secondary transmissions do not interfere with the primary use of the
> >>>> spectrum. Often, in a given physical location, the primary user(s)
> >>> may
> >>>> not be using the entire band allocated to them. The available
> >>> spectrum
> >>>> for a secondary use would then depend on the location of the
> >>> secondary
> >>>> user. The primary user may have a schedule when it uses the spectrum,
> >>>> which may be available for secondary use outside that schedule. The
> >>>> fundamental issue is how to determine for a specific location and
> >>>> specific time, if any of the primary spectrum is available for
> >>> secondary
> >>>> use. One simple mechanism is to use a geospatial database that
> >>> records
> >>>> protected contours for primary users, and require the secondary users
> >>> to
> >>>> check the database prior to selecting what part of the spectrum they
> >>>> use. Such databases could be available on the Internet for query by
> >>>> users.
> >>>>
> >>>> In a typical implementation of geolocation and database to access TV
> >>>> white space, a radio is configured with, or has the capability to
> >>>> determine its location in latitude and longitude. At power-on, before
> >>>> the device can transmit or use any of the spectrum set aside for
> >>>> secondary use, the device must identify the relevant database to
> >>> query,
> >>>> contact the database, provide its geolocation and receive in return a
> >>>> list of unoccupied or "white space" spectrum (for example, in a TV
> >>>> White space implementation, the list of available channels at that
> >>>> location). The device can then select one of the channels from the
> >>> list
> >>>> and begin to transmit and receive on the selected channel. The device
> >>>> must query the database subsequently on a periodic basis for a list
> >>> of
> >>>> unoccupied channels based on certain conditions, e.g. a fixed amount
> >>> of
> >>>> time has passed or the device has changed location beyond a specified
> >>>> threshold.
> >>>>
> >>>> The databases are expected to be reachable via the Internet and the
> >>>> devices querying these databases are expected to have some form of
> >>>> Internet connectivity, directly or indirectly. The databases may be
> >>>> country specific since the available spectrum and regulations may
> >>> vary,
> >>>> but the fundamental operation of the protocol should be country
> >>>> independent, thus extensibility of data structures will be required.
> >>> The
> >>>> solution will not be tied to any specific spectrum, country, or
> >>>> phy/mac/air interface but may incorporate relevant aspects of these
> >>> as
> >>>> needed for proper operation.
> >>>>
> >>>> The proposed working group will :
> >>>> - standardize a protocol for querying the database, which includes a
> >>>> location sensitive database discovery mechanism and security for the
> >>>> protocol, and application services.
> >>>> - Standardize the data structure to be carried by the query
> >>>> protocol.
> >>>>
> >>>> The protocol must protect both the channel enablement process and the
> >>>> privacy of users. Robust security mechanisms are required to prevent:
> >>>> device identity spoofing, modification of device requests,
> >>> modification
> >>>> of channel enablement information, impersonation of registered
> >>> database
> >>>> services and unauthorized disclosure of a users location.
> >>>>
> >>>> Existing IETF location data structures and privacy mechanisms may be
> >>>> considered for use. The WG will also investigate the need for other
> >>>> mechanisms and related protocols to the White Space DB.
> >>>>
> >>>> The Working Group will set up and maintain appropriate contact and
> >>>> liaison with other relevant standards bodies and groups, including
> >>> IEEE
> >>>> 802.11af and IEEE 802.22 to begin with. The working group may also
> >>>> consider input from regulatory entities that are involved in the
> >>>> specification of the rules for secondary use of spectrum in specific
> >>>> bands.
> >>>>
> >>>> Goals and Milestones
> >>>>
> >>>> Sep 2011  Submit 'Requirements and Framework' to the IESG for
> >>>>             publication as Informational
> >>>>
> >>>> Apr 2012  Submit 'Protocol for Querying a Whitespace Database' to
> >>>>             the IESG for publication as Proposed Standard
> >>>>
> >>>> Apr 2012  Submit 'Data Model for Whitespace query protocol' to the
> >>>>             IESG for publication as Proposed Standard
> >>>> _______________________________________________
> >>>> paws mailing list
> >>>> paws@ietf.org
> >>>> https://www.ietf.org/mailman/listinfo/paws
> >>>>
> >>> _______________________________________________
> >>> paws mailing list
> >>> paws@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/paws
> >> _______________________________________________
> >> paws mailing list
> >> paws@ietf.org
> >> https://www.ietf.org/mailman/listinfo/paws
> >
> >
> >
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From fluffy@cisco.com  Wed Apr 20 11:23:07 2011
Return-Path: <fluffy@cisco.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id DA961E073E; Wed, 20 Apr 2011 11:23:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.585
X-Spam-Level: 
X-Spam-Status: No, score=-110.585 tagged_above=-999 required=5 tests=[AWL=0.014, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8OyrxvdSFUpK; Wed, 20 Apr 2011 11:23:06 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by ietfc.amsl.com (Postfix) with ESMTP id 1B556E0732; Wed, 20 Apr 2011 11:23:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fluffy@cisco.com; l=6676; q=dns/txt; s=iport; t=1303323784; x=1304533384; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=cKWdl2kHU2VpnLzKGXA0YOivG8TR6L1jmr/qqaZYrbI=; b=L7EX/3xDU9IhWbHFzGX45TeGG40lYliI1q0Z4Vh5H1p6RaIdcUkNmHPH gr11XtroipU52Dn74kneulu6/1kGFZGKoTIYyqU+bOvEhyd8Hnm/Bq5FA 6Sy48kxo4EGy46uKpjauYuJHrT/KY1HAOWj0+JXW1xPMh+Ev/CxOf/LLD Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkgBAG8jr02rRDoJ/2dsb2JhbACXM44Kd4hvojmcdoJ/AYJxBIV0iC6Df4of
X-IronPort-AV: E=Sophos;i="4.64,247,1301875200"; d="scan'208";a="298657412"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by sj-iport-3.cisco.com with ESMTP; 20 Apr 2011 18:23:03 +0000
Received: from [192.168.4.100] (rcdn-fluffy-8712.cisco.com [10.99.9.19]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p3KIN2A6012654; Wed, 20 Apr 2011 18:23:02 GMT
Subject: Re: [paws] WG Review: Protocol to Access White Space database (paws)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <4DADCB52.1020309@joelhalpern.com>
Date: Wed, 20 Apr 2011 12:23:01 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <76B1A6A1-F704-45F3-9A82-C590308C60F7@cisco.com>
References: <20110419165634.CD24CE07CF@ietfc.amsl.com> <4DADCB52.1020309@joelhalpern.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
X-Mailer: Apple Mail (2.1084)
Cc: paws@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: Wed, 20 Apr 2011 18:23:08 -0000

GEOLOC has been a WG that is somewhat on the edge between Apps and RAI. =
Much of what geoloc was doing, particularly the location for emergency =
calling, had real time issues and the interested people largely lined up =
with the the other RAI groups even though geoloc has uses outside =
anything to do with SIP. PAWS on the other hand does not seem to have =
real time application issues so it seems like Apps is probably a more =
appropriate area for it.=20

Cullen


On Apr 19, 2011, at 11:50 AM, Joel M. Halpern wrote:

> I think this working group is a good idea.
> My inclination would be to place it in the Applications area.  It =
looks like a nice application protocol to me.
> There is a reasonable argument for placing it in RAI, as that is where =
the relevant GEOLOC work has been done up till now.
>=20
> Yours,
> Joel M. Halpern
>=20
> On 4/19/2011 12:56 PM, IESG Secretary wrote:
>> A new IETF working group has been proposed.  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@ietf.org) by Tuesday, April 26, 2011.
>>=20
>>=20
>> Protocol to Access White Space database (paws)
>> ------------------------------------------------
>> Current Status: Proposed Working Group
>> Last updated: 2011-04-14
>>=20
>> Chairs:
>> TBD
>>=20
>> Area Directors:
>> TBD
>>=20
>> Area Advisor:
>> TBD
>>=20
>> Mailing lists:
>> Address: paws@ietf.org
>> To Subscribe: https://www.ietf.org/mailman/listinfo/paws
>> Archive: http://www.ietf.org/mail-archive/web/paws/
>>=20
>> Description of Working Group:
>>=20
>> Governments around the world continue to search for new pieces of =
radio
>> spectrum which can be used by the expanding wireless communications
>> industry to provide more services in the usable spectrum. The concept
>> of allowing secondary transmissions (licensed or unlicensed) in
>> frequencies allocated to a primary user is a technique to "unlock"
>> existing spectrum for new use. An obvious requirement is that these
>> secondary transmissions do not interfere with the primary use of the
>> spectrum. Often, in a given physical location, the primary user(s) =
may
>> not be using the entire band allocated to them. The available =
spectrum
>> for a secondary use would then depend on the location of the =
secondary
>> user. The primary user may have a schedule when it uses the spectrum,
>> which may be available for secondary use outside that schedule. The
>> fundamental issue is how to determine for a specific location and
>> specific time, if any of the primary spectrum is available for =
secondary
>> use. One simple mechanism is to use a geospatial database that =
records
>> protected contours for primary users, and require the secondary users =
to
>> check the database prior to selecting what part of the spectrum they
>> use. Such databases could be available on the Internet for query by
>> users.
>>=20
>> In a typical implementation of geolocation and database to access TV
>> white space, a radio is configured with, or has the capability to
>> determine its location in latitude and longitude. At power-on, before
>> the device can transmit or use any of the spectrum set aside for
>> secondary use, the device must identify the relevant database to =
query,
>> contact the database, provide its geolocation and receive in return a
>> list of unoccupied or "white space" spectrum (for example, in a TV
>> White space implementation, the list of available channels at that
>> location). The device can then select one of the channels from the =
list
>> and begin to transmit and receive on the selected channel. The device
>> must query the database subsequently on a periodic basis for a list =
of
>> unoccupied channels based on certain conditions, e.g. a fixed amount =
of
>> time has passed or the device has changed location beyond a specified
>> threshold.
>>=20
>> The databases are expected to be reachable via the Internet and the
>> devices querying these databases are expected to have some form of
>> Internet connectivity, directly or indirectly. The databases may be
>> country specific since the available spectrum and regulations may =
vary,
>> but the fundamental operation of the protocol should be country
>> independent, thus extensibility of data structures will be required. =
The
>> solution will not be tied to any specific spectrum, country, or
>> phy/mac/air interface but may incorporate relevant aspects of these =
as
>> needed for proper operation.
>>=20
>> The proposed working group will :
>> - standardize a protocol for querying the database, which includes a
>> location sensitive database discovery mechanism and security for the
>> protocol, and application services.
>> - Standardize the data structure to be carried by the query
>> protocol.
>>=20
>> The protocol must protect both the channel enablement process and the
>> privacy of users. Robust security mechanisms are required to prevent:
>> device identity spoofing, modification of device requests, =
modification
>> of channel enablement information, impersonation of registered =
database
>> services and unauthorized disclosure of a users location.
>>=20
>> Existing IETF location data structures and privacy mechanisms may be
>> considered for use. The WG will also investigate the need for other
>> mechanisms and related protocols to the White Space DB.
>>=20
>> The Working Group will set up and maintain appropriate contact and
>> liaison with other relevant standards bodies and groups, including =
IEEE
>> 802.11af and IEEE 802.22 to begin with. The working group may also
>> consider input from regulatory entities that are involved in the
>> specification of the rules for secondary use of spectrum in specific
>> bands.
>>=20
>> Goals and Milestones
>>=20
>> Sep 2011  Submit 'Requirements and Framework' to the IESG for
>>           publication as Informational
>>=20
>> Apr 2012  Submit 'Protocol for Querying a Whitespace Database' to
>>           the IESG for publication as Proposed Standard
>>=20
>> Apr 2012  Submit 'Data Model for Whitespace query protocol' to the
>>           IESG for publication as Proposed Standard
>> _______________________________________________
>> paws mailing list
>> paws@ietf.org
>> https://www.ietf.org/mailman/listinfo/paws
>>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From brian.e.carpenter@gmail.com  Wed Apr 20 14:22:02 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id E057EE0764 for <ietf@ietfc.amsl.com>; Wed, 20 Apr 2011 14:22:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.216
X-Spam-Level: 
X-Spam-Status: No, score=-103.216 tagged_above=-999 required=5 tests=[AWL=0.383, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cB5A6E+Uoz3G for <ietf@ietfc.amsl.com>; Wed, 20 Apr 2011 14:22:01 -0700 (PDT)
Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by ietfc.amsl.com (Postfix) with ESMTP id BD1CBE074C for <ietf@ietf.org>; Wed, 20 Apr 2011 14:22:01 -0700 (PDT)
Received: by pwi5 with SMTP id 5so756703pwi.31 for <ietf@ietf.org>; Wed, 20 Apr 2011 14:22:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=g0b99V77LBfMbaX5fogmXvthD3/e32DGDesVO+Ft9ec=; b=HCRNBGEG0TIxU84dx/NCu2HgWrAqe1Mu+PAUApyc2QaztHdVlTrLa92McOS6FZMLei 3Q1L+6WIHNydn3KCaid+EsmhFGOqJXicUazWXvKUOZ6x8efwdaOVUoTGuQfOILrIy+lI BjvGORueJCk3Gj+3OqFLpiMASNkhCqHiUAb7s=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=hqGKLLdYRvcqW9r4K+zCJ/svWcAUVdPv7db6FGjnc5asJZxm59atm4emSGVeaXBnPp ZZGlr6WuKtqWsG9BLH8aVgVdzb9+e2XjnsBPDqFAr/hcPWn//vkoz8B7dZEjfr8exoHb zY8HJoBRBF3xzSJ86qenV+GNKT/ynUTbQj10c=
Received: by 10.68.51.101 with SMTP id j5mr11333449pbo.462.1303334520951; Wed, 20 Apr 2011 14:22:00 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id d10sm847049pbf.98.2011.04.20.14.21.57 (version=SSLv3 cipher=OTHER); Wed, 20 Apr 2011 14:21:59 -0700 (PDT)
Message-ID: <4DAF4E76.1000806@gmail.com>
Date: Thu, 21 Apr 2011 09:21:58 +1200
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: IAOC: delegating ex-officio responsibility
References: <2BE582FA-2682-4232-9D83-23A03F01A0DB@NLnetLabs.nl>	<6.2.5.6.2.20110330073936.0e1899d0@resistor.net>	<E2E41FDE-3818-4513-9933-CB1E0326B43E@nlnetlabs.nl>	<6.2.5.6.2.20110330113947.0c948bc0@resistor.net>	<4D942843.4060804@gmail.com>	<6.2.5.6.2.20110331120351.09488990@resistor.net>	<4D955661.8050502@gmail.com>	<9C81C0F6-3ABE-4479-8C5E-C20C486D052A@gmail.com>	<82A347CC-BB19-4A73-8E8A-924FBAA92A5F@NLnetLabs.nl>	<84D6568B-18C9-47B2-A457-C51C2FB3351F@gmail.com>	<5419FA805EF52E79D7822966@PST.JCK.COM>	<DAC0FFD9-9B3B-4726-B56B-5E9BE5A5F1D1@gmail.com>	<4DA8685F.5050504@dcrocker.net>	<D0674791-3D7C-4B90-8189-A895715B977A@gmail.com>	<6.2.5.6.2.20110419080338.0301b940@resistor.net>	<90F3E256-88F5-4DCF-A64B-EF7FDDE667C8@gmail.com> <6.2.5.6.2.20110419161215.03d496a0@resistor.net>
In-Reply-To: <6.2.5.6.2.20110419161215.03d496a0@resistor.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Bob Hinden <bob.hinden@gmail.com>, 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, 20 Apr 2011 21:22:03 -0000

On 2011-04-20 21:13, SM wrote:
> Hi Bob,
> At 14:04 19-04-2011, Bob Hinden wrote:
>> But that may not always be the case that all IAOC members have a lot
>> of IETF experience.  We need to have a governance model that works
>> into the future.

...

> You may notice that there isn't any intersection with the previous list.

I think you are overlooking that some of the people in the first list
have been in liaison positions in NomCom; in terms of understanding
NomCom's challenges, that is sufficient. In any case, the difficulty
of finding available candidates is quite apparent.
...

> I agree with you that the views of the I* Chairs are important.

In the case of the IETF Chair I believe the issue is that it's
highly desirable, from a governance viewpoint, that the IETF Chair
has *personal* responsibility in IAOC decisions, and therefore should
be a voting member as a matter of principle.

I don't believe that argument applies to the IAB Chair - we should
IMHO have a collective goal to sharply reduce the IAB's involvement
in administrative issues, so that it can do its architectural and
liaison jobs properly. Delegating the IAB Chair role in the IAOC
would be a step in that direction, along with appointing the permanent
RFC Series Editor.

We haven't discussed the third proposed delegation, that of the ISOC
President's seat, very much. Assuming it was delegated to another
officer of ISOC, that would seem reasonable too. But it shouldn't
be delegated to just anybody, IMHO.

   Brian

    Brian

From bob.hinden@gmail.com  Wed Apr 20 14:40:46 2011
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 2128BE0777 for <ietf@ietfc.amsl.com>; Wed, 20 Apr 2011 14:40:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.551
X-Spam-Level: 
X-Spam-Status: No, score=-103.551 tagged_above=-999 required=5 tests=[AWL=0.048, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dgbdU1TdxMba for <ietf@ietfc.amsl.com>; Wed, 20 Apr 2011 14:40:45 -0700 (PDT)
Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by ietfc.amsl.com (Postfix) with ESMTP id 5528DE06DE for <ietf@ietf.org>; Wed, 20 Apr 2011 14:40:44 -0700 (PDT)
Received: by pwi5 with SMTP id 5so765500pwi.31 for <ietf@ietf.org>; Wed, 20 Apr 2011 14:40:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=MnWR0T5znf1iqlghyFwBsGj90Om7OKfpo+PHWp+0LqI=; b=vipUsAySTgpVaThoXCsjFwI4PAkMQS+cEMEAFYnrf70srXnddi/VRp9QF00TZJm+uC ygx5siK4kz6otP4bBsMBZUWa+bNvNx5jhcKX3LUz/hqgktRQElyglNB6p6V8SKXa+wyy Yma3UBCVG95uKOTIfpGpPi0CdudRcr9FqByq4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=qBGYqmjHt5nyQvGy6RWINBBrra+NemtyQWRTKdXo3nh0l4g8BAmDuMQ3SbQMMEf2Vz EqcvSiTSS2+dawK2qNVCn++sr0yPTUl1KkhyId0xAPwa5+1phNCsreSKpnvMru83ghgL IMPvLtZJE8n2ur/xpQ1ggtd8zV9mLgc+hWfm4=
Received: by 10.68.50.168 with SMTP id d8mr11774159pbo.224.1303335643854; Wed, 20 Apr 2011 14:40:43 -0700 (PDT)
Received: from [172.16.224.217] ([209.97.127.34]) by mx.google.com with ESMTPS id p7sm857113pbi.58.2011.04.20.14.40.42 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 20 Apr 2011 14:40:42 -0700 (PDT)
Subject: Re: IAOC: delegating ex-officio responsibility
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: <4DAF4E76.1000806@gmail.com>
Date: Wed, 20 Apr 2011 14:40:40 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <B9FCA011-38B7-480B-8FA8-227F8F54B341@gmail.com>
References: <2BE582FA-2682-4232-9D83-23A03F01A0DB@NLnetLabs.nl>	<6.2.5.6.2.20110330073936.0e1899d0@resistor.net>	<E2E41FDE-3818-4513-9933-CB1E0326B43E@nlnetlabs.nl>	<6.2.5.6.2.20110330113947.0c948bc0@resistor.net>	<4D942843.4060804@gmail.com>	<6.2.5.6.2.20110331120351.09488990@resistor.net>	<4D955661.8050502@gmail.com>	<9C81C0F6-3ABE-4479-8C5E-C20C486D052A@gmail.com>	<82A347CC-BB19-4A73-8E8A-924FBAA92A5F@NLnetLabs.nl>	<84D6568B-18C9-47B2-A457-C51C2FB3351F@gmail.com>	<5419FA805EF52E79D7822966@PST.JCK.COM>	<DAC0FFD9-9B3B-4726-B56B-5E9BE5A5F1D1@gmail.com>	<4DA8685F.5050504@dcrocker.net>	<D0674791-3D7C-4B90-8189-A895715B977A@gmail.com>	<6.2.5.6.2.20110419080338.0301b940@resistor.net>	<90F3E256-88F5-4DCF-A64B-EF7FDDE667C8@gmail.com> <6.2.5.6.2.20110419161215.03d496a0@resistor.net> <4DAF4E76.1000806@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: Bob Hinden <bob.hinden@gmail.com>, 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, 20 Apr 2011 21:40:46 -0000

Brian,

If we are going to do this, then I tend to agree with your conclusions.

>=20
>=20
>> I agree with you that the views of the I* Chairs are important.
>=20
> In the case of the IETF Chair I believe the issue is that it's
> highly desirable, from a governance viewpoint, that the IETF Chair
> has *personal* responsibility in IAOC decisions, and therefore should
> be a voting member as a matter of principle.


My preference is that the IETF not delegate this responsibility.  One =
additional reason for this is that the IETF chair is appointed by the =
nomcom (vs. the IAB who appoints their own chair).  It is part of the =
job and an important part.


> I don't believe that argument applies to the IAB Chair - we should
> IMHO have a collective goal to sharply reduce the IAB's involvement
> in administrative issues, so that it can do its architectural and
> liaison jobs properly. Delegating the IAB Chair role in the IAOC
> would be a step in that direction, along with appointing the permanent
> RFC Series Editor.


In the case of the IAB, I would prefer that the IAB selected it's =
representative to the IAOC and that they become the full IAOC voting =
member (and a member of the IETF trust).  That is, it be completely =
delegated for a fixed term.  The IAB could consider this person as a =
vice-chair or even a co-chair.  The both represent other ways to reduce =
the load on the chair. =20


> We haven't discussed the third proposed delegation, that of the ISOC
> President's seat, very much. Assuming it was delegated to another
> officer of ISOC, that would seem reasonable too. But it shouldn't
> be delegated to just anybody, IMHO.

Also agree.  I think it should be limited to the CFO or COO.  I think, =
as above with the IAB, it should be fully delegated.

Bob



From gwz@net-zen.net  Wed Apr 20 22:18:37 2011
Return-Path: <gwz@net-zen.net>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 6CC9FE06D2 for <ietf@ietfc.amsl.com>; Wed, 20 Apr 2011 22:18: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=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oe8ofuElVQLV for <ietf@ietfc.amsl.com>; Wed, 20 Apr 2011 22:18:36 -0700 (PDT)
Received: from smtpauth04.prod.mesa1.secureserver.net (smtpauth04.prod.mesa1.secureserver.net [64.202.165.95]) by ietfc.amsl.com (Postfix) with SMTP id E69B4E07C2 for <ietf@ietf.org>; Wed, 20 Apr 2011 22:18:34 -0700 (PDT)
Received: (qmail 23228 invoked from network); 21 Apr 2011 05:18:34 -0000
Received: from unknown (124.120.98.54) by smtpauth04.prod.mesa1.secureserver.net (64.202.165.95) with ESMTP; 21 Apr 2011 05:18:33 -0000
Message-ID: <4DAFBE22.9070700@net-zen.net>
Date: Thu, 21 Apr 2011 12:18:26 +0700
From: Glen Zorn <gwz@net-zen.net>
Organization: Network Zen
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Behcet Sarikaya <sarikaya@ieee.org>
Subject: Re: Revising I-Ds became painful
References: <3035.52653.qm@web111412.mail.gq1.yahoo.com>
In-Reply-To: <3035.52653.qm@web111412.mail.gq1.yahoo.com>
X-Enigmail-Version: 1.1.1
Content-Type: multipart/mixed; boundary="------------040503070802030506010108"
Cc: Behcet Sarikaya <behcetsarikaya@yahoo.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, 21 Apr 2011 05:18:37 -0000

This is a multi-part message in MIME format.
--------------040503070802030506010108
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

On 4/21/2011 12:18 AM, Behcet Sarikaya wrote:

> Hi,
>   It seems like I-D submission for a revised draft (after expiration) encounters 
> so many new hurdles:
> 
> 1. Version number. Submission page complains about the version number even 
> though it is correct. This seems to be because the system keeps the expiration 
> message in html format as the new version to be submitted. 
> 
> Is there a way to get around this?

Don't let I-Ds expire?

> 
> 2. RFC XML has changed. It seem like 
> xml.resource.org has a new xml compiler. I had a lot of trouble in compiling my 
> existing xml files. 

Hmm.  I'm not experiencing any problems, either with the on-line or the
host based tools.  Are you sure that your XML was valid before?

> I am OK with improving RFC XML but why not keep upward 
> compatibility?
> 
> Regards,
> 
> Behcet
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> 
> 

--------------040503070802030506010108
Content-Type: text/x-vcard; charset=utf-8;
 name="gwz.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="gwz.vcf"

begin:vcard
fn:Glen Zorn
n:Zorn;Glen
org:Network Zen
adr:;;;Seattle;WA;;USA
email;internet:gwz@net-zen.net
tel;cell:+66 87 040 4617
note:PGP Key Fingerprint: DAD3 F5D3 ACE6 4195 9C5C  2EE1 6E17 B5F6 5953 B45F 
version:2.1
end:vcard


--------------040503070802030506010108--

From acooper@cdt.org  Thu Apr 21 04:01:50 2011
Return-Path: <acooper@cdt.org>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 6648AE06C8; Thu, 21 Apr 2011 04:01:50 -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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YdklWDG9tmjt; Thu, 21 Apr 2011 04:01:49 -0700 (PDT)
Received: from mail.maclaboratory.net (mail.maclaboratory.net [209.190.215.232]) by ietfc.amsl.com (Postfix) with ESMTP id 34E1DE06CD; Thu, 21 Apr 2011 04:01:49 -0700 (PDT)
Received: from localhost ([127.0.0.1]) by mail.maclaboratory.net (using TLSv1/SSLv3 with cipher AES128-SHA (128 bits)); Thu, 21 Apr 2011 07:01:29 -0400
Subject: Re: [paws] WG Review: Protocol to Access White Space database (paws)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Alissa Cooper <acooper@cdt.org>
In-Reply-To: <88BE24FD9280884487DEAE0CE1FD3A5B060F1B@008-AM1MPN1-023.mgdnok.nokia.com>
Date: Thu, 21 Apr 2011 12:01:23 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <F4035489-7D81-47C9-BE99-3D9DCF1637FA@cdt.org>
References: <20110419165634.CD24CE07CF@ietfc.amsl.com> <4DADFE6D.3050107@cs.tcd.ie> <88BE24FD9280884487DEAE0CE1FD3A5B060F1B@008-AM1MPN1-023.mgdnok.nokia.com>
To: <scott.probasco@nokia.com> <scott.probasco@nokia.com>
X-Mailer: Apple Mail (2.1084)
Cc: paws@ietf.org, 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: Thu, 21 Apr 2011 11:01:50 -0000

On Apr 20, 2011, at 3:41 PM, <scott.probasco@nokia.com> =
<scott.probasco@nokia.com> wrote:

> Hi Stephen, All,
>=20
> I believe the current wording
>>> Robust security mechanisms are required to prevent:
>>> device identity spoofing, modification of device requests, =
modification
>>> of channel enablement information, ...
> is acceptable because "mechanisms are required" means they should be =
in the protocol, it does not mean they cannot be optional. PAWS should =
support Regulator requirements globally, and thus I believe there will =
be procedures or capabilities which are "required" to be in the protocol =
but will be "optional" during run time. Thus different or conflicting =
requirements from different regions of the world can be supported. =
(Several regulatory groups around the world are still developing their =
views and requirements).
>=20

Agreed on this point, although I think the charter could make it a =
little less ambiguous by saying "Development of robust security =
mechanisms is required . . .," that way it's not indicating that the =
actual mechanisms themselves will always be required.

Given that device identity will have to be shared in some circumstances, =
I would also add its protection to the end of the list of mechanisms:=20

Development of security mechanisms is required to prevent:
device identity spoofing, modification of device requests, modification
of channel enablement information, impersonation of registered database
services and unauthorized disclosure of a user's location and/or device =
identity.

Alissa

> It's not the time to dig deep into proposed solutions, just my opinion =
is the current proposed wording is an acceptable definition to allow a =
Work Group to get started defining the details.
>=20
> Regards,
> Scott
>=20
> -----Original Message-----
> From: paws-bounces@ietf.org [mailto:paws-bounces@ietf.org] On Behalf =
Of ext Stephen Farrell
> Sent: Tuesday, April 19, 2011 4:28 PM
> To: IETF-Discussion
> Cc: paws@ietf.org; iesg@ietf.org
> Subject: Re: [paws] WG Review: Protocol to Access White Space database =
(paws)
>=20
>=20
> I think this is a good and timely thing for the IETF to do.
>=20
> One part of this where I think it might be useful to get
> some broader input (which may have happened already, I'm not
> sure) is the following:
>=20
> On 19/04/11 17:56, IESG Secretary wrote:
>> The protocol must protect both the channel enablement process and the
>> privacy of users.=20
>=20
> That part is fine but it goes on to say:
>=20
>> Robust security mechanisms are required to prevent:
>> device identity spoofing, modification of device requests, =
modification
>> of channel enablement information, ...
>=20
> I'm told (and believe) this in response to (at least) US
> FCC requirements that call for a device ID and sometimes
> serial number to be (securely, for some value of securely)
> sent with the query.
>=20
> Those appear to be real regulatory requirements in the
> US, presumably so the regulator can stomp on someone who
> messes about in the wrong spectrum at the wrong time.
> (The link below [1] may be to the right or wrong bit of
> those US regulations, I'm not at all sure, not being
> from there;-)
>=20
> So my questions:
>=20
> Are there may be similar (or conflicting!) requirements
> elsewhere?
>=20
> Does this bit of the charter text need changes to work
> well for other regions?
>=20
> Separately, I'm not sure how to square those kinds of
> regulatory requirements with protecting privacy where the
> device is carried by a person and has some FCC device ID
> (which lots do I guess) and the person might not want
> the database operator to know who's asking. But I think
> that's ok as something for the WG to figure out since
> the charter already calls for respecting privacy.
>=20
> I'm more concerned in case e.g. some other regional regulation
> called for this protocol to be completely anonymous or
> something, in which case the current charter text might
> be problematic.
>=20
> Cheers,
> Stephen.
>=20
> [1]
> =
http://ecfr.gpoaccess.gov/cgi/t/text/text-idx?c=3Decfr&sid=3D3e9c322addf1f=
7e897d8c84a6c7aca78&rgn=3Ddiv8&view=3Dtext&node=3D47:1.0.1.1.14.8.243.9&id=
no=3D47
> _______________________________________________
> paws mailing list
> paws@ietf.org
> https://www.ietf.org/mailman/listinfo/paws
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>=20



From tony@att.com  Thu Apr 21 04:41:01 2011
Return-Path: <tony@att.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 58615E06DA; Thu, 21 Apr 2011 04:41:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.452
X-Spam-Level: 
X-Spam-Status: No, score=-106.452 tagged_above=-999 required=5 tests=[AWL=0.147, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4gJF5SmQmOKO; Thu, 21 Apr 2011 04:41:00 -0700 (PDT)
Received: from mail119.messagelabs.com (mail119.messagelabs.com [216.82.241.195]) by ietfc.amsl.com (Postfix) with ESMTP id 72242E06CF; Thu, 21 Apr 2011 04:41:00 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: tony@att.com
X-Msg-Ref: server-12.tower-119.messagelabs.com!1303386059!15427449!1
X-StarScan-Version: 6.2.9; banners=-,-,-
X-Originating-IP: [144.160.20.145]
Received: (qmail 19777 invoked from network); 21 Apr 2011 11:40:59 -0000
Received: from sbcsmtp6.sbc.com (HELO mlpd192.enaf.sfdc.sbc.com) (144.160.20.145) by server-12.tower-119.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 21 Apr 2011 11:40:59 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd192.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id p3LBfNs6020242; Thu, 21 Apr 2011 07:41:23 -0400
Received: from alpd052.aldc.att.com (alpd052.aldc.att.com [130.8.42.31]) by mlpd192.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id p3LBfLdn020236; Thu, 21 Apr 2011 07:41:21 -0400
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 p3LBeutw005726; Thu, 21 Apr 2011 07:40:56 -0400
Received: from dns.maillennium.att.com (mailgw1.maillennium.att.com [135.25.114.99]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id p3LBek89005470; Thu, 21 Apr 2011 07:40:50 -0400
Received: from [135.70.2.83] (vpn-135-70-2-83.vpn.west.att.com[135.70.2.83]) by maillennium.att.com (mailgw1) with ESMTP id <20110421114044gw100e4ldde> (Authid: tony); Thu, 21 Apr 2011 11:40:45 +0000
X-Originating-IP: [135.70.2.83]
Message-ID: <4DB017BA.3000402@att.com>
Date: Thu, 21 Apr 2011 07:40:42 -0400
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Behcet Sarikaya <sarikaya@ieee.org>
Subject: Re: Revising I-Ds became painful
References: <3035.52653.qm@web111412.mail.gq1.yahoo.com>
In-Reply-To: <3035.52653.qm@web111412.mail.gq1.yahoo.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, Tools Team Discussion <tools-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, 21 Apr 2011 11:41:01 -0000

On 4/20/2011 1:18 PM, Behcet Sarikaya wrote:
> ...
>
> 2. RFC XML has changed. It seem like
> xml.resource.org has a new xml compiler. I had a lot of trouble in compiling my
> existing xml files. I am OK with improving RFC XML but why not keep upward
> compatibility?

An optional strict checker was added to the online xml2rfc web page, 
turned on by default.


You then have two choices:

1) Fix your XML.  If your XML file fails the strict checker, then it was 
not valid according to the xml2rfc DTD grammar. The error message will 
tell you what you did wrong, using a regular expression to describe what 
is expected (which may be rather cryptic). For example, here are a few 
of the messages you might see:

[Error] INPUT:86:9: The content of element type "list" is incomplete, it 
must match "(t)+".

Your <list> did not include any <t> tags.

[Error] INPUT:175:11: The content of element type "t" must match 
"(list|figure|xref|eref|iref|cref|spanx|vspace)".

Inside a <t> tag, you may only have one of the tags listed -- any other 
tag will be an error.

[Error] INPUT:193:11: The content of element type "section" must match 
"((t|figure|texttable|iref)*,section*)".

Inside a <section> tag, you can have zero or more <t>, <figure>, 
<texttable> or <iref> tags, followed by zero or more <section> tags.

The numbers indicate the line and column number where the error was 
noticed, but that number is figured out after include and reference 
processing has been performed. So it may not match exactly the line 
numbering in your file, but should be close.

2) Turn off the strict checking. In the web form, on the line that says 
Checking, instead of picking Strict choose Fast.

Note that there is currently an effort to rewrite the xml2rfc processor 
that does the actual processing behind the scenes. One of the 
requirements for this effort was that it pay strict attention to the 
DTD, exactly like the Strict Checking does.

Hope this helps.

     Tony Hansen
     tony@att.om

From mperumal@cisco.com  Thu Apr 21 04:44:50 2011
Return-Path: <mperumal@cisco.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id AD2C3E0748; Thu, 21 Apr 2011 04:44:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.174
X-Spam-Level: 
X-Spam-Status: No, score=-10.174 tagged_above=-999 required=5 tests=[AWL=0.425, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qkfj-veM24a2; Thu, 21 Apr 2011 04:44:49 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfc.amsl.com (Postfix) with ESMTP id 8A03EE06DA; Thu, 21 Apr 2011 04:44:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=mperumal@cisco.com; l=10560; q=dns/txt; s=iport; t=1303386288; x=1304595888; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=ER0mNLYMUtQSPJT9wInos3ls+PM80cq62b0pbd8GYYU=; b=TiN+HLSmTze3eW35tyHGwbYB+WA4R/7DEdAufiGIbwWA2XU9mWIa4G2Y HDRPeY3cYhvNFGbzZxW0Y237Vvm1PbLEc9uqcFSLbn/80z1kVY/3ptmaY AUz64iVYl7F+1Z/Fx2+acqOETqgNiAtiNcKJEC/IjRV20psJbsGe0guO3 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsAAHEXsE2Q/khMgWdsb2JhbACXQY4HFAEBFiYlqBecUYIig1QEhXKMRQ
X-IronPort-AV: E=Sophos;i="4.64,251,1301875200"; d="scan'208";a="26604637"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-2.cisco.com with ESMTP; 21 Apr 2011 11:44:47 +0000
Received: from xbh-bgl-412.cisco.com (xbh-bgl-412.cisco.com [72.163.129.202]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p3LBiiEn015210; Thu, 21 Apr 2011 11:44:46 GMT
Received: from xmb-bgl-414.cisco.com ([72.163.129.210]) by xbh-bgl-412.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 21 Apr 2011 17:14:45 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [siprec] Last Call: <draft-ietf-siprec-req-09.txt>(Use	CasesandRequirements	for SIP-based MediaRecording	(SIPREC))	toInformational RFC
Date: Thu, 21 Apr 2011 17:14:43 +0530
Message-ID: <1D062974A4845E4D8A343C6538049202054256F5@XMB-BGL-414.cisco.com>
In-Reply-To: <A444A0F8084434499206E78C106220CA0875EB5D69@MCHP058A.global-ad.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] Last Call: <draft-ietf-siprec-req-09.txt>(Use	CasesandRequirements	for SIP-based MediaRecording	(SIPREC))	toInformational RFC
Thread-Index: Acv0WYBeRuGjGNBtTZSHeqn78QP5xwGEv6YwAAlHtwAAAvtH0AABcMXAAAdJn6AAAIZ7cAAHjozgABTz8IABOK4eoA==
References: <20110406125020.17538.70016.idtracker@localhost><1D062974A4845E4D8A343C65380492020533BB70@XMB-BGL-414.cisco.com><A444A0F8084434499206E78C106220CA0875EB5A4E@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38AB73D00B@TLVMBX01.nice.com><A444A0F8084434499206E78C106220CA0875EB5B28@MCHP058A.global-ad.net> <07465C1D981ABC41A344374066AE1A2C38AB73D110@TLVMBX01.nice.com> <35BCE99A477D6A4986FB2216D8CF2CFD06009D00@XMB-BGL-417.cisco.com> <1D062974A4845E4D8A343C65380492020533BD38@XMB-BGL-414.cisco.com> <A444A0F8084434499206E78C106220CA0875EB5D69@MCHP058A.global-ad.net>
From: "Muthu ArulMozhi Perumal (mperumal)" <mperumal@cisco.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>, "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>, "Leon Portman" <Leon.Portman@nice.com>, <ietf@ietf.org>
X-OriginalArrivalTime: 21 Apr 2011 11:44:45.0701 (UTC) FILETIME=[82E32B50:01CC0019]
Cc: siprec@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 Apr 2011 11:44:50 -0000

+1

I would suggest a small change to REQ-022 that John has drafted below to
make it more explicit:
=20
REQ-022 The mechanism MUST provide means for facilitating the following
either at storage or at playback:
a. Synchronization among the recorded media streams and=20
b. Synchronization of the recorded media streams and metadata.

Muthu

|-----Original Message-----
|From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
|Sent: Friday, April 15, 2011 11:53 AM
|To: Muthu ArulMozhi Perumal (mperumal); Ram Mohan R (rmohanr); Leon
Portman; ietf@ietf.org
|Cc: siprec@ietf.org
|Subject: RE: [siprec] Last Call: <draft-ietf-siprec-req-09.txt>(Use
CasesandRequirements for SIP-based
|MediaRecording (SIPREC)) toInformational RFC
|
|So perhaps if we replace REQ-022 and REQ-023 with the requirement that
Muthu has proposed and one
|further requirement, e.g.:
|
|"REQ-022 The mechanism MUST provide means for facilitating
synchronization of the
|recorded media streams and metadata either at storage or at playback.
|
|REQ-023 The mechanism MUST provide means for relating recordings to
wall clock time."
|
|John (as individual)
|
|> -----Original Message-----
|> From: Muthu ArulMozhi Perumal (mperumal) [mailto:mperumal@cisco.com]
|> Sent: 14 April 2011 21:42
|> To: Ram Mohan R (rmohanr); Leon Portman; Elwell, John; ietf@ietf.org
|> Cc: siprec@ietf.org
|> Subject: RE: [siprec] Last Call:
|> <draft-ietf-siprec-req-09.txt>(Use Cases andRequirements for
|> SIP-based MediaRecording (SIPREC)) toInformational RFC
|>
|> I agree with John that these seem more like part of a solution rather
|> than actual requirements. In addition, sending the wallclock time at
|> media start/end alone may not suffice for achieving inter-media
|> synchronization and playback, instead we may need to send the
|> wallclock
|> time periodically, like RTCP. For e.g, if there is a codec
|> renegotiation
|> in CS the RTP timestamp can restart from a random value. If silence
|> suppression is enabled there would be gaps in the RTP timestamp.
|>
|> These are things that need to be discussed as part of the solution --
|> the requirement itself should be generic enough, like what I
|> described.
|> REQ-022 and REQ-023 we have doesn't seem to clearly indicate the
|> purpose.
|>
|> Muthu
|>
|> |-----Original Message-----
|> |From: Ram Mohan R (rmohanr)
|> |Sent: Thursday, April 14, 2011 10:13 PM
|> |To: Leon Portman; Elwell, John; Muthu ArulMozhi Perumal (mperumal);
|> ietf@ietf.org
|> |Cc: siprec@ietf.org
|> |Subject: RE: [siprec] Last Call: <draft-ietf-siprec-req-09.txt>(Use
|> Cases andRequirements for SIP-
|> |based MediaRecording (SIPREC)) toInformational RFC
|> |
|> |We already have  attributes Start-Time / End-time in Media Stream
|> block. This is for the same purpose
|> |to indicate the wall clock time for start/end of media.
|> |
|> |Ram
|> |
|> |> -----Original Message-----
|> |> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
|> |> Behalf Of Leon Portman
|> |> Sent: Thursday, April 14, 2011 9:57 PM
|> |> To: Elwell, John; Muthu ArulMozhi Perumal (mperumal);
ietf@ietf.org
|> |> Cc: siprec@ietf.org
|> |> Subject: Re: [siprec] Last Call:
<draft-ietf-siprec-req-09.txt>(Use
|> |> Cases andRequirements for SIP-based MediaRecording (SIPREC))
|> |> toInformational RFC
|> |>
|> |> I am not sure that having wall clock only for CS start is enough,
|> |> especially for partial metadata update. I will prefer to have on
|> media
|> |> level
|> |>
|> |> Leon
|> |>
|> |> -----Original Message-----
|> |> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
|> |> Sent: Thursday, April 14, 2011 3:58 PM
|> |> To: Leon Portman; Muthu ArulMozhi Perumal (mperumal);
ietf@ietf.org
|> |> Cc: siprec@ietf.org
|> |> Subject: RE: [siprec] Last Call:
|> <draft-ietf-siprec-req-09.txt> (Use
|> |> Cases andRequirements for SIP-based Media Recording (SIPREC))
|> |> toInformational RFC
|> |>
|> |> Understood, but if we have wall clock time for the start of a CS,
|> |> wouldn't that be sufficient? The new requirement would cover
|> |> synchronization of all media start/stops relative to that time.
|> |>
|> |> John (as individual)
|> |>
|> |>
|> |> > -----Original Message-----
|> |> > From: Leon Portman [mailto:Leon.Portman@nice.com]
|> |> > Sent: 14 April 2011 13:19
|> |> > To: Elwell, John; Muthu ArulMozhi Perumal (mperumal);
|> ietf@ietf.org
|> |> > Cc: siprec@ietf.org
|> |> > Subject: RE: [siprec] Last Call:
|> |> > <draft-ietf-siprec-req-09.txt> (Use Cases andRequirements for
|> |> > SIP-based Media Recording (SIPREC)) toInformational RFC
|> |> >
|> |> > Actually REQ-022 and REQ-023 describing not only requirement to
|> |> > synchronize between different media streams but more importantly
|> |> > ability to relate them to real world (wall) clock. It is not
only
|> |> > important to playback them correctly but also to know when it
was
|> |> > said.
|> |> > One example is continue trading after closing hour (even for one
|> |> > second is not allowed)
|> |> >
|> |> > And if these media are synchronized to wall clock then they are
|> also
|> |> > synchronized between them thus I am not sure if we need this
|> |> > additional requirement.
|> |> >
|> |> > Thanks
|> |> >
|> |> > Leon
|> |> >
|> |> > -----Original Message-----
|> |> > From: siprec-bounces@ietf.org
|> |> > [mailto:siprec-bounces@ietf.org] On Behalf Of Elwell, John
|> |> > Sent: Thursday, April 14, 2011 1:54 PM
|> |> > To: Muthu ArulMozhi Perumal (mperumal); ietf@ietf.org
|> |> > Cc: siprec@ietf.org
|> |> > Subject: Re: [siprec] Last Call:
|> |> > <draft-ietf-siprec-req-09.txt> (Use Cases andRequirements for
|> |> > SIP-based Media Recording (SIPREC)) toInformational RFC
|> |> >
|> |> >
|> |> >
|> |> >
|> |> > > -----Original Message-----
|> |> > > From: siprec-bounces@ietf.org
|> |> > > [mailto:siprec-bounces@ietf.org] On Behalf Of Muthu
|> |> > ArulMozhi Perumal
|> |> > > (mperumal)
|> |> > > Sent: 14 April 2011 07:34
|> |> > > To: ietf@ietf.org
|> |> > > Cc: siprec@ietf.org
|> |> > > Subject: Re: [siprec] Last Call:
|> |> > > <draft-ietf-siprec-req-09.txt> (Use Cases andRequirements for
|> |> > > SIP-based Media Recording (SIPREC)) toInformational RFC
|> |> > >
|> |> > > I've one major comment. It draft discusses synchronization
|> |> > between the
|> |> > > recorded media streams and synchronized playback, which
|> |> > seem important
|> |> > > for certain applications:
|> |> > >
|> |> > > <snip>
|> |> > > Some applications require the recording of more than one
|> |> > media stream,
|> |> > > possibly of different types. Media are synchronized, either
|> |> > at storage
|> |> > > or at playback.
|> |> > > </snip>
|> |> > >
|> |> > > However, in the requirements section it doesn't seem
|> REQ-022 and
|> |> > > REQ-023 are all that are need and sufficient to
|> achieve this with
|> |> > > needed precision. So, I would suggest adding another
|> requirement
|> as
|> |> > > follows:
|> |> > > The mechanism MUST provide means for facilitating
|> |> > synchronization of
|> |> > > the recorded media streams and metadata either at storage or
at
|> |> > > playback.
|> |> > > This includes, but not limited to, the information
|> needed as per
|> |> > > REQ-022 and REQ-023.
|> |> > [JRE] This seems a reasonable addition. I wonder if the new
|> |> > requirement (first sentence only) is sufficient as a
|> |> > **replacement** for REQ-022 and REQ-023. On reading REQ-022 and
|> |> > REQ-023 again, it is not so clear what their purpose
|> was, and they
|> |> > seem to be more like a solution than a requirement.
|> |> > One purpose would certainly be that covered by Muthu's new
|> |> > requirement. Was there any other purpose?
|> |> >
|> |> > John
|> |> >
|> |> > >
|> |> > > A nitpick:
|> |> > > Use Case 8
|> |> > > In cases where calls inside or between branches must
|> be recorded,
|> a
|> |> > > centralized recording system in data centers together with
|> |> > telephony
|> |> > > infrastructure (e.g. PBX) me deployed.
|> |> > >
|> |> > > s/me/may be
|> |> > >
|> |> > > Muthu
|> |> > >
|> |> > > |-----Original Message-----
|> |> > > |From: siprec-bounces@ietf.org
[mailto:siprec-bounces@ietf.org]
|> On
|> |> > > Behalf Of The IESG
|> |> > > |Sent: Wednesday, April 06, 2011 6:20 PM
|> |> > > |To: IETF-Announce
|> |> > > |Cc: siprec@ietf.org
|> |> > > |Subject: [siprec] Last Call: <draft-ietf-siprec-req-09.txt>
|> |> > > (Use Cases
|> |> > > andRequirements for SIP-based
|> |> > > |Media Recording (SIPREC)) toInformational RFC
|> |> > > |
|> |> > > |
|> |> > > |The IESG has received a request from the SIP Recording WG
|> |> > (siprec) to
|> |> > > |consider the following document:
|> |> > > |- 'Use Cases and Requirements for SIP-based Media
|> |> > Recording (SIPREC)'
|> |> > > |  <draft-ietf-siprec-req-09.txt> as an 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 2011-04-20. 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.
|> |> > > |
|> |> > > |The file can be obtained via
|> |> > > |http://datatracker.ietf.org/doc/draft-ietf-siprec-req/
|> |> > > |
|> |> > > |IESG discussion can be tracked via
|> |> > > |http://datatracker.ietf.org/doc/draft-ietf-siprec-req/
|> |> > > |
|> |> > > |
|> |> > > |
|> |> > > |No IPR declarations have been submitted directly on this I-D.
|> |> > > |_______________________________________________
|> |> > > |siprec mailing list
|> |> > > |siprec@ietf.org
|> |> > > |https://www.ietf.org/mailman/listinfo/siprec
|> |> > > _______________________________________________
|> |> > > siprec mailing list
|> |> > > siprec@ietf.org
|> |> > > https://www.ietf.org/mailman/listinfo/siprec
|> |> > >
|> |> > _______________________________________________
|> |> > siprec mailing list
|> |> > siprec@ietf.org
|> |> > https://www.ietf.org/mailman/listinfo/siprec
|> |> >
|> |> _______________________________________________
|> |> siprec mailing list
|> |> siprec@ietf.org
|> |> https://www.ietf.org/mailman/listinfo/siprec
|>

From Leon.Portman@nice.com  Thu Apr 21 06:54:08 2011
Return-Path: <Leon.Portman@nice.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 3F4F3E076F; Thu, 21 Apr 2011 06:54:08 -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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IKsdFUxl7MmJ; Thu, 21 Apr 2011 06:54:06 -0700 (PDT)
Received: from mailil.nice.com (tlvexc07.nice.com [192.114.148.38]) by ietfc.amsl.com (Postfix) with ESMTP id 3C091E077A; Thu, 21 Apr 2011 06:54:06 -0700 (PDT)
Received: from TLVMBX01.nice.com ([192.168.253.242]) by tlvcas02.nice.com ([172.18.253.6]) with mapi; Thu, 21 Apr 2011 16:54:04 +0300
From: Leon Portman <Leon.Portman@nice.com>
To: "Parthasarathi R (partr)" <partr@cisco.com>, "Muthu ArulMozhi Perumal (mperumal)" <mperumal@cisco.com>, "Elwell, John" <john.elwell@siemens-enterprise.com>, "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>, "ietf@ietf.org" <ietf@ietf.org>
Date: Thu, 21 Apr 2011 16:54:03 +0300
Subject: RE: [siprec] Last Call:<draft-ietf-siprec-req-09.txt>(Use CasesandRequirements	forSIP-based MediaRecording	(SIPREC))	toInformational RFC
Thread-Topic: [siprec] Last Call:<draft-ietf-siprec-req-09.txt>(Use CasesandRequirements	forSIP-based MediaRecording	(SIPREC))	toInformational RFC
Thread-Index: Acv0WYBeRuGjGNBtTZSHeqn78QP5xwGEv6YwAAlHtwAAAvtH0AABcMXAAAdJn6AAAIZ7cAAHjozgABTz8IABOK4eoAAEuXiwAABUl5A=
Message-ID: <07465C1D981ABC41A344374066AE1A2C38AB73DDF5@TLVMBX01.nice.com>
References: <20110406125020.17538.70016.idtracker@localhost><1D062974A4845E4D8A343C65380492020533BB70@XMB-BGL-414.cisco.com><A444A0F8084434499206E78C106220CA0875EB5A4E@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38AB73D00B@TLVMBX01.nice.com><A444A0F8084434499206E78C106220CA0875EB5B28@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38AB73D110@TLVMBX01.nice.com><35BCE99A477D6A4986FB2216D8CF2CFD06009D00@XMB-BGL-417.cisco.com><1D062974A4845E4D8A343C65380492020533BD38@XMB-BGL-414.cisco.com><A444A0F8084434499206E78C106220CA0875EB5D69@MCHP058A.global-ad.net> <1D062974A4845E4D8A343C6538049202054256F5@XMB-BGL-414.cisco.com> <A11921905DA1564D9BCF64A6430A623905150BDE@XMB-BGL-411.cisco.com>
In-Reply-To: <A11921905DA1564D9BCF64A6430A623905150BDE@XMB-BGL-411.cisco.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
Cc: "siprec@ietf.org" <siprec@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 Apr 2011 13:54:08 -0000

I agree, we should have dedicated wall clock requirement

Leon

-----Original Message-----
From: Parthasarathi R (partr) [mailto:partr@cisco.com]=20
Sent: Thursday, April 21, 2011 4:51 PM
To: Muthu ArulMozhi Perumal (mperumal); Elwell, John; Ram Mohan R (rmohanr)=
; Leon Portman; ietf@ietf.org
Cc: siprec@ietf.org
Subject: RE: [siprec] Last Call:<draft-ietf-siprec-req-09.txt>(Use Casesand=
Requirements forSIP-based MediaRecording (SIPREC)) toInformational RFC

Muthu/John,

I will prefer to have "a" and "b" as separate requirement as "a" is related=
 to RTP & its model, needs more discussion whereas "b" will be related to S=
IPREC metadata model which will be addressed by the current mechanism of st=
art/stop time of media stream block.

REQ-022: The mechanism MUST provide means for facilitating synchronization =
of the recorded media streams and metadata.

REQ-xxx: The mechanism MUST provide means for facilitating synchronization =
among the recorded media streams

Apart from this, I'm interested to know whether John's Req-023 requirement =
in the below mail will be solved by the current proposed REQ-xxx.=20

Thanks
Partha=20

-----Original Message-----
From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf Of=
 Muthu ArulMozhi Perumal (mperumal)
Sent: Thursday, April 21, 2011 5:15 PM
To: Elwell, John; Ram Mohan R (rmohanr); Leon Portman; ietf@ietf.org
Cc: siprec@ietf.org
Subject: Re: [siprec] Last Call:<draft-ietf-siprec-req-09.txt>(Use
CasesandRequirements forSIP-based MediaRecording (SIPREC)) toInformational =
RFC

+1

I would suggest a small change to REQ-022 that John has drafted below to ma=
ke it more explicit:
=20
REQ-022 The mechanism MUST provide means for facilitating the following eit=
her at storage or at playback:
a. Synchronization among the recorded media streams and b.
Synchronization of the recorded media streams and metadata.

Muthu

|-----Original Message-----
|From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
|Sent: Friday, April 15, 2011 11:53 AM
|To: Muthu ArulMozhi Perumal (mperumal); Ram Mohan R (rmohanr); Leon
Portman; ietf@ietf.org
|Cc: siprec@ietf.org
|Subject: RE: [siprec] Last Call: <draft-ietf-siprec-req-09.txt>(Use
CasesandRequirements for SIP-based
|MediaRecording (SIPREC)) toInformational RFC
|
|So perhaps if we replace REQ-022 and REQ-023 with the requirement that
Muthu has proposed and one
|further requirement, e.g.:
|
|"REQ-022 The mechanism MUST provide means for facilitating
synchronization of the
|recorded media streams and metadata either at storage or at playback.
|
|REQ-023 The mechanism MUST provide means for relating recordings to
wall clock time."
|
|John (as individual)
|
|> -----Original Message-----
|> From: Muthu ArulMozhi Perumal (mperumal) [mailto:mperumal@cisco.com]
|> Sent: 14 April 2011 21:42
|> To: Ram Mohan R (rmohanr); Leon Portman; Elwell, John; ietf@ietf.org
|> Cc: siprec@ietf.org
|> Subject: RE: [siprec] Last Call:
|> <draft-ietf-siprec-req-09.txt>(Use Cases andRequirements for=20
|> SIP-based MediaRecording (SIPREC)) toInformational RFC
|>
|> I agree with John that these seem more like part of a solution rather

|> than actual requirements. In addition, sending the wallclock time at=20
|> media start/end alone may not suffice for achieving inter-media=20
|> synchronization and playback, instead we may need to send the=20
|> wallclock time periodically, like RTCP. For e.g, if there is a codec=20
|> renegotiation in CS the RTP timestamp can restart from a random=20
|> value. If silence suppression is enabled there would be gaps in the=20
|> RTP timestamp.
|>
|> These are things that need to be discussed as part of the solution --

|> the requirement itself should be generic enough, like what I=20
|> described.
|> REQ-022 and REQ-023 we have doesn't seem to clearly indicate the=20
|> purpose.
|>
|> Muthu
|>
|> |-----Original Message-----
|> |From: Ram Mohan R (rmohanr)
|> |Sent: Thursday, April 14, 2011 10:13 PM
|> |To: Leon Portman; Elwell, John; Muthu ArulMozhi Perumal (mperumal);
|> ietf@ietf.org
|> |Cc: siprec@ietf.org
|> |Subject: RE: [siprec] Last Call: <draft-ietf-siprec-req-09.txt>(Use
|> Cases andRequirements for SIP-
|> |based MediaRecording (SIPREC)) toInformational RFC
|> |
|> |We already have  attributes Start-Time / End-time in Media Stream
|> block. This is for the same purpose
|> |to indicate the wall clock time for start/end of media.
|> |
|> |Ram
|> |
|> |> -----Original Message-----
|> |> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On=20
|> |> Behalf Of Leon Portman
|> |> Sent: Thursday, April 14, 2011 9:57 PM
|> |> To: Elwell, John; Muthu ArulMozhi Perumal (mperumal);
ietf@ietf.org
|> |> Cc: siprec@ietf.org
|> |> Subject: Re: [siprec] Last Call:
<draft-ietf-siprec-req-09.txt>(Use
|> |> Cases andRequirements for SIP-based MediaRecording (SIPREC))=20
|> |> toInformational RFC
|> |>
|> |> I am not sure that having wall clock only for CS start is enough,=20
|> |> especially for partial metadata update. I will prefer to have on
|> media
|> |> level
|> |>
|> |> Leon
|> |>
|> |> -----Original Message-----
|> |> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
|> |> Sent: Thursday, April 14, 2011 3:58 PM
|> |> To: Leon Portman; Muthu ArulMozhi Perumal (mperumal);
ietf@ietf.org
|> |> Cc: siprec@ietf.org
|> |> Subject: RE: [siprec] Last Call:
|> <draft-ietf-siprec-req-09.txt> (Use
|> |> Cases andRequirements for SIP-based Media Recording (SIPREC))=20
|> |> toInformational RFC
|> |>
|> |> Understood, but if we have wall clock time for the start of a CS,=20
|> |> wouldn't that be sufficient? The new requirement would cover=20
|> |> synchronization of all media start/stops relative to that time.
|> |>
|> |> John (as individual)
|> |>
|> |>
|> |> > -----Original Message-----
|> |> > From: Leon Portman [mailto:Leon.Portman@nice.com]
|> |> > Sent: 14 April 2011 13:19
|> |> > To: Elwell, John; Muthu ArulMozhi Perumal (mperumal);
|> ietf@ietf.org
|> |> > Cc: siprec@ietf.org
|> |> > Subject: RE: [siprec] Last Call:
|> |> > <draft-ietf-siprec-req-09.txt> (Use Cases andRequirements for=20
|> |> > SIP-based Media Recording (SIPREC)) toInformational RFC
|> |> >
|> |> > Actually REQ-022 and REQ-023 describing not only requirement to=20
|> |> > synchronize between different media streams but more importantly

|> |> > ability to relate them to real world (wall) clock. It is not
only
|> |> > important to playback them correctly but also to know when it
was
|> |> > said.
|> |> > One example is continue trading after closing hour (even for one

|> |> > second is not allowed)
|> |> >
|> |> > And if these media are synchronized to wall clock then they are
|> also
|> |> > synchronized between them thus I am not sure if we need this=20
|> |> > additional requirement.
|> |> >
|> |> > Thanks
|> |> >
|> |> > Leon
|> |> >
|> |> > -----Original Message-----
|> |> > From: siprec-bounces@ietf.org
|> |> > [mailto:siprec-bounces@ietf.org] On Behalf Of Elwell, John
|> |> > Sent: Thursday, April 14, 2011 1:54 PM
|> |> > To: Muthu ArulMozhi Perumal (mperumal); ietf@ietf.org
|> |> > Cc: siprec@ietf.org
|> |> > Subject: Re: [siprec] Last Call:
|> |> > <draft-ietf-siprec-req-09.txt> (Use Cases andRequirements for=20
|> |> > SIP-based Media Recording (SIPREC)) toInformational RFC
|> |> >
|> |> >
|> |> >
|> |> >
|> |> > > -----Original Message-----
|> |> > > From: siprec-bounces@ietf.org
|> |> > > [mailto:siprec-bounces@ietf.org] On Behalf Of Muthu
|> |> > ArulMozhi Perumal
|> |> > > (mperumal)
|> |> > > Sent: 14 April 2011 07:34
|> |> > > To: ietf@ietf.org
|> |> > > Cc: siprec@ietf.org
|> |> > > Subject: Re: [siprec] Last Call:
|> |> > > <draft-ietf-siprec-req-09.txt> (Use Cases andRequirements for=20
|> |> > > SIP-based Media Recording (SIPREC)) toInformational RFC
|> |> > >
|> |> > > I've one major comment. It draft discusses synchronization
|> |> > between the
|> |> > > recorded media streams and synchronized playback, which
|> |> > seem important
|> |> > > for certain applications:
|> |> > >
|> |> > > <snip>
|> |> > > Some applications require the recording of more than one
|> |> > media stream,
|> |> > > possibly of different types. Media are synchronized, either
|> |> > at storage
|> |> > > or at playback.
|> |> > > </snip>
|> |> > >
|> |> > > However, in the requirements section it doesn't seem
|> REQ-022 and
|> |> > > REQ-023 are all that are need and sufficient to
|> achieve this with
|> |> > > needed precision. So, I would suggest adding another
|> requirement
|> as
|> |> > > follows:
|> |> > > The mechanism MUST provide means for facilitating
|> |> > synchronization of
|> |> > > the recorded media streams and metadata either at storage or
at
|> |> > > playback.
|> |> > > This includes, but not limited to, the information
|> needed as per
|> |> > > REQ-022 and REQ-023.
|> |> > [JRE] This seems a reasonable addition. I wonder if the new=20
|> |> > requirement (first sentence only) is sufficient as a
|> |> > **replacement** for REQ-022 and REQ-023. On reading REQ-022 and
|> |> > REQ-023 again, it is not so clear what their purpose
|> was, and they
|> |> > seem to be more like a solution than a requirement.
|> |> > One purpose would certainly be that covered by Muthu's new=20
|> |> > requirement. Was there any other purpose?
|> |> >
|> |> > John
|> |> >
|> |> > >
|> |> > > A nitpick:
|> |> > > Use Case 8
|> |> > > In cases where calls inside or between branches must
|> be recorded,
|> a
|> |> > > centralized recording system in data centers together with
|> |> > telephony
|> |> > > infrastructure (e.g. PBX) me deployed.
|> |> > >
|> |> > > s/me/may be
|> |> > >
|> |> > > Muthu
|> |> > >
|> |> > > |-----Original Message-----
|> |> > > |From: siprec-bounces@ietf.org
[mailto:siprec-bounces@ietf.org]
|> On
|> |> > > Behalf Of The IESG
|> |> > > |Sent: Wednesday, April 06, 2011 6:20 PM
|> |> > > |To: IETF-Announce
|> |> > > |Cc: siprec@ietf.org
|> |> > > |Subject: [siprec] Last Call: <draft-ietf-siprec-req-09.txt>
|> |> > > (Use Cases
|> |> > > andRequirements for SIP-based
|> |> > > |Media Recording (SIPREC)) toInformational RFC
|> |> > > |
|> |> > > |
|> |> > > |The IESG has received a request from the SIP Recording WG
|> |> > (siprec) to
|> |> > > |consider the following document:
|> |> > > |- 'Use Cases and Requirements for SIP-based Media
|> |> > Recording (SIPREC)'
|> |> > > |  <draft-ietf-siprec-req-09.txt> as an 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 2011-04-20. 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.
|> |> > > |
|> |> > > |The file can be obtained via
|> |> > > |http://datatracker.ietf.org/doc/draft-ietf-siprec-req/
|> |> > > |
|> |> > > |IESG discussion can be tracked via=20
|> |> > > |http://datatracker.ietf.org/doc/draft-ietf-siprec-req/
|> |> > > |
|> |> > > |
|> |> > > |
|> |> > > |No IPR declarations have been submitted directly on this I-D.
|> |> > > |_______________________________________________
|> |> > > |siprec mailing list
|> |> > > |siprec@ietf.org
|> |> > > |https://www.ietf.org/mailman/listinfo/siprec
|> |> > > _______________________________________________
|> |> > > siprec mailing list
|> |> > > siprec@ietf.org
|> |> > > https://www.ietf.org/mailman/listinfo/siprec
|> |> > >
|> |> > _______________________________________________
|> |> > siprec mailing list
|> |> > siprec@ietf.org
|> |> > https://www.ietf.org/mailman/listinfo/siprec
|> |> >
|> |> _______________________________________________
|> |> siprec mailing list
|> |> siprec@ietf.org
|> |> https://www.ietf.org/mailman/listinfo/siprec
|>
_______________________________________________
siprec mailing list
siprec@ietf.org
https://www.ietf.org/mailman/listinfo/siprec

From scott.probasco@nokia.com  Thu Apr 21 06:06:14 2011
Return-Path: <scott.probasco@nokia.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 8D4BCE0775; Thu, 21 Apr 2011 06:06:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.099
X-Spam-Level: 
X-Spam-Status: No, score=-3.099 tagged_above=-999 required=5 tests=[AWL=0.500,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zzDQBNbkpT1f; Thu, 21 Apr 2011 06:06:13 -0700 (PDT)
Received: from mgw-da01.nokia.com (smtp.nokia.com [147.243.128.24]) by ietfc.amsl.com (Postfix) with ESMTP id 46419E076F; Thu, 21 Apr 2011 06:06:13 -0700 (PDT)
Received: from vaebh106.NOE.Nokia.com (vaebh106.europe.nokia.com [10.160.244.32]) by mgw-da01.nokia.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p3LD5IIu020071; Thu, 21 Apr 2011 16:05:49 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.5]) by vaebh106.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 21 Apr 2011 16:05:20 +0300
Received: from 008-AM1MMR1-002.mgdnok.nokia.com (65.54.30.57) by NOK-am1MHUB-01.mgdnok.nokia.com (65.54.30.5) with Microsoft SMTP Server (TLS) id 8.2.255.0; Thu, 21 Apr 2011 15:05:19 +0200
Received: from 008-AM1MPN1-023.mgdnok.nokia.com ([169.254.3.210]) by 008-AM1MMR1-002.mgdnok.nokia.com ([65.54.30.57]) with mapi id 14.01.0289.008; Thu, 21 Apr 2011 15:05:16 +0200
From: <scott.probasco@nokia.com>
To: <acooper@cdt.org>
Subject: RE: [paws] WG Review: Protocol to Access White Space database (paws)
Thread-Topic: [paws] WG Review: Protocol to Access White Space database (paws)
Thread-Index: AQHL/rLA5Czj0i0wfE+ujEk1m1AO2ZRlknOAgAE/lXCAATXygIAAQm6A
Date: Thu, 21 Apr 2011 13:05:15 +0000
Message-ID: <88BE24FD9280884487DEAE0CE1FD3A5B06182F@008-AM1MPN1-023.mgdnok.nokia.com>
References: <20110419165634.CD24CE07CF@ietfc.amsl.com> <4DADFE6D.3050107@cs.tcd.ie> <88BE24FD9280884487DEAE0CE1FD3A5B060F1B@008-AM1MPN1-023.mgdnok.nokia.com> <F4035489-7D81-47C9-BE99-3D9DCF1637FA@cdt.org>
In-Reply-To: <F4035489-7D81-47C9-BE99-3D9DCF1637FA@cdt.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-titus-version: 3.2.55
x-tituslabs-classifications-30: TLPropertyRoot=Trial License;Classification=Personal;
x-putclassificationandsendinfointox-header: Classification: Personal Project: Subject: RE: [paws] WG Review: Protocol to Access White Space database (paws) Sender Name: Probasco Scott (Nokia-CIC/Dallas) Sender Email: scott.probasco@nokia.com Send Date: Thursday, April 21, 2011 Send Time: 8:05:10 AM
x-originating-ip: [10.243.2.236]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 21 Apr 2011 13:05:20.0115 (UTC) FILETIME=[C46C3430:01CC0024]
X-Nokia-AV: Clean
X-Mailman-Approved-At: Thu, 21 Apr 2011 08:34:12 -0700
Cc: paws@ietf.org, 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: Thu, 21 Apr 2011 13:06:14 -0000

Hi,

I agree with the concept, just want to be sure the PAWS is not expected to =
develop these security mechanisms (i.e. the tools) as contrasted to includi=
ng or using in PAWS the security tools developed by appropriate expert grou=
ps.

"Inclusion of robust security mechanisms is required:..."
??

Regards,
Scott



-----Original Message-----
From: ext Alissa Cooper [mailto:acooper@cdt.org]=20
Sent: Thursday, April 21, 2011 6:01 AM
To: Probasco Scott (Nokia-CIC/Dallas)
Cc: stephen.farrell@cs.tcd.ie; ietf@ietf.org; paws@ietf.org; iesg@ietf.org
Subject: Re: [paws] WG Review: Protocol to Access White Space database (paw=
s)

On Apr 20, 2011, at 3:41 PM, <scott.probasco@nokia.com> <scott.probasco@nok=
ia.com> wrote:

> Hi Stephen, All,
>=20
> I believe the current wording
>>> Robust security mechanisms are required to prevent:
>>> device identity spoofing, modification of device requests, modification
>>> of channel enablement information, ...
> is acceptable because "mechanisms are required" means they should be in t=
he protocol, it does not mean they cannot be optional. PAWS should support =
Regulator requirements globally, and thus I believe there will be procedure=
s or capabilities which are "required" to be in the protocol but will be "o=
ptional" during run time. Thus different or conflicting requirements from d=
ifferent regions of the world can be supported. (Several regulatory groups =
around the world are still developing their views and requirements).
>=20

Agreed on this point, although I think the charter could make it a little l=
ess ambiguous by saying "Development of robust security mechanisms is requi=
red . . .," that way it's not indicating that the actual mechanisms themsel=
ves will always be required.

Given that device identity will have to be shared in some circumstances, I =
would also add its protection to the end of the list of mechanisms:=20

Development of security mechanisms is required to prevent:
device identity spoofing, modification of device requests, modification
of channel enablement information, impersonation of registered database
services and unauthorized disclosure of a user's location and/or device ide=
ntity.

Alissa

> It's not the time to dig deep into proposed solutions, just my opinion is=
 the current proposed wording is an acceptable definition to allow a Work G=
roup to get started defining the details.
>=20
> Regards,
> Scott
>=20
> -----Original Message-----
> From: paws-bounces@ietf.org [mailto:paws-bounces@ietf.org] On Behalf Of e=
xt Stephen Farrell
> Sent: Tuesday, April 19, 2011 4:28 PM
> To: IETF-Discussion
> Cc: paws@ietf.org; iesg@ietf.org
> Subject: Re: [paws] WG Review: Protocol to Access White Space database (p=
aws)
>=20
>=20
> I think this is a good and timely thing for the IETF to do.
>=20
> One part of this where I think it might be useful to get
> some broader input (which may have happened already, I'm not
> sure) is the following:
>=20
> On 19/04/11 17:56, IESG Secretary wrote:
>> The protocol must protect both the channel enablement process and the
>> privacy of users.=20
>=20
> That part is fine but it goes on to say:
>=20
>> Robust security mechanisms are required to prevent:
>> device identity spoofing, modification of device requests, modification
>> of channel enablement information, ...
>=20
> I'm told (and believe) this in response to (at least) US
> FCC requirements that call for a device ID and sometimes
> serial number to be (securely, for some value of securely)
> sent with the query.
>=20
> Those appear to be real regulatory requirements in the
> US, presumably so the regulator can stomp on someone who
> messes about in the wrong spectrum at the wrong time.
> (The link below [1] may be to the right or wrong bit of
> those US regulations, I'm not at all sure, not being
> from there;-)
>=20
> So my questions:
>=20
> Are there may be similar (or conflicting!) requirements
> elsewhere?
>=20
> Does this bit of the charter text need changes to work
> well for other regions?
>=20
> Separately, I'm not sure how to square those kinds of
> regulatory requirements with protecting privacy where the
> device is carried by a person and has some FCC device ID
> (which lots do I guess) and the person might not want
> the database operator to know who's asking. But I think
> that's ok as something for the WG to figure out since
> the charter already calls for respecting privacy.
>=20
> I'm more concerned in case e.g. some other regional regulation
> called for this protocol to be completely anonymous or
> something, in which case the current charter text might
> be problematic.
>=20
> Cheers,
> Stephen.
>=20
> [1]
> http://ecfr.gpoaccess.gov/cgi/t/text/text-idx?c=3Decfr&sid=3D3e9c322addf1=
f7e897d8c84a6c7aca78&rgn=3Ddiv8&view=3Dtext&node=3D47:1.0.1.1.14.8.243.9&id=
no=3D47
> _______________________________________________
> paws mailing list
> paws@ietf.org
> https://www.ietf.org/mailman/listinfo/paws
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>=20



From partr@cisco.com  Thu Apr 21 06:51:03 2011
Return-Path: <partr@cisco.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 030F0E0689; Thu, 21 Apr 2011 06:51:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.133
X-Spam-Level: 
X-Spam-Status: No, score=-10.133 tagged_above=-999 required=5 tests=[AWL=0.466, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rMDSSzKE5ae1; Thu, 21 Apr 2011 06:51:01 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfc.amsl.com (Postfix) with ESMTP id 8C116E00BE; Thu, 21 Apr 2011 06:51:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=partr@cisco.com; l=11874; q=dns/txt; s=iport; t=1303393860; x=1304603460; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=mLN8YjXKoTsmdriLg7gN1Te9u/NqXoPw9J8AbF+B1F0=; b=IZoxgAPrLS8jdrnPZrE6uQ5BWE58lEB7oA/rkYjmWNVI/lgMkvOEFbBK qCqMw0cNNYmiYUF7GPeIUiC2pqi0/2LXV52Se6vyS5lPsa07/V6WNt3FT Pf0/igbbz3fGr6x/qNPMQeRUo3DJnlNeVzFD4PILEfi2lGoy0i7YM0FVj Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvwAAP00sE2Q/khMgWdsb2JhbACXQI4HFAEBFiYlqCCcWoIig1QEhXKMRQ
X-IronPort-AV: E=Sophos;i="4.64,251,1301875200"; d="scan'208";a="84591744"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-1.cisco.com with ESMTP; 21 Apr 2011 13:50:59 +0000
Received: from xbh-bgl-412.cisco.com (xbh-bgl-412.cisco.com [72.163.129.202]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p3LDoweN019868; Thu, 21 Apr 2011 13:50:59 GMT
Received: from xmb-bgl-411.cisco.com ([72.163.129.207]) by xbh-bgl-412.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 21 Apr 2011 19:20:58 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [siprec] Last Call:<draft-ietf-siprec-req-09.txt>(Use	CasesandRequirements	forSIP-based MediaRecording	(SIPREC))	toInformational RFC
Date: Thu, 21 Apr 2011 19:20:57 +0530
Message-ID: <A11921905DA1564D9BCF64A6430A623905150BDE@XMB-BGL-411.cisco.com>
In-Reply-To: <1D062974A4845E4D8A343C6538049202054256F5@XMB-BGL-414.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] Last Call:<draft-ietf-siprec-req-09.txt>(Use	CasesandRequirements	forSIP-based MediaRecording	(SIPREC))	toInformational RFC
Thread-Index: Acv0WYBeRuGjGNBtTZSHeqn78QP5xwGEv6YwAAlHtwAAAvtH0AABcMXAAAdJn6AAAIZ7cAAHjozgABTz8IABOK4eoAAEuXiw
References: <20110406125020.17538.70016.idtracker@localhost><1D062974A4845E4D8A343C65380492020533BB70@XMB-BGL-414.cisco.com><A444A0F8084434499206E78C106220CA0875EB5A4E@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38AB73D00B@TLVMBX01.nice.com><A444A0F8084434499206E78C106220CA0875EB5B28@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38AB73D110@TLVMBX01.nice.com><35BCE99A477D6A4986FB2216D8CF2CFD06009D00@XMB-BGL-417.cisco.com><1D062974A4845E4D8A343C65380492020533BD38@XMB-BGL-414.cisco.com><A444A0F8084434499206E78C106220CA0875EB5D69@MCHP058A.global-ad.net> <1D062974A4845E4D8A343C6538049202054256F5@XMB-BGL-414.cisco.com>
From: "Parthasarathi R (partr)" <partr@cisco.com>
To: "Muthu ArulMozhi Perumal (mperumal)" <mperumal@cisco.com>, "Elwell, John" <john.elwell@siemens-enterprise.com>, "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>, "Leon Portman" <Leon.Portman@nice.com>, <ietf@ietf.org>
X-OriginalArrivalTime: 21 Apr 2011 13:50:58.0124 (UTC) FILETIME=[246738C0:01CC002B]
X-Mailman-Approved-At: Thu, 21 Apr 2011 08:34:12 -0700
Cc: siprec@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 Apr 2011 13:51:03 -0000

Muthu/John,

I will prefer to have "a" and "b" as separate requirement as "a" is
related to RTP & its model, needs more discussion whereas "b" will be
related to SIPREC metadata model which will be addressed by the current
mechanism of start/stop time of media stream block.

REQ-022: The mechanism MUST provide means for facilitating
synchronization of the recorded media streams and metadata.

REQ-xxx: The mechanism MUST provide means for facilitating
synchronization among the recorded media streams

Apart from this, I'm interested to know whether John's Req-023
requirement in the below mail will be solved by the current proposed
REQ-xxx.=20

Thanks
Partha=20

-----Original Message-----
From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf
Of Muthu ArulMozhi Perumal (mperumal)
Sent: Thursday, April 21, 2011 5:15 PM
To: Elwell, John; Ram Mohan R (rmohanr); Leon Portman; ietf@ietf.org
Cc: siprec@ietf.org
Subject: Re: [siprec] Last Call:<draft-ietf-siprec-req-09.txt>(Use
CasesandRequirements forSIP-based MediaRecording (SIPREC))
toInformational RFC

+1

I would suggest a small change to REQ-022 that John has drafted below to
make it more explicit:
=20
REQ-022 The mechanism MUST provide means for facilitating the following
either at storage or at playback:
a. Synchronization among the recorded media streams and b.
Synchronization of the recorded media streams and metadata.

Muthu

|-----Original Message-----
|From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
|Sent: Friday, April 15, 2011 11:53 AM
|To: Muthu ArulMozhi Perumal (mperumal); Ram Mohan R (rmohanr); Leon
Portman; ietf@ietf.org
|Cc: siprec@ietf.org
|Subject: RE: [siprec] Last Call: <draft-ietf-siprec-req-09.txt>(Use
CasesandRequirements for SIP-based
|MediaRecording (SIPREC)) toInformational RFC
|
|So perhaps if we replace REQ-022 and REQ-023 with the requirement that
Muthu has proposed and one
|further requirement, e.g.:
|
|"REQ-022 The mechanism MUST provide means for facilitating
synchronization of the
|recorded media streams and metadata either at storage or at playback.
|
|REQ-023 The mechanism MUST provide means for relating recordings to
wall clock time."
|
|John (as individual)
|
|> -----Original Message-----
|> From: Muthu ArulMozhi Perumal (mperumal) [mailto:mperumal@cisco.com]
|> Sent: 14 April 2011 21:42
|> To: Ram Mohan R (rmohanr); Leon Portman; Elwell, John; ietf@ietf.org
|> Cc: siprec@ietf.org
|> Subject: RE: [siprec] Last Call:
|> <draft-ietf-siprec-req-09.txt>(Use Cases andRequirements for=20
|> SIP-based MediaRecording (SIPREC)) toInformational RFC
|>
|> I agree with John that these seem more like part of a solution rather

|> than actual requirements. In addition, sending the wallclock time at=20
|> media start/end alone may not suffice for achieving inter-media=20
|> synchronization and playback, instead we may need to send the=20
|> wallclock time periodically, like RTCP. For e.g, if there is a codec=20
|> renegotiation in CS the RTP timestamp can restart from a random=20
|> value. If silence suppression is enabled there would be gaps in the=20
|> RTP timestamp.
|>
|> These are things that need to be discussed as part of the solution --

|> the requirement itself should be generic enough, like what I=20
|> described.
|> REQ-022 and REQ-023 we have doesn't seem to clearly indicate the=20
|> purpose.
|>
|> Muthu
|>
|> |-----Original Message-----
|> |From: Ram Mohan R (rmohanr)
|> |Sent: Thursday, April 14, 2011 10:13 PM
|> |To: Leon Portman; Elwell, John; Muthu ArulMozhi Perumal (mperumal);
|> ietf@ietf.org
|> |Cc: siprec@ietf.org
|> |Subject: RE: [siprec] Last Call: <draft-ietf-siprec-req-09.txt>(Use
|> Cases andRequirements for SIP-
|> |based MediaRecording (SIPREC)) toInformational RFC
|> |
|> |We already have  attributes Start-Time / End-time in Media Stream
|> block. This is for the same purpose
|> |to indicate the wall clock time for start/end of media.
|> |
|> |Ram
|> |
|> |> -----Original Message-----
|> |> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On=20
|> |> Behalf Of Leon Portman
|> |> Sent: Thursday, April 14, 2011 9:57 PM
|> |> To: Elwell, John; Muthu ArulMozhi Perumal (mperumal);
ietf@ietf.org
|> |> Cc: siprec@ietf.org
|> |> Subject: Re: [siprec] Last Call:
<draft-ietf-siprec-req-09.txt>(Use
|> |> Cases andRequirements for SIP-based MediaRecording (SIPREC))=20
|> |> toInformational RFC
|> |>
|> |> I am not sure that having wall clock only for CS start is enough,=20
|> |> especially for partial metadata update. I will prefer to have on
|> media
|> |> level
|> |>
|> |> Leon
|> |>
|> |> -----Original Message-----
|> |> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
|> |> Sent: Thursday, April 14, 2011 3:58 PM
|> |> To: Leon Portman; Muthu ArulMozhi Perumal (mperumal);
ietf@ietf.org
|> |> Cc: siprec@ietf.org
|> |> Subject: RE: [siprec] Last Call:
|> <draft-ietf-siprec-req-09.txt> (Use
|> |> Cases andRequirements for SIP-based Media Recording (SIPREC))=20
|> |> toInformational RFC
|> |>
|> |> Understood, but if we have wall clock time for the start of a CS,=20
|> |> wouldn't that be sufficient? The new requirement would cover=20
|> |> synchronization of all media start/stops relative to that time.
|> |>
|> |> John (as individual)
|> |>
|> |>
|> |> > -----Original Message-----
|> |> > From: Leon Portman [mailto:Leon.Portman@nice.com]
|> |> > Sent: 14 April 2011 13:19
|> |> > To: Elwell, John; Muthu ArulMozhi Perumal (mperumal);
|> ietf@ietf.org
|> |> > Cc: siprec@ietf.org
|> |> > Subject: RE: [siprec] Last Call:
|> |> > <draft-ietf-siprec-req-09.txt> (Use Cases andRequirements for=20
|> |> > SIP-based Media Recording (SIPREC)) toInformational RFC
|> |> >
|> |> > Actually REQ-022 and REQ-023 describing not only requirement to=20
|> |> > synchronize between different media streams but more importantly

|> |> > ability to relate them to real world (wall) clock. It is not
only
|> |> > important to playback them correctly but also to know when it
was
|> |> > said.
|> |> > One example is continue trading after closing hour (even for one

|> |> > second is not allowed)
|> |> >
|> |> > And if these media are synchronized to wall clock then they are
|> also
|> |> > synchronized between them thus I am not sure if we need this=20
|> |> > additional requirement.
|> |> >
|> |> > Thanks
|> |> >
|> |> > Leon
|> |> >
|> |> > -----Original Message-----
|> |> > From: siprec-bounces@ietf.org
|> |> > [mailto:siprec-bounces@ietf.org] On Behalf Of Elwell, John
|> |> > Sent: Thursday, April 14, 2011 1:54 PM
|> |> > To: Muthu ArulMozhi Perumal (mperumal); ietf@ietf.org
|> |> > Cc: siprec@ietf.org
|> |> > Subject: Re: [siprec] Last Call:
|> |> > <draft-ietf-siprec-req-09.txt> (Use Cases andRequirements for=20
|> |> > SIP-based Media Recording (SIPREC)) toInformational RFC
|> |> >
|> |> >
|> |> >
|> |> >
|> |> > > -----Original Message-----
|> |> > > From: siprec-bounces@ietf.org
|> |> > > [mailto:siprec-bounces@ietf.org] On Behalf Of Muthu
|> |> > ArulMozhi Perumal
|> |> > > (mperumal)
|> |> > > Sent: 14 April 2011 07:34
|> |> > > To: ietf@ietf.org
|> |> > > Cc: siprec@ietf.org
|> |> > > Subject: Re: [siprec] Last Call:
|> |> > > <draft-ietf-siprec-req-09.txt> (Use Cases andRequirements for=20
|> |> > > SIP-based Media Recording (SIPREC)) toInformational RFC
|> |> > >
|> |> > > I've one major comment. It draft discusses synchronization
|> |> > between the
|> |> > > recorded media streams and synchronized playback, which
|> |> > seem important
|> |> > > for certain applications:
|> |> > >
|> |> > > <snip>
|> |> > > Some applications require the recording of more than one
|> |> > media stream,
|> |> > > possibly of different types. Media are synchronized, either
|> |> > at storage
|> |> > > or at playback.
|> |> > > </snip>
|> |> > >
|> |> > > However, in the requirements section it doesn't seem
|> REQ-022 and
|> |> > > REQ-023 are all that are need and sufficient to
|> achieve this with
|> |> > > needed precision. So, I would suggest adding another
|> requirement
|> as
|> |> > > follows:
|> |> > > The mechanism MUST provide means for facilitating
|> |> > synchronization of
|> |> > > the recorded media streams and metadata either at storage or
at
|> |> > > playback.
|> |> > > This includes, but not limited to, the information
|> needed as per
|> |> > > REQ-022 and REQ-023.
|> |> > [JRE] This seems a reasonable addition. I wonder if the new=20
|> |> > requirement (first sentence only) is sufficient as a
|> |> > **replacement** for REQ-022 and REQ-023. On reading REQ-022 and
|> |> > REQ-023 again, it is not so clear what their purpose
|> was, and they
|> |> > seem to be more like a solution than a requirement.
|> |> > One purpose would certainly be that covered by Muthu's new=20
|> |> > requirement. Was there any other purpose?
|> |> >
|> |> > John
|> |> >
|> |> > >
|> |> > > A nitpick:
|> |> > > Use Case 8
|> |> > > In cases where calls inside or between branches must
|> be recorded,
|> a
|> |> > > centralized recording system in data centers together with
|> |> > telephony
|> |> > > infrastructure (e.g. PBX) me deployed.
|> |> > >
|> |> > > s/me/may be
|> |> > >
|> |> > > Muthu
|> |> > >
|> |> > > |-----Original Message-----
|> |> > > |From: siprec-bounces@ietf.org
[mailto:siprec-bounces@ietf.org]
|> On
|> |> > > Behalf Of The IESG
|> |> > > |Sent: Wednesday, April 06, 2011 6:20 PM
|> |> > > |To: IETF-Announce
|> |> > > |Cc: siprec@ietf.org
|> |> > > |Subject: [siprec] Last Call: <draft-ietf-siprec-req-09.txt>
|> |> > > (Use Cases
|> |> > > andRequirements for SIP-based
|> |> > > |Media Recording (SIPREC)) toInformational RFC
|> |> > > |
|> |> > > |
|> |> > > |The IESG has received a request from the SIP Recording WG
|> |> > (siprec) to
|> |> > > |consider the following document:
|> |> > > |- 'Use Cases and Requirements for SIP-based Media
|> |> > Recording (SIPREC)'
|> |> > > |  <draft-ietf-siprec-req-09.txt> as an 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 2011-04-20. 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.
|> |> > > |
|> |> > > |The file can be obtained via
|> |> > > |http://datatracker.ietf.org/doc/draft-ietf-siprec-req/
|> |> > > |
|> |> > > |IESG discussion can be tracked via=20
|> |> > > |http://datatracker.ietf.org/doc/draft-ietf-siprec-req/
|> |> > > |
|> |> > > |
|> |> > > |
|> |> > > |No IPR declarations have been submitted directly on this I-D.
|> |> > > |_______________________________________________
|> |> > > |siprec mailing list
|> |> > > |siprec@ietf.org
|> |> > > |https://www.ietf.org/mailman/listinfo/siprec
|> |> > > _______________________________________________
|> |> > > siprec mailing list
|> |> > > siprec@ietf.org
|> |> > > https://www.ietf.org/mailman/listinfo/siprec
|> |> > >
|> |> > _______________________________________________
|> |> > siprec mailing list
|> |> > siprec@ietf.org
|> |> > https://www.ietf.org/mailman/listinfo/siprec
|> |> >
|> |> _______________________________________________
|> |> siprec mailing list
|> |> siprec@ietf.org
|> |> https://www.ietf.org/mailman/listinfo/siprec
|>
_______________________________________________
siprec mailing list
siprec@ietf.org
https://www.ietf.org/mailman/listinfo/siprec

From john.elwell@siemens-enterprise.com  Thu Apr 21 08:44:50 2011
Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 46540E07C5; Thu, 21 Apr 2011 08:44:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.152
X-Spam-Level: 
X-Spam-Status: No, score=-105.152 tagged_above=-999 required=5 tests=[AWL=1.447, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8bCcgogiWOUW; Thu, 21 Apr 2011 08:44:48 -0700 (PDT)
Received: from mail27.messagelabs.com (mail27.messagelabs.com [193.109.254.147]) by ietfc.amsl.com (Postfix) with SMTP id 14C1AE065C; Thu, 21 Apr 2011 08:44:47 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: john.elwell@siemens-enterprise.com
X-Msg-Ref: server-11.tower-27.messagelabs.com!1303400685!20452180!1
X-StarScan-Version: 6.2.9; banners=-,-,-
X-Originating-IP: [62.134.46.9]
Received: (qmail 22270 invoked from network); 21 Apr 2011 15:44:45 -0000
Received: from unknown (HELO senmx11-mx) (62.134.46.9) by server-11.tower-27.messagelabs.com with SMTP; 21 Apr 2011 15:44:45 -0000
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx11-mx (Server) with ESMTP id 505241EB83F2; Thu, 21 Apr 2011 17:44:47 +0200 (CEST)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Thu, 21 Apr 2011 17:44:47 +0200
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: Leon Portman <Leon.Portman@nice.com>, "Parthasarathi R (partr)" <partr@cisco.com>, "Muthu ArulMozhi Perumal (mperumal)" <mperumal@cisco.com>,  "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>, "ietf@ietf.org" <ietf@ietf.org>
Date: Thu, 21 Apr 2011 17:44:46 +0200
Subject: RE: [siprec] Last Call:<draft-ietf-siprec-req-09.txt>(Use CasesandRequirements	forSIP-based MediaRecording	(SIPREC))	toInformational RFC
Thread-Topic: [siprec] Last Call:<draft-ietf-siprec-req-09.txt>(Use CasesandRequirements	forSIP-based MediaRecording	(SIPREC))	toInformational RFC
Thread-Index: Acv0WYBeRuGjGNBtTZSHeqn78QP5xwGEv6YwAAlHtwAAAvtH0AABcMXAAAdJn6AAAIZ7cAAHjozgABTz8IABOK4eoAAEuXiwAABUl5AAA9OvcA==
Message-ID: <A444A0F8084434499206E78C106220CA0875F293BD@MCHP058A.global-ad.net>
References: <20110406125020.17538.70016.idtracker@localhost><1D062974A4845E4D8A343C65380492020533BB70@XMB-BGL-414.cisco.com><A444A0F8084434499206E78C106220CA0875EB5A4E@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38AB73D00B@TLVMBX01.nice.com><A444A0F8084434499206E78C106220CA0875EB5B28@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38AB73D110@TLVMBX01.nice.com><35BCE99A477D6A4986FB2216D8CF2CFD06009D00@XMB-BGL-417.cisco.com><1D062974A4845E4D8A343C65380492020533BD38@XMB-BGL-414.cisco.com><A444A0F8084434499206E78C106220CA0875EB5D69@MCHP058A.global-ad.net> <1D062974A4845E4D8A343C6538049202054256F5@XMB-BGL-414.cisco.com> <A11921905DA1564D9BCF64A6430A623905150BDE@XMB-BGL-411.cisco.com> <07465C1D981ABC41A344374066AE1A2C38AB73DDF5@TLVMBX01.nice.com>
In-Reply-To: <07465C1D981ABC41A344374066AE1A2C38AB73DDF5@TLVMBX01.nice.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
Cc: "siprec@ietf.org" <siprec@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 Apr 2011 15:44:50 -0000

I like the separated REQ-022 and REQ-xxx. In accordance with previous discu=
ssions, I think we need REQ-023 too.

John (as individual)

> -----Original Message-----
> From: Leon Portman [mailto:Leon.Portman@nice.com]=20
> Sent: 21 April 2011 14:54
> To: Parthasarathi R (partr); Muthu ArulMozhi Perumal=20
> (mperumal); Elwell, John; Ram Mohan R (rmohanr); ietf@ietf.org
> Cc: siprec@ietf.org
> Subject: RE: [siprec] Last=20
> Call:<draft-ietf-siprec-req-09.txt>(Use CasesandRequirements=20
> forSIP-based MediaRecording (SIPREC)) toInformational RFC
>=20
> I agree, we should have dedicated wall clock requirement
>=20
> Leon
>=20
> -----Original Message-----
> From: Parthasarathi R (partr) [mailto:partr@cisco.com]=20
> Sent: Thursday, April 21, 2011 4:51 PM
> To: Muthu ArulMozhi Perumal (mperumal); Elwell, John; Ram=20
> Mohan R (rmohanr); Leon Portman; ietf@ietf.org
> Cc: siprec@ietf.org
> Subject: RE: [siprec] Last=20
> Call:<draft-ietf-siprec-req-09.txt>(Use CasesandRequirements=20
> forSIP-based MediaRecording (SIPREC)) toInformational RFC
>=20
> Muthu/John,
>=20
> I will prefer to have "a" and "b" as separate requirement as=20
> "a" is related to RTP & its model, needs more discussion=20
> whereas "b" will be related to SIPREC metadata model which=20
> will be addressed by the current mechanism of start/stop time=20
> of media stream block.
>=20
> REQ-022: The mechanism MUST provide means for facilitating=20
> synchronization of the recorded media streams and metadata.
>=20
> REQ-xxx: The mechanism MUST provide means for facilitating=20
> synchronization among the recorded media streams
>=20
> Apart from this, I'm interested to know whether John's=20
> Req-023 requirement in the below mail will be solved by the=20
> current proposed REQ-xxx.=20
>=20
> Thanks
> Partha=20
>=20
> -----Original Message-----
> From: siprec-bounces@ietf.org=20
> [mailto:siprec-bounces@ietf.org] On Behalf Of Muthu ArulMozhi=20
> Perumal (mperumal)
> Sent: Thursday, April 21, 2011 5:15 PM
> To: Elwell, John; Ram Mohan R (rmohanr); Leon Portman; ietf@ietf.org
> Cc: siprec@ietf.org
> Subject: Re: [siprec] Last Call:<draft-ietf-siprec-req-09.txt>(Use
> CasesandRequirements forSIP-based MediaRecording (SIPREC))=20
> toInformational RFC
>=20
> +1
>=20
> I would suggest a small change to REQ-022 that John has=20
> drafted below to make it more explicit:
> =20
> REQ-022 The mechanism MUST provide means for facilitating the=20
> following either at storage or at playback:
> a. Synchronization among the recorded media streams and b.
> Synchronization of the recorded media streams and metadata.
>=20
> Muthu
>=20
> |-----Original Message-----
> |From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> |Sent: Friday, April 15, 2011 11:53 AM
> |To: Muthu ArulMozhi Perumal (mperumal); Ram Mohan R (rmohanr); Leon
> Portman; ietf@ietf.org
> |Cc: siprec@ietf.org
> |Subject: RE: [siprec] Last Call: <draft-ietf-siprec-req-09.txt>(Use
> CasesandRequirements for SIP-based
> |MediaRecording (SIPREC)) toInformational RFC
> |
> |So perhaps if we replace REQ-022 and REQ-023 with the=20
> requirement that
> Muthu has proposed and one
> |further requirement, e.g.:
> |
> |"REQ-022 The mechanism MUST provide means for facilitating
> synchronization of the
> |recorded media streams and metadata either at storage or at playback.
> |
> |REQ-023 The mechanism MUST provide means for relating recordings to
> wall clock time."
> |
> |John (as individual)
> |
> |> -----Original Message-----
> |> From: Muthu ArulMozhi Perumal (mperumal)=20
> [mailto:mperumal@cisco.com]
> |> Sent: 14 April 2011 21:42
> |> To: Ram Mohan R (rmohanr); Leon Portman; Elwell, John;=20
> ietf@ietf.org
> |> Cc: siprec@ietf.org
> |> Subject: RE: [siprec] Last Call:
> |> <draft-ietf-siprec-req-09.txt>(Use Cases andRequirements for=20
> |> SIP-based MediaRecording (SIPREC)) toInformational RFC
> |>
> |> I agree with John that these seem more like part of a=20
> solution rather
>=20
> |> than actual requirements. In addition, sending the=20
> wallclock time at=20
> |> media start/end alone may not suffice for achieving inter-media=20
> |> synchronization and playback, instead we may need to send the=20
> |> wallclock time periodically, like RTCP. For e.g, if there=20
> is a codec=20
> |> renegotiation in CS the RTP timestamp can restart from a random=20
> |> value. If silence suppression is enabled there would be=20
> gaps in the=20
> |> RTP timestamp.
> |>
> |> These are things that need to be discussed as part of the=20
> solution --
>=20
> |> the requirement itself should be generic enough, like what I=20
> |> described.
> |> REQ-022 and REQ-023 we have doesn't seem to clearly indicate the=20
> |> purpose.
> |>
> |> Muthu
> |>
> |> |-----Original Message-----
> |> |From: Ram Mohan R (rmohanr)
> |> |Sent: Thursday, April 14, 2011 10:13 PM
> |> |To: Leon Portman; Elwell, John; Muthu ArulMozhi Perumal=20
> (mperumal);
> |> ietf@ietf.org
> |> |Cc: siprec@ietf.org
> |> |Subject: RE: [siprec] Last Call:=20
> <draft-ietf-siprec-req-09.txt>(Use
> |> Cases andRequirements for SIP-
> |> |based MediaRecording (SIPREC)) toInformational RFC
> |> |
> |> |We already have  attributes Start-Time / End-time in Media Stream
> |> block. This is for the same purpose
> |> |to indicate the wall clock time for start/end of media.
> |> |
> |> |Ram
> |> |
> |> |> -----Original Message-----
> |> |> From: siprec-bounces@ietf.org=20
> [mailto:siprec-bounces@ietf.org] On=20
> |> |> Behalf Of Leon Portman
> |> |> Sent: Thursday, April 14, 2011 9:57 PM
> |> |> To: Elwell, John; Muthu ArulMozhi Perumal (mperumal);
> ietf@ietf.org
> |> |> Cc: siprec@ietf.org
> |> |> Subject: Re: [siprec] Last Call:
> <draft-ietf-siprec-req-09.txt>(Use
> |> |> Cases andRequirements for SIP-based MediaRecording (SIPREC))=20
> |> |> toInformational RFC
> |> |>
> |> |> I am not sure that having wall clock only for CS start=20
> is enough,=20
> |> |> especially for partial metadata update. I will prefer to have on
> |> media
> |> |> level
> |> |>
> |> |> Leon
> |> |>
> |> |> -----Original Message-----
> |> |> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
> |> |> Sent: Thursday, April 14, 2011 3:58 PM
> |> |> To: Leon Portman; Muthu ArulMozhi Perumal (mperumal);
> ietf@ietf.org
> |> |> Cc: siprec@ietf.org
> |> |> Subject: RE: [siprec] Last Call:
> |> <draft-ietf-siprec-req-09.txt> (Use
> |> |> Cases andRequirements for SIP-based Media Recording (SIPREC))=20
> |> |> toInformational RFC
> |> |>
> |> |> Understood, but if we have wall clock time for the=20
> start of a CS,=20
> |> |> wouldn't that be sufficient? The new requirement would cover=20
> |> |> synchronization of all media start/stops relative to that time.
> |> |>
> |> |> John (as individual)
> |> |>
> |> |>
> |> |> > -----Original Message-----
> |> |> > From: Leon Portman [mailto:Leon.Portman@nice.com]
> |> |> > Sent: 14 April 2011 13:19
> |> |> > To: Elwell, John; Muthu ArulMozhi Perumal (mperumal);
> |> ietf@ietf.org
> |> |> > Cc: siprec@ietf.org
> |> |> > Subject: RE: [siprec] Last Call:
> |> |> > <draft-ietf-siprec-req-09.txt> (Use Cases andRequirements for=20
> |> |> > SIP-based Media Recording (SIPREC)) toInformational RFC
> |> |> >
> |> |> > Actually REQ-022 and REQ-023 describing not only=20
> requirement to=20
> |> |> > synchronize between different media streams but more=20
> importantly
>=20
> |> |> > ability to relate them to real world (wall) clock. It is not
> only
> |> |> > important to playback them correctly but also to know when it
> was
> |> |> > said.
> |> |> > One example is continue trading after closing hour=20
> (even for one
>=20
> |> |> > second is not allowed)
> |> |> >
> |> |> > And if these media are synchronized to wall clock=20
> then they are
> |> also
> |> |> > synchronized between them thus I am not sure if we need this=20
> |> |> > additional requirement.
> |> |> >
> |> |> > Thanks
> |> |> >
> |> |> > Leon
> |> |> >
> |> |> > -----Original Message-----
> |> |> > From: siprec-bounces@ietf.org
> |> |> > [mailto:siprec-bounces@ietf.org] On Behalf Of Elwell, John
> |> |> > Sent: Thursday, April 14, 2011 1:54 PM
> |> |> > To: Muthu ArulMozhi Perumal (mperumal); ietf@ietf.org
> |> |> > Cc: siprec@ietf.org
> |> |> > Subject: Re: [siprec] Last Call:
> |> |> > <draft-ietf-siprec-req-09.txt> (Use Cases andRequirements for=20
> |> |> > SIP-based Media Recording (SIPREC)) toInformational RFC
> |> |> >
> |> |> >
> |> |> >
> |> |> >
> |> |> > > -----Original Message-----
> |> |> > > From: siprec-bounces@ietf.org
> |> |> > > [mailto:siprec-bounces@ietf.org] On Behalf Of Muthu
> |> |> > ArulMozhi Perumal
> |> |> > > (mperumal)
> |> |> > > Sent: 14 April 2011 07:34
> |> |> > > To: ietf@ietf.org
> |> |> > > Cc: siprec@ietf.org
> |> |> > > Subject: Re: [siprec] Last Call:
> |> |> > > <draft-ietf-siprec-req-09.txt> (Use Cases=20
> andRequirements for=20
> |> |> > > SIP-based Media Recording (SIPREC)) toInformational RFC
> |> |> > >
> |> |> > > I've one major comment. It draft discusses synchronization
> |> |> > between the
> |> |> > > recorded media streams and synchronized playback, which
> |> |> > seem important
> |> |> > > for certain applications:
> |> |> > >
> |> |> > > <snip>
> |> |> > > Some applications require the recording of more than one
> |> |> > media stream,
> |> |> > > possibly of different types. Media are synchronized, either
> |> |> > at storage
> |> |> > > or at playback.
> |> |> > > </snip>
> |> |> > >
> |> |> > > However, in the requirements section it doesn't seem
> |> REQ-022 and
> |> |> > > REQ-023 are all that are need and sufficient to
> |> achieve this with
> |> |> > > needed precision. So, I would suggest adding another
> |> requirement
> |> as
> |> |> > > follows:
> |> |> > > The mechanism MUST provide means for facilitating
> |> |> > synchronization of
> |> |> > > the recorded media streams and metadata either at storage or
> at
> |> |> > > playback.
> |> |> > > This includes, but not limited to, the information
> |> needed as per
> |> |> > > REQ-022 and REQ-023.
> |> |> > [JRE] This seems a reasonable addition. I wonder if the new=20
> |> |> > requirement (first sentence only) is sufficient as a
> |> |> > **replacement** for REQ-022 and REQ-023. On reading=20
> REQ-022 and
> |> |> > REQ-023 again, it is not so clear what their purpose
> |> was, and they
> |> |> > seem to be more like a solution than a requirement.
> |> |> > One purpose would certainly be that covered by Muthu's new=20
> |> |> > requirement. Was there any other purpose?
> |> |> >
> |> |> > John
> |> |> >
> |> |> > >
> |> |> > > A nitpick:
> |> |> > > Use Case 8
> |> |> > > In cases where calls inside or between branches must
> |> be recorded,
> |> a
> |> |> > > centralized recording system in data centers together with
> |> |> > telephony
> |> |> > > infrastructure (e.g. PBX) me deployed.
> |> |> > >
> |> |> > > s/me/may be
> |> |> > >
> |> |> > > Muthu
> |> |> > >
> |> |> > > |-----Original Message-----
> |> |> > > |From: siprec-bounces@ietf.org
> [mailto:siprec-bounces@ietf.org]
> |> On
> |> |> > > Behalf Of The IESG
> |> |> > > |Sent: Wednesday, April 06, 2011 6:20 PM
> |> |> > > |To: IETF-Announce
> |> |> > > |Cc: siprec@ietf.org
> |> |> > > |Subject: [siprec] Last Call: <draft-ietf-siprec-req-09.txt>
> |> |> > > (Use Cases
> |> |> > > andRequirements for SIP-based
> |> |> > > |Media Recording (SIPREC)) toInformational RFC
> |> |> > > |
> |> |> > > |
> |> |> > > |The IESG has received a request from the SIP Recording WG
> |> |> > (siprec) to
> |> |> > > |consider the following document:
> |> |> > > |- 'Use Cases and Requirements for SIP-based Media
> |> |> > Recording (SIPREC)'
> |> |> > > |  <draft-ietf-siprec-req-09.txt> as an 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 2011-04-20. 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.
> |> |> > > |
> |> |> > > |The file can be obtained via
> |> |> > > |http://datatracker.ietf.org/doc/draft-ietf-siprec-req/
> |> |> > > |
> |> |> > > |IESG discussion can be tracked via=20
> |> |> > > |http://datatracker.ietf.org/doc/draft-ietf-siprec-req/
> |> |> > > |
> |> |> > > |
> |> |> > > |
> |> |> > > |No IPR declarations have been submitted directly=20
> on this I-D.
> |> |> > > |_______________________________________________
> |> |> > > |siprec mailing list
> |> |> > > |siprec@ietf.org
> |> |> > > |https://www.ietf.org/mailman/listinfo/siprec
> |> |> > > _______________________________________________
> |> |> > > siprec mailing list
> |> |> > > siprec@ietf.org
> |> |> > > https://www.ietf.org/mailman/listinfo/siprec
> |> |> > >
> |> |> > _______________________________________________
> |> |> > siprec mailing list
> |> |> > siprec@ietf.org
> |> |> > https://www.ietf.org/mailman/listinfo/siprec
> |> |> >
> |> |> _______________________________________________
> |> |> siprec mailing list
> |> |> siprec@ietf.org
> |> |> https://www.ietf.org/mailman/listinfo/siprec
> |>
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec
> =

From mperumal@cisco.com  Thu Apr 21 08:57:50 2011
Return-Path: <mperumal@cisco.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 60068E07C7; Thu, 21 Apr 2011 08:57:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.044
X-Spam-Level: 
X-Spam-Status: No, score=-9.044 tagged_above=-999 required=5 tests=[AWL=-0.745, BAYES_00=-2.599, MANGLED_TOOL=2.3, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W0uM9CxJxhCx; Thu, 21 Apr 2011 08:57:48 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfc.amsl.com (Postfix) with ESMTP id 896CAE065C; Thu, 21 Apr 2011 08:57:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=mperumal@cisco.com; l=14565; q=dns/txt; s=iport; t=1303401467; x=1304611067; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=7WL/QxFAAeysO0Agg6So5vwAaAI/RF8NVyx6aLnIC08=; b=dmnUElo2qRhlE7xjfP6D6TdFFG9SP9vzvqplZDLp/eRvKrgNXfGoQZbV Z+f2CxLyfNm8P/xzDwVGA1CapY0orsBHOfawgYuyOQ25cVeFW13qPB8mf 1tWOkn9NNk83YrXozdjGZhrC42y0LtOaMPhE4ZuHPOzUQcTIMcdtCIe9d Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvwAADJTsE2Q/khMgWdsb2JhbACXQI4HFAEBFiYliHCeUJxegiKDVASFcoxF
X-IronPort-AV: E=Sophos;i="4.64,252,1301875200"; d="scan'208";a="26642991"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-2.cisco.com with ESMTP; 21 Apr 2011 15:57:46 +0000
Received: from xbh-bgl-411.cisco.com (xbh-bgl-411.cisco.com [72.163.129.201]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p3LFvf4R022603; Thu, 21 Apr 2011 15:57:46 GMT
Received: from xmb-bgl-414.cisco.com ([72.163.129.210]) by xbh-bgl-411.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 21 Apr 2011 21:27:44 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [siprec] Last Call:<draft-ietf-siprec-req-09.txt>(UseCasesandRequirements	forSIP-based MediaRecording	(SIPREC))	toInformational RFC
Date: Thu, 21 Apr 2011 21:27:42 +0530
Message-ID: <1D062974A4845E4D8A343C653804920205425772@XMB-BGL-414.cisco.com>
In-Reply-To: <A444A0F8084434499206E78C106220CA0875F293BD@MCHP058A.global-ad.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] Last Call:<draft-ietf-siprec-req-09.txt>(UseCasesandRequirements	forSIP-based MediaRecording	(SIPREC))	toInformational RFC
Thread-Index: Acv0WYBeRuGjGNBtTZSHeqn78QP5xwGEv6YwAAlHtwAAAvtH0AABcMXAAAdJn6AAAIZ7cAAHjozgABTz8IABOK4eoAAEuXiwAABUl5AAA9OvcAAAHn0A
References: <20110406125020.17538.70016.idtracker@localhost><1D062974A4845E4D8A343C65380492020533BB70@XMB-BGL-414.cisco.com><A444A0F8084434499206E78C106220CA0875EB5A4E@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38AB73D00B@TLVMBX01.nice.com><A444A0F8084434499206E78C106220CA0875EB5B28@MCHP058A.global-ad.net><07465C1D981ABC41A344374066AE1A2C38AB73D110@TLVMBX01.nice.com><35BCE99A477D6A4986FB2216D8CF2CFD06009D00@XMB-BGL-417.cisco.com><1D062974A4845E4D8A343C65380492020533BD38@XMB-BGL-414.cisco.com><A444A0F8084434499206E78C106220CA0875EB5D69@MCHP058A.global-ad.net> <1D062974A4845E4D8A343C6538049202054256F5@XMB-BGL-414.cisco.com> <A11921905DA1564D9BCF64A6430A623905150BDE@XMB-BGL-411.cisco.com> <07465C1D981ABC41A344374066AE1A2C38AB73DDF5@TLVMBX01.nice.com> <A444A0F8084434499206E78C106220CA0875F293BD@MCHP058A.global-ad.net>
From: "Muthu ArulMozhi Perumal (mperumal)" <mperumal@cisco.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>, "Leon Portman" <Leon.Portman@nice.com>, "Parthasarathi R (partr)" <partr@cisco.com>, "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>, <ietf@ietf.org>
X-OriginalArrivalTime: 21 Apr 2011 15:57:44.0051 (UTC) FILETIME=[D9E39430:01CC003C]
Cc: siprec@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 Apr 2011 15:57:50 -0000

I am fine with separated REQ-022 and REQ-xxx. Though the solution for
REQ-022 and REQ-xxx could be based on the wallclock time, having an
explicit REQ-023 looks fine from a requirements perspective.

Muthu

|-----Original Message-----
|From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
|Sent: Thursday, April 21, 2011 9:15 PM
|To: Leon Portman; Parthasarathi R (partr); Muthu ArulMozhi Perumal
(mperumal); Ram Mohan R (rmohanr);
|ietf@ietf.org
|Cc: siprec@ietf.org
|Subject: RE: [siprec] Last
Call:<draft-ietf-siprec-req-09.txt>(UseCasesandRequirements forSIP-based
|MediaRecording (SIPREC)) toInformational RFC
|
|I like the separated REQ-022 and REQ-xxx. In accordance with previous
discussions, I think we need
|REQ-023 too.
|
|John (as individual)
|
|> -----Original Message-----
|> From: Leon Portman [mailto:Leon.Portman@nice.com]
|> Sent: 21 April 2011 14:54
|> To: Parthasarathi R (partr); Muthu ArulMozhi Perumal
|> (mperumal); Elwell, John; Ram Mohan R (rmohanr); ietf@ietf.org
|> Cc: siprec@ietf.org
|> Subject: RE: [siprec] Last
|> Call:<draft-ietf-siprec-req-09.txt>(Use CasesandRequirements
|> forSIP-based MediaRecording (SIPREC)) toInformational RFC
|>
|> I agree, we should have dedicated wall clock requirement
|>
|> Leon
|>
|> -----Original Message-----
|> From: Parthasarathi R (partr) [mailto:partr@cisco.com]
|> Sent: Thursday, April 21, 2011 4:51 PM
|> To: Muthu ArulMozhi Perumal (mperumal); Elwell, John; Ram
|> Mohan R (rmohanr); Leon Portman; ietf@ietf.org
|> Cc: siprec@ietf.org
|> Subject: RE: [siprec] Last
|> Call:<draft-ietf-siprec-req-09.txt>(Use CasesandRequirements
|> forSIP-based MediaRecording (SIPREC)) toInformational RFC
|>
|> Muthu/John,
|>
|> I will prefer to have "a" and "b" as separate requirement as
|> "a" is related to RTP & its model, needs more discussion
|> whereas "b" will be related to SIPREC metadata model which
|> will be addressed by the current mechanism of start/stop time
|> of media stream block.
|>
|> REQ-022: The mechanism MUST provide means for facilitating
|> synchronization of the recorded media streams and metadata.
|>
|> REQ-xxx: The mechanism MUST provide means for facilitating
|> synchronization among the recorded media streams
|>
|> Apart from this, I'm interested to know whether John's
|> Req-023 requirement in the below mail will be solved by the
|> current proposed REQ-xxx.
|>
|> Thanks
|> Partha
|>
|> -----Original Message-----
|> From: siprec-bounces@ietf.org
|> [mailto:siprec-bounces@ietf.org] On Behalf Of Muthu ArulMozhi
|> Perumal (mperumal)
|> Sent: Thursday, April 21, 2011 5:15 PM
|> To: Elwell, John; Ram Mohan R (rmohanr); Leon Portman; ietf@ietf.org
|> Cc: siprec@ietf.org
|> Subject: Re: [siprec] Last Call:<draft-ietf-siprec-req-09.txt>(Use
|> CasesandRequirements forSIP-based MediaRecording (SIPREC))
|> toInformational RFC
|>
|> +1
|>
|> I would suggest a small change to REQ-022 that John has
|> drafted below to make it more explicit:
|>
|> REQ-022 The mechanism MUST provide means for facilitating the
|> following either at storage or at playback:
|> a. Synchronization among the recorded media streams and b.
|> Synchronization of the recorded media streams and metadata.
|>
|> Muthu
|>
|> |-----Original Message-----
|> |From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
|> |Sent: Friday, April 15, 2011 11:53 AM
|> |To: Muthu ArulMozhi Perumal (mperumal); Ram Mohan R (rmohanr); Leon
|> Portman; ietf@ietf.org
|> |Cc: siprec@ietf.org
|> |Subject: RE: [siprec] Last Call: <draft-ietf-siprec-req-09.txt>(Use
|> CasesandRequirements for SIP-based
|> |MediaRecording (SIPREC)) toInformational RFC
|> |
|> |So perhaps if we replace REQ-022 and REQ-023 with the
|> requirement that
|> Muthu has proposed and one
|> |further requirement, e.g.:
|> |
|> |"REQ-022 The mechanism MUST provide means for facilitating
|> synchronization of the
|> |recorded media streams and metadata either at storage or at
playback.
|> |
|> |REQ-023 The mechanism MUST provide means for relating recordings to
|> wall clock time."
|> |
|> |John (as individual)
|> |
|> |> -----Original Message-----
|> |> From: Muthu ArulMozhi Perumal (mperumal)
|> [mailto:mperumal@cisco.com]
|> |> Sent: 14 April 2011 21:42
|> |> To: Ram Mohan R (rmohanr); Leon Portman; Elwell, John;
|> ietf@ietf.org
|> |> Cc: siprec@ietf.org
|> |> Subject: RE: [siprec] Last Call:
|> |> <draft-ietf-siprec-req-09.txt>(Use Cases andRequirements for
|> |> SIP-based MediaRecording (SIPREC)) toInformational RFC
|> |>
|> |> I agree with John that these seem more like part of a
|> solution rather
|>
|> |> than actual requirements. In addition, sending the
|> wallclock time at
|> |> media start/end alone may not suffice for achieving inter-media
|> |> synchronization and playback, instead we may need to send the
|> |> wallclock time periodically, like RTCP. For e.g, if there
|> is a codec
|> |> renegotiation in CS the RTP timestamp can restart from a random
|> |> value. If silence suppression is enabled there would be
|> gaps in the
|> |> RTP timestamp.
|> |>
|> |> These are things that need to be discussed as part of the
|> solution --
|>
|> |> the requirement itself should be generic enough, like what I
|> |> described.
|> |> REQ-022 and REQ-023 we have doesn't seem to clearly indicate the
|> |> purpose.
|> |>
|> |> Muthu
|> |>
|> |> |-----Original Message-----
|> |> |From: Ram Mohan R (rmohanr)
|> |> |Sent: Thursday, April 14, 2011 10:13 PM
|> |> |To: Leon Portman; Elwell, John; Muthu ArulMozhi Perumal
|> (mperumal);
|> |> ietf@ietf.org
|> |> |Cc: siprec@ietf.org
|> |> |Subject: RE: [siprec] Last Call:
|> <draft-ietf-siprec-req-09.txt>(Use
|> |> Cases andRequirements for SIP-
|> |> |based MediaRecording (SIPREC)) toInformational RFC
|> |> |
|> |> |We already have  attributes Start-Time / End-time in Media Stream
|> |> block. This is for the same purpose
|> |> |to indicate the wall clock time for start/end of media.
|> |> |
|> |> |Ram
|> |> |
|> |> |> -----Original Message-----
|> |> |> From: siprec-bounces@ietf.org
|> [mailto:siprec-bounces@ietf.org] On
|> |> |> Behalf Of Leon Portman
|> |> |> Sent: Thursday, April 14, 2011 9:57 PM
|> |> |> To: Elwell, John; Muthu ArulMozhi Perumal (mperumal);
|> ietf@ietf.org
|> |> |> Cc: siprec@ietf.org
|> |> |> Subject: Re: [siprec] Last Call:
|> <draft-ietf-siprec-req-09.txt>(Use
|> |> |> Cases andRequirements for SIP-based MediaRecording (SIPREC))
|> |> |> toInformational RFC
|> |> |>
|> |> |> I am not sure that having wall clock only for CS start
|> is enough,
|> |> |> especially for partial metadata update. I will prefer to have
on
|> |> media
|> |> |> level
|> |> |>
|> |> |> Leon
|> |> |>
|> |> |> -----Original Message-----
|> |> |> From: Elwell, John [mailto:john.elwell@siemens-enterprise.com]
|> |> |> Sent: Thursday, April 14, 2011 3:58 PM
|> |> |> To: Leon Portman; Muthu ArulMozhi Perumal (mperumal);
|> ietf@ietf.org
|> |> |> Cc: siprec@ietf.org
|> |> |> Subject: RE: [siprec] Last Call:
|> |> <draft-ietf-siprec-req-09.txt> (Use
|> |> |> Cases andRequirements for SIP-based Media Recording (SIPREC))
|> |> |> toInformational RFC
|> |> |>
|> |> |> Understood, but if we have wall clock time for the
|> start of a CS,
|> |> |> wouldn't that be sufficient? The new requirement would cover
|> |> |> synchronization of all media start/stops relative to that time.
|> |> |>
|> |> |> John (as individual)
|> |> |>
|> |> |>
|> |> |> > -----Original Message-----
|> |> |> > From: Leon Portman [mailto:Leon.Portman@nice.com]
|> |> |> > Sent: 14 April 2011 13:19
|> |> |> > To: Elwell, John; Muthu ArulMozhi Perumal (mperumal);
|> |> ietf@ietf.org
|> |> |> > Cc: siprec@ietf.org
|> |> |> > Subject: RE: [siprec] Last Call:
|> |> |> > <draft-ietf-siprec-req-09.txt> (Use Cases andRequirements for
|> |> |> > SIP-based Media Recording (SIPREC)) toInformational RFC
|> |> |> >
|> |> |> > Actually REQ-022 and REQ-023 describing not only
|> requirement to
|> |> |> > synchronize between different media streams but more
|> importantly
|>
|> |> |> > ability to relate them to real world (wall) clock. It is not
|> only
|> |> |> > important to playback them correctly but also to know when it
|> was
|> |> |> > said.
|> |> |> > One example is continue trading after closing hour
|> (even for one
|>
|> |> |> > second is not allowed)
|> |> |> >
|> |> |> > And if these media are synchronized to wall clock
|> then they are
|> |> also
|> |> |> > synchronized between them thus I am not sure if we need this
|> |> |> > additional requirement.
|> |> |> >
|> |> |> > Thanks
|> |> |> >
|> |> |> > Leon
|> |> |> >
|> |> |> > -----Original Message-----
|> |> |> > From: siprec-bounces@ietf.org
|> |> |> > [mailto:siprec-bounces@ietf.org] On Behalf Of Elwell, John
|> |> |> > Sent: Thursday, April 14, 2011 1:54 PM
|> |> |> > To: Muthu ArulMozhi Perumal (mperumal); ietf@ietf.org
|> |> |> > Cc: siprec@ietf.org
|> |> |> > Subject: Re: [siprec] Last Call:
|> |> |> > <draft-ietf-siprec-req-09.txt> (Use Cases andRequirements for
|> |> |> > SIP-based Media Recording (SIPREC)) toInformational RFC
|> |> |> >
|> |> |> >
|> |> |> >
|> |> |> >
|> |> |> > > -----Original Message-----
|> |> |> > > From: siprec-bounces@ietf.org
|> |> |> > > [mailto:siprec-bounces@ietf.org] On Behalf Of Muthu
|> |> |> > ArulMozhi Perumal
|> |> |> > > (mperumal)
|> |> |> > > Sent: 14 April 2011 07:34
|> |> |> > > To: ietf@ietf.org
|> |> |> > > Cc: siprec@ietf.org
|> |> |> > > Subject: Re: [siprec] Last Call:
|> |> |> > > <draft-ietf-siprec-req-09.txt> (Use Cases
|> andRequirements for
|> |> |> > > SIP-based Media Recording (SIPREC)) toInformational RFC
|> |> |> > >
|> |> |> > > I've one major comment. It draft discusses synchronization
|> |> |> > between the
|> |> |> > > recorded media streams and synchronized playback, which
|> |> |> > seem important
|> |> |> > > for certain applications:
|> |> |> > >
|> |> |> > > <snip>
|> |> |> > > Some applications require the recording of more than one
|> |> |> > media stream,
|> |> |> > > possibly of different types. Media are synchronized, either
|> |> |> > at storage
|> |> |> > > or at playback.
|> |> |> > > </snip>
|> |> |> > >
|> |> |> > > However, in the requirements section it doesn't seem
|> |> REQ-022 and
|> |> |> > > REQ-023 are all that are need and sufficient to
|> |> achieve this with
|> |> |> > > needed precision. So, I would suggest adding another
|> |> requirement
|> |> as
|> |> |> > > follows:
|> |> |> > > The mechanism MUST provide means for facilitating
|> |> |> > synchronization of
|> |> |> > > the recorded media streams and metadata either at storage
or
|> at
|> |> |> > > playback.
|> |> |> > > This includes, but not limited to, the information
|> |> needed as per
|> |> |> > > REQ-022 and REQ-023.
|> |> |> > [JRE] This seems a reasonable addition. I wonder if the new
|> |> |> > requirement (first sentence only) is sufficient as a
|> |> |> > **replacement** for REQ-022 and REQ-023. On reading
|> REQ-022 and
|> |> |> > REQ-023 again, it is not so clear what their purpose
|> |> was, and they
|> |> |> > seem to be more like a solution than a requirement.
|> |> |> > One purpose would certainly be that covered by Muthu's new
|> |> |> > requirement. Was there any other purpose?
|> |> |> >
|> |> |> > John
|> |> |> >
|> |> |> > >
|> |> |> > > A nitpick:
|> |> |> > > Use Case 8
|> |> |> > > In cases where calls inside or between branches must
|> |> be recorded,
|> |> a
|> |> |> > > centralized recording system in data centers together with
|> |> |> > telephony
|> |> |> > > infrastructure (e.g. PBX) me deployed.
|> |> |> > >
|> |> |> > > s/me/may be
|> |> |> > >
|> |> |> > > Muthu
|> |> |> > >
|> |> |> > > |-----Original Message-----
|> |> |> > > |From: siprec-bounces@ietf.org
|> [mailto:siprec-bounces@ietf.org]
|> |> On
|> |> |> > > Behalf Of The IESG
|> |> |> > > |Sent: Wednesday, April 06, 2011 6:20 PM
|> |> |> > > |To: IETF-Announce
|> |> |> > > |Cc: siprec@ietf.org
|> |> |> > > |Subject: [siprec] Last Call:
<draft-ietf-siprec-req-09.txt>
|> |> |> > > (Use Cases
|> |> |> > > andRequirements for SIP-based
|> |> |> > > |Media Recording (SIPREC)) toInformational RFC
|> |> |> > > |
|> |> |> > > |
|> |> |> > > |The IESG has received a request from the SIP Recording WG
|> |> |> > (siprec) to
|> |> |> > > |consider the following document:
|> |> |> > > |- 'Use Cases and Requirements for SIP-based Media
|> |> |> > Recording (SIPREC)'
|> |> |> > > |  <draft-ietf-siprec-req-09.txt> as an 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 2011-04-20. 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.
|> |> |> > > |
|> |> |> > > |The file can be obtained via
|> |> |> > > |http://datatracker.ietf.org/doc/draft-ietf-siprec-req/
|> |> |> > > |
|> |> |> > > |IESG discussion can be tracked via
|> |> |> > > |http://datatracker.ietf.org/doc/draft-ietf-siprec-req/
|> |> |> > > |
|> |> |> > > |
|> |> |> > > |
|> |> |> > > |No IPR declarations have been submitted directly
|> on this I-D.
|> |> |> > > |_______________________________________________
|> |> |> > > |siprec mailing list
|> |> |> > > |siprec@ietf.org
|> |> |> > > |https://www.ietf.org/mailman/listinfo/siprec
|> |> |> > > _______________________________________________
|> |> |> > > siprec mailing list
|> |> |> > > siprec@ietf.org
|> |> |> > > https://www.ietf.org/mailman/listinfo/siprec
|> |> |> > >
|> |> |> > _______________________________________________
|> |> |> > siprec mailing list
|> |> |> > siprec@ietf.org
|> |> |> > https://www.ietf.org/mailman/listinfo/siprec
|> |> |> >
|> |> |> _______________________________________________
|> |> |> siprec mailing list
|> |> |> siprec@ietf.org
|> |> |> https://www.ietf.org/mailman/listinfo/siprec
|> |>
|> _______________________________________________
|> siprec mailing list
|> siprec@ietf.org
|> https://www.ietf.org/mailman/listinfo/siprec
|>

From dhc2@dcrocker.net  Thu Apr 21 10:38:56 2011
Return-Path: <dhc2@dcrocker.net>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 010A8E07C6 for <ietf@ietfc.amsl.com>; Thu, 21 Apr 2011 10:38:56 -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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p+Ot3Swhw0tY for <ietf@ietfc.amsl.com>; Thu, 21 Apr 2011 10:38:55 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfc.amsl.com (Postfix) with ESMTP id 21B3EE079F for <ietf@ietf.org>; Thu, 21 Apr 2011 10:38:55 -0700 (PDT)
Received: from [192.168.1.4] (adsl-67-127-56-68.dsl.pltn13.pacbell.net [67.127.56.68]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p3LHclfL021916 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Thu, 21 Apr 2011 10:38:52 -0700
Message-ID: <4DB06BA1.7020003@dcrocker.net>
Date: Thu, 21 Apr 2011 10:38:41 -0700
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: IAOC: delegating ex-officio responsibility
References: <2BE582FA-2682-4232-9D83-23A03F01A0DB@NLnetLabs.nl>	<6.2.5.6.2.20110330073936.0e1899d0@resistor.net>	<E2E41FDE-3818-4513-9933-CB1E0326B43E@nlnetlabs.nl>	<6.2.5.6.2.20110330113947.0c948bc0@resistor.net>	<4D942843.4060804@gmail.com>	<6.2.5.6.2.20110331120351.09488990@resistor.net>	<4D955661.8050502@gmail.com>	<9C81C0F6-3ABE-4479-8C5E-C20C486D052A@gmail.com>	<82A347CC-BB19-4A73-8E8A-924FBAA92A5F@NLnetLabs.nl>	<84D6568B-18C9-47B2-A457-C51C2FB3351F@gmail.com>	<5419FA805EF52E79D7822966@PST.JCK.COM>	<DAC0FFD9-9B3B-4726-B56B-5E9BE5A5F1D1@gmail.com>	<4DA8685F.5050504@dcrocker.net>	<D0674791-3D7C-4B90-8189-A895715B977A@gmail.com>	<6.2.5.6.2.20110419080338.0301b940@resistor.net>	<90F3E256-88F5-4DCF-A64B-EF7FDDE667C8@gmail.com>	<6.2.5.6.2.20110419161215.03d496a0@resistor.net> <4DAF4E76.1000806@gmail.com>
In-Reply-To: <4DAF4E76.1000806@gmail.com>
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]); Thu, 21 Apr 2011 10:38:52 -0700 (PDT)
Cc: IETF Discussion <ietf@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: Thu, 21 Apr 2011 17:38:56 -0000

On 4/20/2011 2:21 PM, Brian E Carpenter wrote:
> In the case of the IETF Chair I believe the issue is that it's
> highly desirable, from a governance viewpoint, that the IETF Chair
> has *personal* responsibility in IAOC decisions,


Why?

What happens if the person in that role is not specifically "accountable"?

And by the way, what does it mean to be accountable in the way that you consider 
so important?

What actions flow from that accountability?

d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From joelja@bogus.com  Thu Apr 21 10:50:06 2011
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id C72FEE073A for <ietf@ietfc.amsl.com>; Thu, 21 Apr 2011 10:50:06 -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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JpnyvjcEgE5o for <ietf@ietfc.amsl.com>; Thu, 21 Apr 2011 10:50:06 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfc.amsl.com (Postfix) with ESMTP id 07295E06EA for <ietf@ietf.org>; Thu, 21 Apr 2011 10:50:05 -0700 (PDT)
Received: from 23173jjaeggli.corp.zynga.com ([12.184.108.202]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p3LHnpvI078457 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Thu, 21 Apr 2011 17:49:51 GMT (envelope-from joelja@bogus.com)
Message-ID: <4DB06E39.7050306@bogus.com>
Date: Thu, 21 Apr 2011 10:49:45 -0700
From: Joel Jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.15) Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Re: IAOC: delegating ex-officio responsibility
References: <2BE582FA-2682-4232-9D83-23A03F01A0DB@NLnetLabs.nl>	<6.2.5.6.2.20110330073936.0e1899d0@resistor.net>	<E2E41FDE-3818-4513-9933-CB1E0326B43E@nlnetlabs.nl>	<6.2.5.6.2.20110330113947.0c948bc0@resistor.net>	<4D942843.4060804@gmail.com>	<6.2.5.6.2.20110331120351.09488990@resistor.net>	<4D955661.8050502@gmail.com>	<9C81C0F6-3ABE-4479-8C5E-C20C486D052A@gmail.com>	<82A347CC-BB19-4A73-8E8A-924FBAA92A5F@NLnetLabs.nl>	<84D6568B-18C9-47B2-A457-C51C2FB3351F@gmail.com>	<5419FA805EF52E79D7822966@PST.JCK.COM>	<DAC0FFD9-9B3B-4726-B56B-5E9BE5A5F1D1@gmail.com>	<4DA8685F.5050504@dcrocker.net>	<D0674791-3D7C-4B90-8189-A895715B977A@gmail.com>	<6.2.5.6.2.20110419080338.0301b940@resistor.net>	<90F3E256-88F5-4DCF-A64B-EF7FDDE667C8@gmail.com>	<6.2.5.6.2.20110419161215.03d496a0@resistor.net>	<4DAF4E76.1000806@gmail.com> <4DB06BA1.7020003@dcrocker.net>
In-Reply-To: <4DB06BA1.7020003@dcrocker.net>
X-Enigmail-Version: 1.1.1
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.2 (nagasaki.bogus.com [147.28.0.81]); Thu, 21 Apr 2011 17:49:51 +0000 (UTC)
Cc: Dave CROCKER <dhc2@dcrocker.net>, 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: Thu, 21 Apr 2011 17:50:06 -0000

On 4/21/11 10:38 AM, Dave CROCKER wrote:
> 
> 
> On 4/20/2011 2:21 PM, Brian E Carpenter wrote:
>> In the case of the IETF Chair I believe the issue is that it's
>> highly desirable, from a governance viewpoint, that the IETF Chair
>> has *personal* responsibility in IAOC decisions,
> 
> 
> Why?
> 
> What happens if the person in that role is not specifically "accountable"?

We have the potential for disconnect between the business of the ietf
and the business of running the ietf. We had that before so it's not a
hypothetical scenario.

> And by the way, what does it mean to be accountable in the way that you
> consider so important?

It means that the ability to perform the iaoc function is a
consideration for filling and retaining the role of ietf chair.

> What actions flow from that accountability?
> 
> d/
> 


From brian.e.carpenter@gmail.com  Thu Apr 21 13:52:49 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 1638AE07E0 for <ietf@ietfc.amsl.com>; Thu, 21 Apr 2011 13:52:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.099
X-Spam-Level: 
X-Spam-Status: No, score=-103.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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q-xz6+uOIIdw for <ietf@ietfc.amsl.com>; Thu, 21 Apr 2011 13:52:48 -0700 (PDT)
Received: from mail-px0-f182.google.com (mail-px0-f182.google.com [209.85.212.182]) by ietfc.amsl.com (Postfix) with ESMTP id 55868E074E for <ietf@ietf.org>; Thu, 21 Apr 2011 13:52:48 -0700 (PDT)
Received: by pxi20 with SMTP id 20so72601pxi.27 for <ietf@ietf.org>; Thu, 21 Apr 2011 13:52:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=hykXQJ9XUCLass2H0mNgA3hdjU7k4kBOElj4TmyjTv4=; b=FCeRCDxi8PkN9jHDWWr1u4xRAm/2rUVnfDXqvc7NYYT+zyndIz9qtXVrdLzEtq4dTq BZZWXFIuP/DKGvkMp+PO5KtSy7hr4Hzqj7E50i8sCqIDC1bP/D9nouV+kefTTAZr/DrO i4vX5BkGTyNj0Mwqw0EsBbyH43el2Qv0wF2XY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=RNIbgfbOcWSvQjnyNaY0bNAVf06cDJLHF7jPWrlNGYaarZwEq+JK5nuRNf5r/qAbDf hF2uLCudFVarM0sNaEbJho6QnPBe/dRBkFcojx4kWeXndCGu5iVIMcBEP/MX/GBejL// /UGoH8OQ3uKJB2AqJeDh6WUxnJQaIYUDEq40k=
Received: by 10.68.27.229 with SMTP id w5mr529973pbg.96.1303419167797; Thu, 21 Apr 2011 13:52:47 -0700 (PDT)
Received: from [10.1.1.4] ([121.98.190.33]) by mx.google.com with ESMTPS id a1sm1519155pbo.91.2011.04.21.13.52.44 (version=SSLv3 cipher=OTHER); Thu, 21 Apr 2011 13:52:46 -0700 (PDT)
Message-ID: <4DB0991D.2000607@gmail.com>
Date: Fri, 22 Apr 2011 08:52:45 +1200
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: Joel Jaeggli <joelja@bogus.com>
Subject: Re: IAOC: delegating ex-officio responsibility
References: <2BE582FA-2682-4232-9D83-23A03F01A0DB@NLnetLabs.nl>	<6.2.5.6.2.20110330073936.0e1899d0@resistor.net>	<E2E41FDE-3818-4513-9933-CB1E0326B43E@nlnetlabs.nl>	<6.2.5.6.2.20110330113947.0c948bc0@resistor.net>	<4D942843.4060804@gmail.com>	<6.2.5.6.2.20110331120351.09488990@resistor.net>	<4D955661.8050502@gmail.com>	<9C81C0F6-3ABE-4479-8C5E-C20C486D052A@gmail.com>	<82A347CC-BB19-4A73-8E8A-924FBAA92A5F@NLnetLabs.nl>	<84D6568B-18C9-47B2-A457-C51C2FB3351F@gmail.com>	<5419FA805EF52E79D7822966@PST.JCK.COM>	<DAC0FFD9-9B3B-4726-B56B-5E9BE5A5F1D1@gmail.com>	<4DA8685F.5050504@dcrocker.net>	<D0674791-3D7C-4B90-8189-A895715B977A@gmail.com>	<6.2.5.6.2.20110419080338.0301b940@resistor.net>	<90F3E256-88F5-4DCF-A64B-EF7FDDE667C8@gmail.com>	<6.2.5.6.2.20110419161215.03d496a0@resistor.net>	<4DAF4E76.1000806@gmail.com> <4DB06BA1.7020003@dcrocker.net> <4DB06E39.7050306@bogus.com>
In-Reply-To: <4DB06E39.7050306@bogus.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Dave CROCKER <dhc2@dcrocker.net>, dcrocker@bbiw.net, 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: Thu, 21 Apr 2011 20:52:49 -0000

On 2011-04-22 05:49, Joel Jaeggli wrote:
> On 4/21/11 10:38 AM, Dave CROCKER wrote:
>>
>> On 4/20/2011 2:21 PM, Brian E Carpenter wrote:
>>> In the case of the IETF Chair I believe the issue is that it's
>>> highly desirable, from a governance viewpoint, that the IETF Chair
>>> has *personal* responsibility in IAOC decisions,
>>
>> Why?
>>
>> What happens if the person in that role is not specifically "accountable"?
> 
> We have the potential for disconnect between the business of the ietf
> and the business of running the ietf. We had that before so it's not a
> hypothetical scenario.

Exactly. My personal experience as IETF Chair was that the administrative
work, which we engineers have a lordly tendency to dismiss as trivial,
is truly vital to making the IETF work properly. I just can't conceive
of an IETF Chair decoupling from the chain of responsibility for this.

Just to repeat myself: the IAOC workload represents a substantial
*reduction* of the IETF Chair workload (and stress load) compared to the
pre-IAOC situation.

> 
>> And by the way, what does it mean to be accountable in the way that you
>> consider so important?
> 
> It means that the ability to perform the iaoc function is a
> consideration for filling and retaining the role of ietf chair.

Exactly. An IETF Chair who doesn't see this as fundamental would be
a bad choice.

> 
>> What actions flow from that accountability?

Failure in this part of the role would be a strong signal
to NomCom if the Chair wants to re-up, and dramatic failure
would be potential grounds for recall.

   Brian

From brian.e.carpenter@gmail.com  Thu Apr 21 13:56:14 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 2B6B7E0722 for <ietf@ietfc.amsl.com>; Thu, 21 Apr 2011 13:56:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.199
X-Spam-Level: 
X-Spam-Status: No, score=-103.199 tagged_above=-999 required=5 tests=[AWL=0.400, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AdgaIQzjnGM9 for <ietf@ietfc.amsl.com>; Thu, 21 Apr 2011 13:56:13 -0700 (PDT)
Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by ietfc.amsl.com (Postfix) with ESMTP id 89286E06B9 for <ietf@ietf.org>; Thu, 21 Apr 2011 13:56:13 -0700 (PDT)
Received: by pwi5 with SMTP id 5so78892pwi.31 for <ietf@ietf.org>; Thu, 21 Apr 2011 13:56:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=MDC2Gxq9JQAlHVd/02Ugt94MHjyrbrzoPwlds5KPF9I=; b=KMfzgpYB63wIV+7dxjzMfXScppaWSpXwDvP13dLXfNJq3CFyJmvCyWFOAolTPqezzz ei4yxFhrXj2Aw0Jc6l/C18S6ZtohhGp/1zaFQXNQ764herYS440698D54Xb0LoOG9djX 5vbSdP4e3vrMff2GmYVcabgyX6jtIwgTo9Hew=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=qaUlnfRGdHLDF9nKmOTLyj5/FPlX3Qxd0noO8fL/yKKcGU0Xy7KQ48aOv/HEODD7iS qYGZ+r3PrbufKjdF5qv9EjUGzyC/Bqs57AuN8sFGliHSZWs/lSR2Hr1pgf/2I8o8sB7V YYyxa5r6KUQrOjX0GrFCgcnt1j4ltSCmPzERo=
Received: by 10.68.52.38 with SMTP id q6mr557761pbo.179.1303419372879; Thu, 21 Apr 2011 13:56:12 -0700 (PDT)
Received: from [10.1.1.4] ([121.98.190.33]) by mx.google.com with ESMTPS id k2sm1523581pbj.47.2011.04.21.13.56.09 (version=SSLv3 cipher=OTHER); Thu, 21 Apr 2011 13:56:11 -0700 (PDT)
Message-ID: <4DB099EC.60206@gmail.com>
Date: Fri, 22 Apr 2011 08:56:12 +1200
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: Glen Zorn <gwz@net-zen.net>
Subject: Re: Revising I-Ds became painful
References: <3035.52653.qm@web111412.mail.gq1.yahoo.com> <4DAFBE22.9070700@net-zen.net>
In-Reply-To: <4DAFBE22.9070700@net-zen.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Behcet Sarikaya <behcetsarikaya@yahoo.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, 21 Apr 2011 20:56:14 -0000

On 2011-04-21 17:18, Glen Zorn wrote:
> On 4/21/2011 12:18 AM, Behcet Sarikaya wrote:
> 
>> Hi,
>>   It seems like I-D submission for a revised draft (after expiration) encounters 
>> so many new hurdles:
>>
>> 1. Version number. Submission page complains about the version number even 
>> though it is correct. This seems to be because the system keeps the expiration 
>> message in html format as the new version to be submitted. 
>>
>> Is there a way to get around this?
> 
> Don't let I-Ds expire?

I don't understand Behcet's problem statement. But if it's a bug,
please send a very detailed explanation to ietf-action@ietf.org, not to
the thousands of people on this list.

   Brian

From john-ietf@jck.com  Thu Apr 21 14:00:23 2011
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 38C52E06B9 for <ietf@ietfc.amsl.com>; Thu, 21 Apr 2011 14:00:23 -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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tV+5ot6xwaBK for <ietf@ietfc.amsl.com>; Thu, 21 Apr 2011 14:00:22 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfc.amsl.com (Postfix) with ESMTP id 1D591E0702 for <ietf@ietf.org>; Thu, 21 Apr 2011 14:00:22 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QD0yt-000HdG-Q1; Thu, 21 Apr 2011 17:00:08 -0400
Date: Thu, 21 Apr 2011 17:00:06 -0400
From: John C Klensin <john-ietf@jck.com>
To: Joel Jaeggli <joelja@bogus.com>, dcrocker@bbiw.net
Subject: Re: IAOC: delegating ex-officio responsibility
Message-ID: <FECA99F6A22079ADA746608B@PST.JCK.COM>
In-Reply-To: <4DB06E39.7050306@bogus.com>
References: <2BE582FA-2682-4232-9D83-23A03F01A0DB@NLnetLabs.nl> <6.2.5.6.2.20110330073936.0e1899d0@resistor.net> <E2E41FDE-3818-4513-9933-CB1E0326B43E@nlnetlabs.nl> <6.2.5.6.2.20110330113947.0c948bc0@resistor.net> <4D942843.4060804@gmail.com> <6.2.5.6.2.20110331120351.09488990@resistor.net> <4D955661.8050502@gmail.com> <9C81C0F6-3ABE-4479-8C5E-C20C486D052A@gmail.com> <82A347CC-BB19-4A73-8E8A-924FBAA92A5F@NLnetLabs.nl> <84D6568B-18C9-47B2-A457-C51C2FB3351F@gmail.com> <5419FA805EF52E79D7822966@PST.JCK.COM> <DAC0FFD9-9B3B-4726-B56B-5E9BE5A5F1D1@gmail.com> <4DA8685F.5050504@dcrocker.net> <D0674791-3D7C-4B90-8189-A895715B977A@gmail.com> <6.2.5.6.2.20110419080338.0301b940@resistor.net> <90F3E256-88F5-4DCF-A64B-EF7FDDE667C8@gmail.com> <6.2.5.6.2.20110419161215.03d496a0@resistor.net> <4DAF4E76.1000806@gmail.com>	<4DB06BA1.7020003@dcrocker.net> <4DB06E39.7050306@bogus.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: Dave CROCKER <dhc2@dcrocker.net>, 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: Thu, 21 Apr 2011 21:00:23 -0000

--On Thursday, April 21, 2011 10:49 -0700 Joel Jaeggli
<joelja@bogus.com> wrote:

> On 4/21/11 10:38 AM, Dave CROCKER wrote:
>> 
>> 
>> On 4/20/2011 2:21 PM, Brian E Carpenter wrote:
>>> In the case of the IETF Chair I believe the issue is that
>>> it's highly desirable, from a governance viewpoint, that the
>>> IETF Chair has *personal* responsibility in IAOC decisions,
>> 
>> Why?
>> 
>> What happens if the person in that role is not specifically
>> "accountable"?
> 
> We have the potential for disconnect between the business of
> the ietf and the business of running the ietf. We had that
> before so it's not a hypothetical scenario.

But, if it is the "business of running the IETF" that we are
after, why is it better to try to blame/ hold accountable one
individual than to hold the IESG accountable and let them manage
the question of who goes to IAOC meetings as they (with the
Chair's active participation in the IESG discussions) think fit?
There is nothing in any of our document that either crowns the
IETF Chair King or endows him or her with divine guidance or
wisdom.
 
>> And by the way, what does it mean to be accountable in the
>> way that you consider so important?
> 
> It means that the ability to perform the iaoc function is a
> consideration for filling and retaining the role of ietf chair.

And that takes us back around the loop of requiring that the
criteria for selection of the IETF Chair include a combination
of skills and interests that we are unlikely to find, ability to
devote unlimited time and attention to the job (and I mean
"unlimited" as in ability to create and utilize 32 hour days),
and resources to match.  It also suggests that Nomcoms are able
to understand all of those skills and optimize for all of them
at once, choosing from the relatively small number of people who
meet the criteria.   Noting that Russ has done, IMO, a
superhuman job of balancing the various tasks and demands that
we've placed on him but is still feeling overloaded, you will
forgive me if my reaction to imposing those requirements as
minimum conditions on future candidates is a little skeptical.

      john


From dharkins@lounge.org  Thu Apr 21 17:39:11 2011
Return-Path: <dharkins@lounge.org>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id E1C24E0675; Thu, 21 Apr 2011 17:39:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.265
X-Spam-Level: 
X-Spam-Status: No, score=-6.265 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id anybBKxyCcln; Thu, 21 Apr 2011 17:39:11 -0700 (PDT)
Received: from colo.trepanning.net (colo.trepanning.net [69.55.226.174]) by ietfc.amsl.com (Postfix) with ESMTP id 42A52E065C; Thu, 21 Apr 2011 17:39:11 -0700 (PDT)
Received: from www.trepanning.net (localhost [127.0.0.1]) by colo.trepanning.net (Postfix) with ESMTP id AEF281022404C; Thu, 21 Apr 2011 17:39:10 -0700 (PDT)
Received: from 69.12.173.8 (SquirrelMail authenticated user dharkins@lounge.org) by www.trepanning.net with HTTP; Thu, 21 Apr 2011 17:39:10 -0700 (PDT)
Message-ID: <9a944e460983182912fe0d2e85ef32f9.squirrel@www.trepanning.net>
In-Reply-To: <4da2f037.cf03d90a.5d44.fffff941@mx.google.com>
References: <4da2f037.cf03d90a.5d44.fffff941@mx.google.com>
Date: Thu, 21 Apr 2011 17:39:10 -0700 (PDT)
Subject: Re: Gen-ART LC review of draft-harkins-ipsecme-spsk-auth-03
From: "Dan Harkins" <dharkins@lounge.org>
To: "Roni Even" <ron.even.tlv@gmail.com>
User-Agent: SquirrelMail/1.4.14 [SVN]
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Cc: gen-art@ietf.org, 'IETF-Discussion list' <ietf@ietf.org>, draft-harkins-ipsecme-spsk-auth.all@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, 22 Apr 2011 00:39:12 -0000

  Hi Roni,

  Thank you for reviewing my draft. Comments inline....

On Mon, April 11, 2011 5:11 am, Roni Even 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.
>
> Minor issues:
>
> 1.	In section 8.5 and 8.6 the draft says that "If no more password
> pre-processing techniques are supported the exchange MUST be
> terminated."
> Reading section 6, I thought that NONE MUST be supported for
> interoperability purpose.

  One of the valid techniques for password pre-processing is "none".
That doesn't mean that there isn't a technique, it means the technique
is to perform no pre-processing on the password (treat it as a raw
blob of bits).

> 2.	In section 8.1 and in figure 1 and figure 2 is there a maximum value
> for "counter"?

  No there isn't, but it is doubtful the number will get very large.
The probability that more than n iterations is necessary will be
roughly (1-(r/2p))^n, where r is the order and p is the prime, and
that number rapidly approaches zero as n increases.

> Nits/editorial comments:
>
> 1.       In section 1 just before 1.1 you have "suceed" instead of
> "succeed"
>
> 2.       In section 4 third bullet "an" instead of "and"
>
> 3.       In section 4.2 "Two elementx" instead of "Two elements"
>
> 4.       In section 5 second row "authenticaiton" should be
> "authentication"
>
> 5.       In section 6 fourth row "identitcal" instead of "identical"

  Thank you for catching all of these.

  regards,

  Dan.



From dharkins@lounge.org  Thu Apr 21 17:54:52 2011
Return-Path: <dharkins@lounge.org>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id A7AF8E06F2 for <ietf@ietfc.amsl.com>; Thu, 21 Apr 2011 17:54:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.265
X-Spam-Level: 
X-Spam-Status: No, score=-6.265 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R5Dg+qt7SioU for <ietf@ietfc.amsl.com>; Thu, 21 Apr 2011 17:54:52 -0700 (PDT)
Received: from colo.trepanning.net (colo.trepanning.net [69.55.226.174]) by ietfc.amsl.com (Postfix) with ESMTP id E5CB8E065C for <ietf@ietf.org>; Thu, 21 Apr 2011 17:54:51 -0700 (PDT)
Received: from www.trepanning.net (localhost [127.0.0.1]) by colo.trepanning.net (Postfix) with ESMTP id 63FA71022404C; Thu, 21 Apr 2011 17:54:51 -0700 (PDT)
Received: from 69.12.173.8 (SquirrelMail authenticated user dharkins@lounge.org) by www.trepanning.net with HTTP; Thu, 21 Apr 2011 17:54:51 -0700 (PDT)
Message-ID: <422a53796c3f69bea881677f9ee7bc10.squirrel@www.trepanning.net>
In-Reply-To: <4D8EC5C1.1060909@gmail.com>
References: <20110326163349.10560.66105.idtracker@localhost> <4D8EC5C1.1060909@gmail.com>
Date: Thu, 21 Apr 2011 17:54:51 -0700 (PDT)
Subject: Re: Last Call: <draft-harkins-ipsecme-spsk-auth-03.txt> (Secure  PSK Authentication for IKE) to Informational RFC
From: "Dan Harkins" <dharkins@lounge.org>
To: "Mykyta Yevstifeyev" <evnikita2@gmail.com>
User-Agent: SquirrelMail/1.4.14 [SVN]
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Cc: ietf@ietf.org, draft-harkins-ipsecme-spsk-auth@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, 22 Apr 2011 00:54:52 -0000

  Hi Mykyta,

  Thank you for reviewing my draft. Responses inline....

On Sat, March 26, 2011 10:06 pm, Mykyta Yevstifeyev wrote:
> Hello,
>
> A question on the flowing extract:
>
>> This memo contains a new numberspace to be managed by IANA, a
>>     registry used to indicate a password preprocessing technique.  The
>>     initial layout of this registry SHALL be:
>>
>>     o   0x00 : None
>>
>>     o   0x01 :RFC2759  <http://tools.ietf.org/html/rfc2759>
>>
>>     o   0x02 : SASLprep
>>
>>     The Prep field is 8 bits long and all other values are available
>>     through assignment by IANA.  IANA is instructed to assign values
>>     based on "Specification Required" (see [RFC5226
>> <http://tools.ietf.org/html/rfc5226>]).
> It contains the description of new registry. but it fails to give it the
> distinctive definition.  Among other, what is the exact name of the
> registry?  How are the fields named?  The sentence "The Prep field is 8
> bits long and all other values are available through assignment by
> IANA." also makes me confusing.  This means that the Prep field is not
> assigned by IANA?  Finally, 0x00 is Unassigned or Reserved?
>
> Thus, this extract needs more clarification.

  How would the following look to you:

  "This memo contains a new numberspace to be managed by IANA, the
   password preprocessing method (Prep) registry. The initial layout
   of this registry SHALL be:

   o   0x00 : None (no preprocessing is performed)

   o   0x01 : RFC2759

   o   0x02 : SASLprep

   The Prep field is 8 bits long and all other values are available
   through assignment by IANA.  IANA is instructed to assign values
   based on "Specification Required" (see [RFC5226])."

  regards,

  Dan.




From gwz@net-zen.net  Thu Apr 21 18:35:37 2011
Return-Path: <gwz@net-zen.net>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id D1403E0773 for <ietf@ietfc.amsl.com>; Thu, 21 Apr 2011 18:35: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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ohCMpVj8oevf for <ietf@ietfc.amsl.com>; Thu, 21 Apr 2011 18:35:34 -0700 (PDT)
Received: from smtpauth21.prod.mesa1.secureserver.net (smtpauth21.prod.mesa1.secureserver.net [64.202.165.38]) by ietfc.amsl.com (Postfix) with SMTP id 8D42CE0756 for <ietf@ietf.org>; Thu, 21 Apr 2011 18:35:34 -0700 (PDT)
Received: (qmail 23221 invoked from network); 22 Apr 2011 01:35:33 -0000
Received: from unknown (124.120.98.54) by smtpauth21.prod.mesa1.secureserver.net (64.202.165.38) with ESMTP; 22 Apr 2011 01:35:32 -0000
Message-ID: <4DB0DB5F.8020806@net-zen.net>
Date: Fri, 22 Apr 2011 08:35:27 +0700
From: Glen Zorn <gwz@net-zen.net>
Organization: Network Zen
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: scott.probasco@nokia.com
Subject: Re: [paws] WG Review: Protocol to Access White Space database (paws)
References: <20110419165634.CD24CE07CF@ietfc.amsl.com>	<4DADFE6D.3050107@cs.tcd.ie>	<88BE24FD9280884487DEAE0CE1FD3A5B060F1B@008-AM1MPN1-023.mgdnok.nokia.com>	<F4035489-7D81-47C9-BE99-3D9DCF1637FA@cdt.org> <88BE24FD9280884487DEAE0CE1FD3A5B06182F@008-AM1MPN1-023.mgdnok.nokia.com>
In-Reply-To: <88BE24FD9280884487DEAE0CE1FD3A5B06182F@008-AM1MPN1-023.mgdnok.nokia.com>
X-Enigmail-Version: 1.1.1
Content-Type: multipart/mixed; boundary="------------050405030501010207010101"
Cc: paws@ietf.org, 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: Fri, 22 Apr 2011 01:35:38 -0000

This is a multi-part message in MIME format.
--------------050405030501010207010101
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

On 4/21/2011 8:05 PM, scott.probasco@nokia.com wrote:

> Hi,
> 
> I agree with the concept, just want to be sure the PAWS is not expected to develop these security mechanisms (i.e. the tools) as contrasted to including or using in PAWS the security tools developed by appropriate expert groups.
> 

I agree.

> "Inclusion of robust security mechanisms is required:..."
> ??
> 
> Regards,
> Scott
> 
> 
> 
> -----Original Message-----
> From: ext Alissa Cooper [mailto:acooper@cdt.org] 
> Sent: Thursday, April 21, 2011 6:01 AM
> To: Probasco Scott (Nokia-CIC/Dallas)
> Cc: stephen.farrell@cs.tcd.ie; ietf@ietf.org; paws@ietf.org; iesg@ietf.org
> Subject: Re: [paws] WG Review: Protocol to Access White Space database (paws)
> 
> On Apr 20, 2011, at 3:41 PM, <scott.probasco@nokia.com> <scott.probasco@nokia.com> wrote:
> 
>> Hi Stephen, All,
>>
>> I believe the current wording
>>>> Robust security mechanisms are required to prevent:
>>>> device identity spoofing, modification of device requests, modification
>>>> of channel enablement information, ...
>> is acceptable because "mechanisms are required" means they should be in the protocol, it does not mean they cannot be optional. PAWS should support Regulator requirements globally, and thus I believe there will be procedures or capabilities which are "required" to be in the protocol but will be "optional" during run time. Thus different or conflicting requirements from different regions of the world can be supported. (Several regulatory groups around the world are still developing their views and requirements).
>>
> 
> Agreed on this point, although I think the charter could make it a little less ambiguous by saying "Development of robust security mechanisms is required . . .," that way it's not indicating that the actual mechanisms themselves will always be required.
> 
> Given that device identity will have to be shared in some circumstances, I would also add its protection to the end of the list of mechanisms: 
> 
> Development of security mechanisms is required to prevent:
> device identity spoofing, modification of device requests, modification
> of channel enablement information, impersonation of registered database
> services and unauthorized disclosure of a user's location and/or device identity.
> 
> Alissa
> 
>> It's not the time to dig deep into proposed solutions, just my opinion is the current proposed wording is an acceptable definition to allow a Work Group to get started defining the details.
>>
>> Regards,
>> Scott
>>
>> -----Original Message-----
>> From: paws-bounces@ietf.org [mailto:paws-bounces@ietf.org] On Behalf Of ext Stephen Farrell
>> Sent: Tuesday, April 19, 2011 4:28 PM
>> To: IETF-Discussion
>> Cc: paws@ietf.org; iesg@ietf.org
>> Subject: Re: [paws] WG Review: Protocol to Access White Space database (paws)
>>
>>
>> I think this is a good and timely thing for the IETF to do.
>>
>> One part of this where I think it might be useful to get
>> some broader input (which may have happened already, I'm not
>> sure) is the following:
>>
>> On 19/04/11 17:56, IESG Secretary wrote:
>>> The protocol must protect both the channel enablement process and the
>>> privacy of users. 
>>
>> That part is fine but it goes on to say:
>>
>>> Robust security mechanisms are required to prevent:
>>> device identity spoofing, modification of device requests, modification
>>> of channel enablement information, ...
>>
>> I'm told (and believe) this in response to (at least) US
>> FCC requirements that call for a device ID and sometimes
>> serial number to be (securely, for some value of securely)
>> sent with the query.
>>
>> Those appear to be real regulatory requirements in the
>> US, presumably so the regulator can stomp on someone who
>> messes about in the wrong spectrum at the wrong time.
>> (The link below [1] may be to the right or wrong bit of
>> those US regulations, I'm not at all sure, not being
>> from there;-)
>>
>> So my questions:
>>
>> Are there may be similar (or conflicting!) requirements
>> elsewhere?
>>
>> Does this bit of the charter text need changes to work
>> well for other regions?
>>
>> Separately, I'm not sure how to square those kinds of
>> regulatory requirements with protecting privacy where the
>> device is carried by a person and has some FCC device ID
>> (which lots do I guess) and the person might not want
>> the database operator to know who's asking. But I think
>> that's ok as something for the WG to figure out since
>> the charter already calls for respecting privacy.
>>
>> I'm more concerned in case e.g. some other regional regulation
>> called for this protocol to be completely anonymous or
>> something, in which case the current charter text might
>> be problematic.
>>
>> Cheers,
>> Stephen.
>>
>> [1]
>> http://ecfr.gpoaccess.gov/cgi/t/text/text-idx?c=ecfr&sid=3e9c322addf1f7e897d8c84a6c7aca78&rgn=div8&view=text&node=47:1.0.1.1.14.8.243.9&idno=47
>> _______________________________________________
>> paws mailing list
>> paws@ietf.org
>> https://www.ietf.org/mailman/listinfo/paws
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>>
> 
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> 
> 

--------------050405030501010207010101
Content-Type: text/x-vcard; charset=utf-8;
 name="gwz.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="gwz.vcf"

begin:vcard
fn:Glen Zorn
n:Zorn;Glen
org:Network Zen
adr:;;;Seattle;WA;;USA
email;internet:gwz@net-zen.net
tel;cell:+66 87 040 4617
note:PGP Key Fingerprint: DAD3 F5D3 ACE6 4195 9C5C  2EE1 6E17 B5F6 5953 B45F 
version:2.1
end:vcard


--------------050405030501010207010101--

From narten@us.ibm.com  Thu Apr 21 21:53:17 2011
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id AB267E06D7 for <ietf@ietfc.amsl.com>; Thu, 21 Apr 2011 21:53:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.166
X-Spam-Level: 
X-Spam-Status: No, score=-106.166 tagged_above=-999 required=5 tests=[AWL=0.433, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jrf3bxIffYJJ for <ietf@ietfc.amsl.com>; Thu, 21 Apr 2011 21:53:16 -0700 (PDT)
Received: from e39.co.us.ibm.com (e39.co.us.ibm.com [32.97.110.160]) by ietfc.amsl.com (Postfix) with ESMTP id 256EFE064E for <ietf@ietf.org>; Thu, 21 Apr 2011 21:53:16 -0700 (PDT)
Received: from d03relay02.boulder.ibm.com (d03relay02.boulder.ibm.com [9.17.195.227]) by e39.co.us.ibm.com (8.14.4/8.13.1) with ESMTP id p3M4db87027473 for <ietf@ietf.org>; Thu, 21 Apr 2011 22:39:37 -0600
Received: from d03av05.boulder.ibm.com (d03av05.boulder.ibm.com [9.17.195.85]) by d03relay02.boulder.ibm.com (8.13.8/8.13.8/NCO v9.1) with ESMTP id p3M4r4wp103150 for <ietf@ietf.org>; Thu, 21 Apr 2011 22:53:04 -0600
Received: from d03av05.boulder.ibm.com (loopback [127.0.0.1]) by d03av05.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id p3M4r4IF016324 for <ietf@ietf.org>; Thu, 21 Apr 2011 22:53:04 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.151.17]) by d03av05.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id p3M4r3Ab016316 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 21 Apr 2011 22:53:04 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id p3M4r3Oe012796 for <ietf@ietf.org>; Fri, 22 Apr 2011 00:53:03 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.4/8.14.4/Submit) id p3M4r2XP012784 for ietf@ietf.org; Fri, 22 Apr 2011 00:53:02 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201104220453.p3M4r2XP012784@rotala.raleigh.ibm.com>
Date: Fri, 22 Apr 2011 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-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 04:53:17 -0000

Total of 78 messages in the last 7 days.
 
script run at: Fri Apr 22 00:53:02 EDT 2011
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  8.97% |    7 |  7.32% |    53224 | dhc2@dcrocker.net
  5.13% |    4 |  5.33% |    38714 | jmh@joelhalpern.com
  5.13% |    4 |  4.22% |    30657 | bob.hinden@gmail.com
  5.13% |    4 |  2.86% |    20806 | housley@vigilsec.com
  2.56% |    2 |  5.30% |    38526 | bernard_aboba@hotmail.com
  2.56% |    2 |  4.96% |    36065 | mperumal@cisco.com
  3.85% |    3 |  3.49% |    25402 | brian.e.carpenter@gmail.com
  2.56% |    2 |  4.71% |    34220 | partr@cisco.com
  2.56% |    2 |  4.60% |    33469 | eckelcu@cisco.com
  2.56% |    2 |  4.55% |    33090 | john.elwell@siemens-enterprise.com
  3.85% |    3 |  3.00% |    21783 | sm@resistor.net
  2.56% |    2 |  3.83% |    27868 | stpeter@stpeter.im
  2.56% |    2 |  2.49% |    18096 | scott.probasco@nokia.com
  2.56% |    2 |  2.34% |    17044 | llynch@civil-tongue.net
  2.56% |    2 |  2.20% |    16020 | gwz@net-zen.net
  2.56% |    2 |  2.07% |    15072 | slawomir.testowy@gmail.com
  2.56% |    2 |  1.66% |    12065 | evnikita2@gmail.com
  2.56% |    2 |  1.65% |    11974 | john-ietf@jck.com
  2.56% |    2 |  1.52% |    11026 | dharkins@lounge.org
  2.56% |    2 |  1.39% |    10108 | joelja@bogus.com
  1.28% |    1 |  2.67% |    19384 | kent@bbn.com
  1.28% |    1 |  2.36% |    17189 | leon.portman@nice.com
  2.56% |    2 |  0.90% |     6537 | iad@ietf.org
  1.28% |    1 |  2.03% |    14758 | lars.eggert@nokia.com
  1.28% |    1 |  2.01% |    14645 | daedulus@btconnect.com
  1.28% |    1 |  1.69% |    12285 | rmohanr@cisco.com
  1.28% |    1 |  1.62% |    11778 | budden@nps.navy.mil
  1.28% |    1 |  1.50% |    10918 | paul@marvell.com
  1.28% |    1 |  1.48% |    10784 | fluffy@cisco.com
  1.28% |    1 |  1.30% |     9456 | vesely@tana.it
  1.28% |    1 |  1.15% |     8339 | john@jck.com
  1.28% |    1 |  1.14% |     8324 | tom111.taylor@bell.net
  1.28% |    1 |  1.10% |     8017 | acooper@cdt.org
  1.28% |    1 |  1.09% |     7939 | olaf@nlnetlabs.nl
  1.28% |    1 |  1.08% |     7853 | jari.arkko@piuha.net
  1.28% |    1 |  0.99% |     7163 | narten@us.ibm.com
  1.28% |    1 |  0.99% |     7163 | john@jlc.net
  1.28% |    1 |  0.93% |     6771 | tony@att.com
  1.28% |    1 |  0.89% |     6500 | stephen.farrell@cs.tcd.ie
  1.28% |    1 |  0.78% |     5638 | behcetsarikaya@yahoo.com
  1.28% |    1 |  0.77% |     5602 | henk@uijterwaal.nl
  1.28% |    1 |  0.73% |     5307 | amorris@amsl.com
  1.28% |    1 |  0.65% |     4731 | alexey.melnikov@isode.com
  1.28% |    1 |  0.64% |     4678 | ajs@shinkuro.com
--------+------+--------+----------+------------------------
100.00% |   78 |100.00% |   726988 | Total

From gwz@net-zen.net  Thu Apr 21 22:08:06 2011
Return-Path: <gwz@net-zen.net>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id A4B10E0764 for <ietf@ietfc.amsl.com>; Thu, 21 Apr 2011 22:08:06 -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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SS2lbxK4vAs6 for <ietf@ietfc.amsl.com>; Thu, 21 Apr 2011 22:08:05 -0700 (PDT)
Received: from p3plsmtpa07-10.prod.phx3.secureserver.net (p3plsmtpa07-10.prod.phx3.secureserver.net [173.201.192.239]) by ietfc.amsl.com (Postfix) with SMTP id 118A5E06D7 for <ietf@ietf.org>; Thu, 21 Apr 2011 22:08:05 -0700 (PDT)
Received: (qmail 18193 invoked from network); 22 Apr 2011 05:08:04 -0000
Received: from unknown (124.120.89.74) by p3plsmtpa07-10.prod.phx3.secureserver.net (173.201.192.239) with ESMTP; 22 Apr 2011 05:08:02 -0000
Message-ID: <4DB10D2D.6020503@net-zen.net>
Date: Fri, 22 Apr 2011 12:07:57 +0700
From: Glen Zorn <gwz@net-zen.net>
Organization: Network Zen
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Dan Harkins <dharkins@lounge.org>
Subject: Re: Last Call: <draft-harkins-ipsecme-spsk-auth-03.txt> (Secure  PSK Authentication for IKE) to Informational RFC
References: <20110326163349.10560.66105.idtracker@localhost>	<4D8EC5C1.1060909@gmail.com> <422a53796c3f69bea881677f9ee7bc10.squirrel@www.trepanning.net>
In-Reply-To: <422a53796c3f69bea881677f9ee7bc10.squirrel@www.trepanning.net>
X-Enigmail-Version: 1.1.1
Content-Type: multipart/mixed; boundary="------------000008040001070400050406"
Cc: ietf@ietf.org, draft-harkins-ipsecme-spsk-auth@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, 22 Apr 2011 05:08:06 -0000

This is a multi-part message in MIME format.
--------------000008040001070400050406
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

On 4/22/2011 7:54 AM, Dan Harkins wrote:

> 
>   Hi Mykyta,
> 
>   Thank you for reviewing my draft. Responses inline....
> 
> On Sat, March 26, 2011 10:06 pm, Mykyta Yevstifeyev wrote:
>> Hello,
>>
>> A question on the flowing extract:
>>
>>> This memo contains a new numberspace to be managed by IANA, a
>>>     registry used to indicate a password preprocessing technique.  The
>>>     initial layout of this registry SHALL be:
>>>
>>>     o   0x00 : None
>>>
>>>     o   0x01 :RFC2759  <http://tools.ietf.org/html/rfc2759>
>>>
>>>     o   0x02 : SASLprep
>>>
>>>     The Prep field is 8 bits long and all other values are available
>>>     through assignment by IANA.  IANA is instructed to assign values
>>>     based on "Specification Required" (see [RFC5226
>>> <http://tools.ietf.org/html/rfc5226>]).
>> It contains the description of new registry. but it fails to give it the
>> distinctive definition.  Among other, what is the exact name of the
>> registry?  How are the fields named?  The sentence "The Prep field is 8
>> bits long and all other values are available through assignment by
>> IANA." also makes me confusing.  This means that the Prep field is not
>> assigned by IANA?  Finally, 0x00 is Unassigned or Reserved?
>>
>> Thus, this extract needs more clarification.
> 
>   How would the following look to you:
> 
>   "This memo contains a new numberspace to be managed by IANA, the
>    password preprocessing method (Prep) registry. The initial layout
>    of this registry SHALL be:
> 
>    o   0x00 : None (no preprocessing is performed)
> 
>    o   0x01 : RFC2759
> 
>    o   0x02 : SASLprep
> 
>    The Prep field is 8 bits long and all other values are available
>    through assignment by IANA.  IANA is instructed to assign values
>    based on "Specification Required" (see [RFC5226])."

This looks strangely familiar ;-).  From RFC 5931:

 The following is the initial layout for the password pre-processing
 method registry:

   o   0x00 : None

   o   0x01 : RFC2759

   o   0x02 : SASLprep

   The Prep field is 8 bits long, and all other values are available
   through assignment by IANA.  IANA is instructed to assign values
   based on "Specification Required" (see [RFC5226]).

Is there some good reason not to use the IANA Registry already
established
(http://www.iana.org/assignments/eap-pwd-parameters/eap-pwd-parameters.xml#eap-pwd-parameters-4)?

--------------000008040001070400050406
Content-Type: text/x-vcard; charset=utf-8;
 name="gwz.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="gwz.vcf"

begin:vcard
fn:Glen Zorn
n:Zorn;Glen
org:Network Zen
adr:;;;Seattle;WA;;USA
email;internet:gwz@net-zen.net
tel;cell:+66 87 040 4617
note:PGP Key Fingerprint: DAD3 F5D3 ACE6 4195 9C5C  2EE1 6E17 B5F6 5953 B45F 
version:2.1
end:vcard


--------------000008040001070400050406--

From amorris@amsl.com  Thu Apr 21 22:53:28 2011
Return-Path: <amorris@amsl.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id F152DE06C5 for <ietf@ietfc.amsl.com>; Thu, 21 Apr 2011 22:53:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.599
X-Spam-Level: 
X-Spam-Status: No, score=-4.599 tagged_above=-999 required=5 tests=[AWL=2.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4MsSG0ix4yFx for <ietf@ietfc.amsl.com>; Thu, 21 Apr 2011 22:53:27 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [64.170.98.20]) by ietfc.amsl.com (Postfix) with ESMTP id 1DC2EE064E for <ietf@ietf.org>; Thu, 21 Apr 2011 22:53:27 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c1a.amsl.com (Postfix) with ESMTP id C99ACE08C8; Thu, 21 Apr 2011 22:53:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c1a.amsl.com ([127.0.0.1]) by localhost (c1a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2mYIJKXIBaI0; Thu, 21 Apr 2011 22:53:26 -0700 (PDT)
Received: from [192.168.0.194] (c-76-102-55-37.hsd1.ca.comcast.net [76.102.55.37]) by c1a.amsl.com (Postfix) with ESMTPSA id 8E552E08BC; Thu, 21 Apr 2011 22:53:26 -0700 (PDT)
Message-Id: <8FC142E2-3C3D-4B2E-B914-3DDB89EF2A45@amsl.com>
From: Alexa Morris <amorris@amsl.com>
To: i.grok@comcast.net, IETF-Discussion list <ietf@ietf.org>
In-Reply-To: <383ECAF1-8D1A-466E-997C-D07BE9E5907D@amsl.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Subject: Re: audio streaming archive...
Date: Thu, 21 Apr 2011 22:53:25 -0700
References: <201104140254.p3E2sMjk014471@fs4113.wdf.sap.corp>	<4DA67EF0.4050209@bogus.com> <20110415032222.GB22852@odin.ulthar.us> <4DABE255.3080209@bogus.com> <383ECAF1-8D1A-466E-997C-D07BE9E5907D@amsl.com>
X-Mailer: Apple Mail (2.936)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 05:53:29 -0000

To close the loop on this, VeriLAN did double check all of the  
recordings and, unfortunately, both streaming05 and streaming08 have  
identical files for that day.  Likely one of the files was mis-named  
and the sync process overwrote the local copies. However, VeriLAN does  
plan to make changes to the streaming software for the next meeting;  
these changes will include automation of the file naming and uploading  
process and this will hopefully eliminate missing and/or erroneously  
named recordings.

Alexa

On Apr 18, 2011, at 11:19 PM, Alexa Morris wrote:

> VeriLAN is going to check this computer on Wednesday (it's currently  
> located at a warehouse) to verify that all recordings were uploaded.  
> We'll know more shortly.
>
> Alexa
>
> On Apr 18, 2011, at 12:03 AM, Joel Jaeggli wrote:
>
>> On 4/14/11 8:22 PM, Scott Schmit wrote:
>>> On Wed, Apr 13, 2011 at 09:58:24PM -0700, Joel Jaeggli wrote:
>>>> there was a naming convention issue on the channel5 recorder  
>>>> which I
>>>> thought that we caught all of those by I could be wrong...
>>>>
>>>> The contractor has the channel8 recorder and should be able  
>>>> toretrive
>>>> the file.
>>>
>>> Is there an ETA for the fix to that?
>>
>> you might want to talk to the secretariate or the contractor (whom I
>> cced on the previous message) I don't have access to the equipment.
>>
>>> I listened to both the .mp3 and .mp3.1 file for wed-am ch8, and  
>>> neither
>>> sounds like the DANE session to me.
>>>
>>
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>>
>
> -----------
> Alexa Morris / Executive Director / IETF
> 48377 Fremont Blvd., Suite 117, Fremont, CA  94538
> Phone: +1.510.492.4089 / Fax: +1.510.492.4001
> Email: amorris@amsl.com
>
> Managed by Association Management Solutions (AMS)
> Forum Management, Meeting and Event Planning
> www.amsl.com <http://www.amsl.com/>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>

-----------
Alexa Morris / Executive Director / IETF
48377 Fremont Blvd., Suite 117, Fremont, CA  94538
Phone: +1.510.492.4089 / Fax: +1.510.492.4001
Email: amorris@amsl.com

Managed by Association Management Solutions (AMS)
Forum Management, Meeting and Event Planning
www.amsl.com <http://www.amsl.com/>


From hannes.tschofenig@gmx.net  Fri Apr 22 02:19:15 2011
Return-Path: <hannes.tschofenig@gmx.net>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id ED4E7E078E for <ietf@ietfc.amsl.com>; Fri, 22 Apr 2011 02:19:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.929
X-Spam-Level: 
X-Spam-Status: No, score=-101.929 tagged_above=-999 required=5 tests=[AWL=0.670, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sqfxalopN7KG for <ietf@ietfc.amsl.com>; Fri, 22 Apr 2011 02:19:15 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfc.amsl.com (Postfix) with SMTP id B0B1EE0692 for <ietf@ietf.org>; Fri, 22 Apr 2011 02:19:14 -0700 (PDT)
Received: (qmail invoked by alias); 22 Apr 2011 09:19:12 -0000
Received: from a88-115-222-204.elisa-laajakaista.fi (EHLO [192.168.1.3]) [88.115.222.204] by mail.gmx.net (mp022) with SMTP; 22 Apr 2011 11:19:12 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX18XMgRNL9sX9rH+QnFWFAHeW4J8qoQJwvPYIon0pW pnoVFzIy5X3+g+
Subject: Re: Call for a Jasmine Revolution in the IETF: Privacy, Integrity, Obscurity
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
In-Reply-To: <4D8A1514.1080403@earthlink.net>
Date: Fri, 22 Apr 2011 12:19:11 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <4960200F-99D0-420A-9842-E74C73820CA8@gmx.net>
References: <69C307E5-8B96-4604-960B-3270B8D01D8D@softarmor.com>	<4CA7D36B-B8DE-431F-AEEB-57675B6951AD@mnot.net>	<877B733B-F1CB-4087-BE82-0A1B07623D24@softarmor.com>	<DEC3D7BB-0EDE-4584-B5A0-35C6F54CD2CC@mnot.net>	<D44303D5-288B-4A44-BD07-8D5A3059BE45@softarmor.com>	<4D88BEE2.90504@tana.it>	<6.2.5.6.2.20110322211644.0db72cf8@resistor.net> <D85C5068-0F54-40D3-9A94-058C07894CFB@gmx.net> <4D8A1514.1080403@earthlink.net>
To: todd glassey <tglassey@earthlink.net>
X-Mailer: Apple Mail (2.1084)
X-Y-GMX-Trusted: 0
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 Apr 2011 09:19:16 -0000

I just notice your mail and thought I should respond given that you may =
have misunderstood something in this email conversation or in one of my =
responses.=20

When a working group works on a specific problem then they get =
requirements from many different sources. Some of these requirements may =
be purely technical (such as performance aspects, encoding related =
questions, etc.) but there are also requirements that come from the =
desire to meet certain deployment constraints. Often protocols build on =
top of something existing; they do not make the assumption of a clean =
slate. By doing this they take business models into consideration, and =
consider a certain type of responsibility sharing. There may also be =
regulatory actions that influenced the work. =
http://tools.ietf.org/html/draft-morris-policy-cons-00 summarize these =
observations. It is not an IAB document but, as the filename indicates, =
an individual submission. The authors are soliciting input from the IETF =
community on the document and to share their protocol development =
experience with us.=20

In any case, there are many requirements and the large number of =
guidelines we have protocol developers reflect this. Protocol design is =
not easy. Since a single person typically does not have the complete =
range of expertise needed we make use of directorates as well in the =
development of high-quality specifications.=20

Despite all these different sources for requirements the actual result =
(the output of the working group) is a technical specification. It may =
provide background information, instructions for implementers or for =
those who deploy.=20

The IAB and ISOC documents you mentioned in your other mails are =
slightly different. IAB documents, for example, may provide broader =
architectural advice. RFC 2804 "IETF Policy on Wiretapping" is such a =
document (written by IESG/IAB).=20
Again other documents concern the core role of the IAB, such as the RFC =
Editor and IANA.

You like to call everything "politics" particularly if you do not like a =
certain argument. This is not a particularly useful approach since it =
does not help me (and maybe others) to get insight into the argument you =
are trying to make.=20

Ciao
Hannes
(speaking for myself as an individual contributor to the IETF =
standardization process)=20

On Mar 23, 2011, at 5:43 PM, todd glassey wrote:

> On 3/23/2011 12:02 AM, Hannes Tschofenig wrote:
>> On Mar 23, 2011, at 6:52 AM, SM wrote:
>>=20
>>> The IETF can only address the technical problems.
>>=20
>> This is an argument I often hear. I do, however, believe that you =
cannot see technology in isolation.
>=20
> That's because you are being a political animal and not a pure =
technologist here which violates the charter of the IETF in spades.
>=20
> If the IETF is only set up to standardize technology then it cannot =
refuse to accept anything, further its members who try and block =
protocol's standardization regularly commit antitrust and TI by =
sabotaging various initiatives, and IMHO they need to be formally =
spanked (by lawyers) and sent to bed with no supper. There is no =
political or legal activity of the IETF in its standardization practice =
and it cannot implement social policy around what it standardizes and =
doesn't IMHO.
>> However, in many cases the technology, regulatory environment, =
business aspects, and the social context gets mixed together.
>> Please have a look at: =
http://tools.ietf.org/html/draft-morris-policy-cons-00
> only in the limited world of Social Networking...
>=20
> Todd Glasssey
>=20
>=20
>> Ciao
>> Hannes
>>=20
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>>=20
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From Francis.Dupont@fdupont.fr  Fri Apr 22 05:29:06 2011
Return-Path: <Francis.Dupont@fdupont.fr>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 2BCE6E0664 for <ietf@ietfc.amsl.com>; Fri, 22 Apr 2011 05:29:06 -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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YA1AFaISCMhC for <ietf@ietfc.amsl.com>; Fri, 22 Apr 2011 05:29:05 -0700 (PDT)
Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) by ietfc.amsl.com (Postfix) with ESMTP id 6657FE0694 for <ietf@ietf.org>; Fri, 22 Apr 2011 05:29:05 -0700 (PDT)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id p3MCT4WD022080 for <ietf@ietf.org>; Fri, 22 Apr 2011 14:29:04 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201104221229.p3MCT4WD022080@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: ietf@ietf.org
Subject: problems with mail.ietf.org
Date: Fri, 22 Apr 2011 14:29:04 +0200
Sender: Francis.Dupont@fdupont.fr
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 12:29:06 -0000

mail.ietf.org changed its IPv4 address (it was 64.170.98.32,
now it is 208.66.40.236) leaving at its previous address
something (i.e., a SMTP server) which blindly eats messages.

I strongly suggest to remove the SMTP server at
the previous address so it no longer misleads people
to believe their messages where successfully posted,
or worse, "I proposed to fix the IP protocol by putting
the addresses in the right order and nobody objects?!" (:-).

Thanks

Francis.Dupont@fdupont.fr

PS: telnet 64.170.98.32 smtp gets in the banner:
220 ietfb.amsl.com ESMTP Postfix
(on the correct 208.66.40.236 it is ietfc.amsl.com).

From elwynd@dial.pipex.com  Fri Apr 22 05:34:11 2011
Return-Path: <elwynd@dial.pipex.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 2CD3BE068A; Fri, 22 Apr 2011 05:34:11 -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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id clkCy6b1SrMi; Fri, 22 Apr 2011 05:34:10 -0700 (PDT)
Received: from auth.a.painless.aaisp.net.uk (c.5.0.d.2.7.e.f.f.f.8.4.0.3.2.0.0.3.0.0.0.0.0.0.0.b.8.0.1.0.0.2.ip6.arpa [IPv6:2001:8b0:0:30:230:48ff:fe72:d05c]) by ietfc.amsl.com (Postfix) with ESMTP id 7A809E0674; Fri, 22 Apr 2011 05:34:10 -0700 (PDT)
Received: from 250.254.187.81.in-addr.arpa ([81.187.254.250]) by a.painless.aaisp.net.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <elwynd@dial.pipex.com>) id 1QDFYl-0001nG-Sr; Fri, 22 Apr 2011 13:34:08 +0100
Subject: Gen-art review of draft-lear-iana-timezone-database-03
From: Elwyn Davies <elwynd@dial.pipex.com>
To: General Area Review Team <gen-art@ietf.org>
Content-Type: text/plain
Date: Fri, 22 Apr 2011 13:37:10 +0100
Message-Id: <1303475830.21284.19230.camel@mightyatom.folly.org.uk>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
Cc: draft-lear-iana-timezone-database.all@tools.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 Apr 2011 12:34:11 -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-lear-iana-timezone-database-01.txt
Reviewer: Elwyn Davies
Review Date: 22 April 2011
IETF LC End Date: 9 May 2011
IESG Telechat date: 12 May 2011

Summary:
Almost ready for the IESG.  This is my second review of the document.  

I suggested in the previous review that it might make life easier, particularly 
if an appeal was ever entered, if the document didn't use the RFC 5226 Designated 
Expert mechanism but defined the role separately.  This hasn't happened but the 
distinction is now clearer.  To make it quite clear I would be inclined to add 
'except as regards appeals against decisions of the Designated Expert 
(see Section 5)' after [RFC5226] in the definition of TZ Coordinator in Section 2.

Otherwise there are a couple of editorial nits.   

.
Nits/Editorial:
s3: s/policy policy/policy/ (repeated word)
s8, first para: s/filling/filling the role/ (maybe 'post')
s8, last para: s/TZ Coordinators/TZ Coordinator/
s10: s/Elwin/Elwyn/ (thanks for the ack!)


From tme@americafree.tv  Fri Apr 22 06:02:22 2011
Return-Path: <tme@americafree.tv>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 87478E0698 for <ietf@ietfc.amsl.com>; Fri, 22 Apr 2011 06:02:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.353
X-Spam-Level: 
X-Spam-Status: No, score=-104.353 tagged_above=-999 required=5 tests=[AWL=2.246, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zZa1yPDdSarp for <ietf@ietfc.amsl.com>; Fri, 22 Apr 2011 06:02:22 -0700 (PDT)
Received: from mail.americafree.tv (rossini.americafree.tv [63.105.122.34]) by ietfc.amsl.com (Postfix) with ESMTP id 071A3E067C for <ietf@ietf.org>; Fri, 22 Apr 2011 06:02:22 -0700 (PDT)
Received: from [IPv6:::1] (rossini.americafree.tv [63.105.122.34]) by mail.americafree.tv (Postfix) with ESMTP id D2B6DA8BE6C6; Fri, 22 Apr 2011 09:02:21 -0400 (EDT)
Subject: Re: problems with mail.ietf.org
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Marshall Eubanks <tme@americafree.tv>
In-Reply-To: <201104221229.p3MCT4WD022080@givry.fdupont.fr>
Date: Fri, 22 Apr 2011 09:02:20 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <B95FD1F7-F19F-4F7C-A0B8-F2199AA518E2@americafree.tv>
References: <201104221229.p3MCT4WD022080@givry.fdupont.fr>
To: Francis Dupont <Francis.Dupont@fdupont.fr>
X-Mailer: Apple Mail (2.1081)
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 Apr 2011 13:02:22 -0000

I have reported this issue. Something will be posted here when it is =
resolved.

Regards
Marshall


On Apr 22, 2011, at 8:29 AM, Francis Dupont wrote:

> mail.ietf.org changed its IPv4 address (it was 64.170.98.32,
> now it is 208.66.40.236) leaving at its previous address
> something (i.e., a SMTP server) which blindly eats messages.
>=20
> I strongly suggest to remove the SMTP server at
> the previous address so it no longer misleads people
> to believe their messages where successfully posted,
> or worse, "I proposed to fix the IP protocol by putting
> the addresses in the right order and nobody objects?!" (:-).
>=20
> Thanks
>=20
> Francis.Dupont@fdupont.fr
>=20
> PS: telnet 64.170.98.32 smtp gets in the banner:
> 220 ietfb.amsl.com ESMTP Postfix
> (on the correct 208.66.40.236 it is ietfc.amsl.com).
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>=20


From john-ietf@jck.com  Fri Apr 22 08:59:59 2011
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 4C57CE0767 for <ietf@ietfc.amsl.com>; Fri, 22 Apr 2011 08:59:59 -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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EPYrnp2E5ozs for <ietf@ietfc.amsl.com>; Fri, 22 Apr 2011 08:59:58 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfc.amsl.com (Postfix) with ESMTP id 9E2B3E065A for <ietf@ietf.org>; Fri, 22 Apr 2011 08:59:58 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QDIls-000AMk-Qr; Fri, 22 Apr 2011 11:59:52 -0400
Date: Fri, 22 Apr 2011 11:59:52 -0400
From: John C Klensin <john-ietf@jck.com>
To: Francis Dupont <Francis.Dupont@fdupont.fr>, ietf@ietf.org
Subject: Re: problems with mail.ietf.org
Message-ID: <7667BF995BE1DD6CAFE86F10@PST.JCK.COM>
In-Reply-To: <201104221229.p3MCT4WD022080@givry.fdupont.fr>
References: <201104221229.p3MCT4WD022080@givry.fdupont.fr>
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, 22 Apr 2011 15:59:59 -0000

--On Friday, April 22, 2011 14:29 +0200 Francis Dupont
<Francis.Dupont@fdupont.fr> wrote:

> mail.ietf.org changed its IPv4 address (it was 64.170.98.32,
> now it is 208.66.40.236) leaving at its previous address
> something (i.e., a SMTP server) which blindly eats messages.
> 
> I strongly suggest to remove the SMTP server at
> the previous address so it no longer misleads people
> to believe their messages where successfully posted,
> or worse, "I proposed to fix the IP protocol by putting
> the addresses in the right order and nobody objects?!" (:-).

Francis,

I don't understand what you think is a problem or what problem
you are encountering.   An MX query for ietf.org yields
mail.ietf.org and an address query for the latter yields the
current address (as do the additional information records for
the first query).  Both sets of records seem to have
appropriately-short TTLs.  So I'm having trouble guessing why
your systems are still seeing 64.170.93.22, much less sending
mail to it.

I agree that having a system floating around that runs an SMTP
server but that eats messages ("blindly" or not) is undesirable
as an operational policy, but I'm having trouble understanding
why any of us should actually care if other things are
configured and working correctly (as they appear to be).

Could you explain?

    john



From Francis.Dupont@fdupont.fr  Fri Apr 22 09:14:09 2011
Return-Path: <Francis.Dupont@fdupont.fr>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 4F3FBE0689 for <ietf@ietfc.amsl.com>; Fri, 22 Apr 2011 09:14:09 -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, NORMAL_HTTP_TO_IP=0.001]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 91No+ZAB3taq for <ietf@ietfc.amsl.com>; Fri, 22 Apr 2011 09:14:08 -0700 (PDT)
Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) by ietfc.amsl.com (Postfix) with ESMTP id 3D975E065A for <ietf@ietf.org>; Fri, 22 Apr 2011 09:14:08 -0700 (PDT)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id p3MGE7Pb035866; Fri, 22 Apr 2011 18:14:07 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201104221614.p3MGE7Pb035866@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: John C Klensin <john-ietf@jck.com>
Subject: Re: problems with mail.ietf.org 
In-reply-to: Your message of Fri, 22 Apr 2011 11:59:52 EDT. <7667BF995BE1DD6CAFE86F10@PST.JCK.COM> 
Date: Fri, 22 Apr 2011 18:14:07 +0200
Sender: Francis.Dupont@fdupont.fr
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 Apr 2011 16:14:09 -0000

 In your previous mail you wrote:

   So I'm having trouble guessing why your systems are still seeing
   64.170.93.22, much less sending mail to it.
   
=> a long time ago mail.ietf.org anti-spam dropped SMTP over IPv6
from a MTA address without a PTR. I put a workaround using the IPv4
address (the old one), it was fixed but I didn't remove the
workaround.

   I agree that having a system floating around that runs an SMTP
   server but that eats messages ("blindly" or not) is undesirable
   as an operational policy.

=> exactly and BTW 32.98.170.64.in-addr.arpa has still a PTR to
mail.ietf.org.
   
Regards

Francis.Dupont@fdupont.fr

From john-ietf@jck.com  Fri Apr 22 09:34:23 2011
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id BB4B1E0703 for <ietf@ietfc.amsl.com>; Fri, 22 Apr 2011 09:34:23 -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, NORMAL_HTTP_TO_IP=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x6Frezy1zyAK for <ietf@ietfc.amsl.com>; Fri, 22 Apr 2011 09:34:23 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfc.amsl.com (Postfix) with ESMTP id ED5E0E065A for <ietf@ietf.org>; Fri, 22 Apr 2011 09:34:22 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QDJJG-000Aku-CH; Fri, 22 Apr 2011 12:34:22 -0400
Date: Fri, 22 Apr 2011 12:34:21 -0400
From: John C Klensin <john-ietf@jck.com>
To: Francis Dupont <Francis.Dupont@fdupont.fr>
Subject: Re: problems with mail.ietf.org
Message-ID: <E9078B26CC37B83DB679E1C3@PST.JCK.COM>
In-Reply-To: <201104221614.p3MGE7Pb035866@givry.fdupont.fr>
References: <201104221614.p3MGE7Pb035866@givry.fdupont.fr>
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, 22 Apr 2011 16:34:23 -0000

--On Friday, April 22, 2011 18:14 +0200 Francis Dupont
<Francis.Dupont@fdupont.fr> wrote:

>  In your previous mail you wrote:
> 
>    So I'm having trouble guessing why your systems are still
> seeing    64.170.93.22, much less sending mail to it.
>    
> => a long time ago mail.ietf.org anti-spam dropped SMTP over
> IPv6 from a MTA address without a PTR. I put a workaround
> using the IPv4 address (the old one), it was fixed but I
> didn't remove the workaround.

It then seems to me that the only thing that ought to be done on
an emergency basis is precisely for you to get rid of the
workaround.   As operational practices go, leaving kludges in
place longer than needed is always a cause of problems sooner or
later.

>    I agree that having a system floating around that runs an
> SMTP    server but that eats messages ("blindly" or not) is
> undesirable    as an operational policy.
> 
> => exactly and BTW 32.98.170.64.in-addr.arpa has still a PTR to
> mail.ietf.org.

Yep.  Both should probably be cleared up, but it isn't something
I could easily be convinced is an emergency.

best,
    john


From jmh@joelhalpern.com  Fri Apr 22 09:48:18 2011
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 75374E06C0; Fri, 22 Apr 2011 09:48:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.502
X-Spam-Level: 
X-Spam-Status: No, score=-102.502 tagged_above=-999 required=5 tests=[AWL=0.097, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MCuvF2ArPEk8; Fri, 22 Apr 2011 09:48:17 -0700 (PDT)
Received: from hermes.out.tigertech.net (hermes.out.tigertech.net [74.114.88.72]) by ietfc.amsl.com (Postfix) with ESMTP id 3A228E0686; Fri, 22 Apr 2011 09:48:17 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.tigertech.net (Postfix) with ESMTP id CE9E54300D5; Fri, 22 Apr 2011 09:48:16 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hermes.tigertech.net
Received: from [10.10.10.101] (pool-71-161-51-218.clppva.btas.verizon.net [71.161.51.218]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by hermes.tigertech.net (Postfix) with ESMTPSA id 8E6EE4300D1; Fri, 22 Apr 2011 09:48:15 -0700 (PDT)
Message-ID: <4DB1B14E.8070003@joelhalpern.com>
Date: Fri, 22 Apr 2011 12:48:14 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.15) Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: "A. Jean Mahoney" <mahoney@nostrum.com>
Subject: [Gen-art] Review: draft-ietf-mboned-maccnt-req-10
References: <4DB0E78E.4050406@nostrum.com>
In-Reply-To: <4DB0E78E.4050406@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: mboned@ietf.org, gen-art@ietf.org, Marshall Eubanks <tme@multicasttech.com>, 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, 22 Apr 2011 16:48:18 -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-mboned-maccnt-req-10
     Requirements for Multicast AAA coordinated between
         Content Provider(s) and Network Service Provider(s)
Reviewer: Joel M. Halpern
Review Date: 22-April-2011
IETF LC End Date: 5-May-2011	
IESG Telechat date: N/A

Summary: This document is not ready for publication as an Informational RFC.

Top Line: This document seems to assume a very specific deployment and a 
specific set of tools from our repertoire.  It also tends to make 
assumptions about the solution that it envisions, which confuse the 
requirements statements.  As such, it needs significant work before it 
may be suitable for publication.

Major issues:
1) The document assumes a specific set of protocols are used, and are 
the only tools used, for handling the problem space.  IGMP / MLD is not 
our only tool, and the document should not be written as if it is the 
only tool.
----  This was noted in a 2006 Discuss comment! ----

1') The document says that it is about Requirements for AAA related to 
Multicast.  It then repeatedly dives into QoS issues.  Other than the 
quesiton of enabling the AAA to provide the QoS information (which is 
never discussed at all), QoS should not appear in this document.

There seem to be a number of cases in section 4 of assuming a solution, 
rather than stating the requirements.

2) After postulating a business model in which the network operator and 
the content provider are distinct, the requirements then assert that 
content distribution control is the network's job.  Enabling the content 
provider to ensure that only authorized users get content is the 
network's job.  But the methods for doing so should be left to the 
solution, not the requirements.  (And then makign the requirement a 
network option makes it even more confusing.)

3) The item on Sharing Program Data seems to have some sort of 
assumption about how information is managed.  Since I can easily 
envision architectures for the separation, which allow multicast, which 
do not required what the document calls "Shard Programming data", there 
seems to be a problem here.

4) In section 5, the documents appears to assume that the network must 
and needs to unilaterally decide whether to admit users to multicast 
trees.  It also states that this is needed for QoS protection.  Given 
the nature of multicast, both statements are likely misleading.

5) The last paragraph of section 5 seems to assert that the operator 
could choose not to deliver some multicast streams to some subscribers 
if this would adversely affect the QoS experienced by other users.  I 
think that there are serious problems with such an assertion appearing 
in an IETF informational document.

6) The section on concomitant requirements mixes items of a different 
nature together.  It has one item that really belongs in this document, 
namely scale.  It has one very confusing item, namely Small Impact on 
the Existing Product.  And the rest of the items in teh section do not 
belong in this document at all.

6') On the "Small Impact" item, given that different operators have 
deployed different solutions, using different pieces of technology, it 
seems very hard to define a solution that has "small" impact on all 
operators.

7) What is section 9?  Is it a diagram  of some existing deployment 
architecture?  Is it an effort to define a solution?  It does not define 
any requirements.

Minor issues:
1) I find the approach the document takes to its "requirements" 
ingenuous, and misleading.  The document is actually a proposal for a 
business model that it wants supported.  This business model includes 
well-respected notions, such as the separation of content providers from 
network operators.  it also includes assumptions about the charging 
basis for the service, and who needs what visibility to whom.  While 
these may indeed be accurate assumptions, treating them as givens, on 
the basis of which a set of requirements can be asserted, seems 
inappropriate.

2) There is a related implicit assumption that individual user usage is 
somehow related to overall network consumption.  The whole point of 
using multicast is to avoid that coupling, i.e. the increase in network 
consumption is much lower than the increase in user consumption.

3) The paragraph in section 5 on the user edge stream join admissions 
seems to be about a particular view of how an operator would deliver 
suitable QoS to a subscriber.  This seems to assume certain 
relationships between the user's requests and the operators network, and 
certain operational behaviors.  They may or may not be accurate.  They 
also appear to be a local matter, having nothing to do with the rest of 
the document.

4) Given that section 6 calls for a method for deauthorization, it seems 
that there should be some additional explanation of why reauthorization 
is needed.  This also leads to the question of whether we are expecting 
the network to enforce the cotnent providers charging relationships with 
the end user, including expiration of prepaid quanta, and other 
complexities that are better left purely to the content provider.  A 
pure deauthorization model would seem sufficient.)

5) I do not understand what section 7, on performance requirements, is 
doing in thsi document.  It has a lot to do with whether a given network 
architecture is suitable for a given content provider's desired end 
customer interaction.  But it has nothing to do with the accounting or 
customer identification problems that this document says that it deals with.

Nits/editorial comments:
The document style does not make clear what the actual requirements are.

From msk@cloudmark.com  Fri Apr 22 11:57:56 2011
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id E8326E07CF for <ietf@ietfc.amsl.com>; Fri, 22 Apr 2011 11:57:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.122
X-Spam-Level: 
X-Spam-Status: No, score=-104.122 tagged_above=-999 required=5 tests=[AWL=-1.523, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4MDrOH-ZMXKI for <ietf@ietfc.amsl.com>; Fri, 22 Apr 2011 11:57:56 -0700 (PDT)
Received: from ht2-outbound.cloudmark.com (ht2-outbound.cloudmark.com [72.5.239.36]) by ietfc.amsl.com (Postfix) with ESMTP id 3CAD9E0655 for <ietf@ietf.org>; Fri, 22 Apr 2011 11:57:56 -0700 (PDT)
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by spite.corp.cloudmark.com ([172.22.10.72]) with mapi; Fri, 22 Apr 2011 11:57:55 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: IETF Discussion <ietf@ietf.org>
Date: Fri, 22 Apr 2011 11:57:53 -0700
Subject: RE: Review of:  draft-iab-dns-applications-01
Thread-Topic: Review of:  draft-iab-dns-applications-01
Thread-Index: Acv/aMwZlc7cT9cuTZSILouInOPzrAA78j9g
Message-ID: <F5833273385BB34F99288B3648C4F06F1343319FD8@EXCH-C2.corp.cloudmark.com>
References: <4DAEF008.6040101@dcrocker.net>
In-Reply-To: <4DAEF008.6040101@dcrocker.net>
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: Fri, 22 Apr 2011 18:57:57 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of D=
ave CROCKER
> Sent: Wednesday, April 20, 2011 7:39 AM
> To: Olaf Kolkman; Jon Peterson; Hannes Tschofenig; Bernard Aboba
> Cc: IETF Discussion
> Subject: Review of: draft-iab-dns-applications-01
>=20
> Review --
>=20
> Title:        Architectural Considerations on Application Features in the=
 DNS
> By:           Kolkman, Peterson, Tschofenig, Aboba
> I-D:          draft-iab-dns-applications-01
>=20
> Reviewer:     D. Crocker <dcrocker@bbiw.net>
> Review Date:  20 April 2011
>=20
> [...]

I concur with many of Dave's review comments here.  My own experience with =
the IETF starts around the time of SPF and its various successors, nearly a=
ll of which use the DNS to store some variants of policy or key data, so th=
is is a topic near and dear to most of my endeavors, and there are more com=
ing.

A couple of other recommendations of my own:

- Where the document enumerates requirements incompatible with the DNS, sug=
gested alternatives might be wise to include, with some (perhaps brief, per=
haps not) description of why/how the alternative is more appropriate.

- The issue of detecting administrative boundaries in the DNS keeps reappea=
ring.  This might be good fodder for another document, since that topic plu=
s that of the idea of "public suffix lists" has been recurring with increas=
ing frequency.

- IETF 80's training day included a session about how to go about extending=
 the DNS by registering new types rather than overloading existing ones.  S=
ome of the material presented there might be useful to include here.

-MSK

From ron.even.tlv@gmail.com  Fri Apr 22 12:26:12 2011
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 3F261E0852; Fri, 22 Apr 2011 12:26:12 -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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tuPa96dXr1NG; Fri, 22 Apr 2011 12:26:11 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfc.amsl.com (Postfix) with ESMTP id 3C0C9E0848; Fri, 22 Apr 2011 12:26:11 -0700 (PDT)
Received: by wwa36 with SMTP id 36so593129wwa.13 for <multiple recipients>; Fri, 22 Apr 2011 12:26:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-type:content-transfer-encoding :x-mailer:thread-index:content-language; bh=2pwT8OjK33EcV3I9k+zrp8AMSuCY6DLayLfix/bd2Pw=; b=meRfUYEoKGgPZTd+67XrK++U6UoBHfIYNTfFtHq/d88gHe0W/bVvJI4UA0g5mrFwpX t/XE6RFseGbPLQHHo93KVPfWa2Sam0wGdIU63/UWyL3yjc8izsXjbbQ1GscD6Eh9qtBR UoSmoChJGVfHupYSscTrtuZoAMZ5PCTMtmZcI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:x-mailer :thread-index:content-language; b=kmGEVVlLLgevbg5C0agQcH/PzE3dVZgFjYAVkUKJ5mh4kxXqpTszOp4+ynGAs6udLX 5q+Gstgai09VEpw+cgFUyLJBkIhkLJ3j5lKUEvEq04M54hpfFZDP+t3VGXL5MHC+408J RarxmZlFyP3WUMwNXO4IfJWFIYmv77+qFfL9I=
Received: by 10.216.69.203 with SMTP id n53mr970129wed.88.1303500370589; Fri, 22 Apr 2011 12:26:10 -0700 (PDT)
Received: from windows8d787f9 (bzq-79-181-29-160.red.bezeqint.net [79.181.29.160]) by mx.google.com with ESMTPS id bs4sm1901075wbb.35.2011.04.22.12.26.05 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 22 Apr 2011 12:26:08 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Dan Harkins'" <dharkins@lounge.org>
References: <4da2f037.cf03d90a.5d44.fffff941@mx.google.com> <9a944e460983182912fe0d2e85ef32f9.squirrel@www.trepanning.net>
In-Reply-To: <9a944e460983182912fe0d2e85ef32f9.squirrel@www.trepanning.net>
Subject: RE: Gen-ART LC review of draft-harkins-ipsecme-spsk-auth-03
Date: Fri, 22 Apr 2011 22:25:00 +0300
Message-ID: <4db1d650.04b4e30a.337e.ffffa569@mx.google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcwAhbL1u1YBRenYQua/hFaSx2z3KwAnCDZg
Content-Language: en-us
Cc: gen-art@ietf.org, 'IETF-Discussion list' <ietf@ietf.org>, draft-harkins-ipsecme-spsk-auth.all@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, 22 Apr 2011 19:26:12 -0000

Hi Dan,
About my first  comment what I meant that section 6 say "   For the purposes
of interoperability, a password pre-processing technique of "None" MUST be
supported.". I now understand that in section 8.5 and 8.6 you say that the
initiator may decide not to use the "none" technique and therefore may not
find an interoperable mode. 
If the initiator will use "none" technique than you will have
interoperability. 
Roni

> -----Original Message-----
> From: Dan Harkins [mailto:dharkins@lounge.org]
> Sent: Friday, April 22, 2011 3:39 AM
> To: Roni Even
> Cc: draft-harkins-ipsecme-spsk-auth.all@tools.ietf.org; gen-
> art@ietf.org; 'IETF-Discussion list'
> Subject: Re: Gen-ART LC review of draft-harkins-ipsecme-spsk-auth-03
> 
> 
>   Hi Roni,
> 
>   Thank you for reviewing my draft. Comments inline....
> 
> On Mon, April 11, 2011 5:11 am, Roni Even 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.
> >
> > Minor issues:
> >
> > 1.	In section 8.5 and 8.6 the draft says that "If no more password
> > pre-processing techniques are supported the exchange MUST be
> > terminated."
> > Reading section 6, I thought that NONE MUST be supported for
> > interoperability purpose.
> 
>   One of the valid techniques for password pre-processing is "none".
> That doesn't mean that there isn't a technique, it means the technique
> is to perform no pre-processing on the password (treat it as a raw
> blob of bits).
> 
> > 2.	In section 8.1 and in figure 1 and figure 2 is there a maximum
> value
> > for "counter"?
> 
>   No there isn't, but it is doubtful the number will get very large.
> The probability that more than n iterations is necessary will be
> roughly (1-(r/2p))^n, where r is the order and p is the prime, and
> that number rapidly approaches zero as n increases.
> 
> > Nits/editorial comments:
> >
> > 1.       In section 1 just before 1.1 you have "suceed" instead of
> > "succeed"
> >
> > 2.       In section 4 third bullet "an" instead of "and"
> >
> > 3.       In section 4.2 "Two elementx" instead of "Two elements"
> >
> > 4.       In section 5 second row "authenticaiton" should be
> > "authentication"
> >
> > 5.       In section 6 fourth row "identitcal" instead of "identical"
> 
>   Thank you for catching all of these.
> 
>   regards,
> 
>   Dan.



From alexey.melnikov@isode.com  Fri Apr 22 12:32:18 2011
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 88573E0855; Fri, 22 Apr 2011 12:32:18 -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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d-YRpTHrCAUd; Fri, 22 Apr 2011 12:32:17 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by ietfc.amsl.com (Postfix) with ESMTP id 5DEBCE0869; Fri, 22 Apr 2011 12:32:17 -0700 (PDT)
Received: from [188.29.6.68] (188.29.6.68.threembb.co.uk [188.29.6.68])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <TbHXvQBK47pk@rufus.isode.com>; Fri, 22 Apr 2011 20:32:15 +0100
Message-ID: <4DB1D785.3080200@isode.com>
Date: Fri, 22 Apr 2011 20:31:17 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Ben Campbell <ben@estacado.net>
Subject: Re: Gen-ART LC review of draft-ietf-kitten-digest-to-historic-03
References: <802CB0FD-9C90-421A-98D2-F1E2F2D644B7@estacado.net>
In-Reply-To: <802CB0FD-9C90-421A-98D2-F1E2F2D644B7@estacado.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: General Area Review Team <gen-art@ietf.org>, The IETF <ietf@ietf.org>, draft-ietf-kitten-digest-to-historic.all@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, 22 Apr 2011 19:32:18 -0000

Hi Ben,
Thanks for your review.

Ben Campbell 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-kitten-digest-to-historic-03
>Reviewer: Ben Campbell
>Review Date: 2011-04-11
>IETF LC End Date: 2011-04-15
>
>Summary: This draft is essentially ready for publication as an informational RFC. I have a couple of editorial comments that should be considered prior to final publication.
>
>Major issues: None
>
>Minor issues: None
>
>Nits/editorial comments:
>
>-- Note following abstract:
>
>Will this note stay in the RFC? The note makes me unsure whether the resulting RFC is intended to actually execute the deprecation, recommend deprecation, or start a discussion about deprecation. I assume from the IANA section, you intend the first.-
>
The note removed and the second sentence of the abstracted reworded to 
say that the document is deprecating/moving to historic.

>-- Section 1, 7B. "Lack of hash agility."
>
>Can you elaborate on what this means? (I think I know, but I don't know if it will be obvious to all readers)
>
Some explanation added.


From paf@cisco.com  Fri Apr 22 12:33:09 2011
Return-Path: <paf@cisco.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 70EACE0830 for <ietf@ietfc.amsl.com>; Fri, 22 Apr 2011 12:33:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.549
X-Spam-Level: 
X-Spam-Status: No, score=-9.549 tagged_above=-999 required=5 tests=[AWL=0.750,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s+XtPlxiM-Zz for <ietf@ietfc.amsl.com>; Fri, 22 Apr 2011 12:33:08 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfc.amsl.com (Postfix) with ESMTP id 2C0EBE06E8 for <ietf@ietf.org>; Fri, 22 Apr 2011 12:32:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=paf@cisco.com; l=2522; q=dns/txt; s=iport; t=1303500776; x=1304710376; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=c6eB64sz0OWWeIdeqjbaDI69LP6BlD3dRMmPPHnVrcc=; b=jTunIsHgti+pGaqnH0Eyn1c1FmCKaR570U6G9+NV8GcRMJ1PdsaPyIBQ HndcRJmyg9Imoj1s13Moyun3flxT/x+D3w4JPfqjA4gd4jxHRCqt1mB1Y 0UIWnhhjLkNF9hdHAUzV+f7khcKyFMgRngb5xJ04IlzcYqfto3W+mj07J 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvMDAFjXsU2Q/khLgWdsb2JhbAClZhQBARYmJYhwn3icUoV2BI4t
X-IronPort-AV: E=Sophos;i="4.64,255,1301875200"; d="scan'208";a="84767278"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-1.cisco.com with ESMTP; 22 Apr 2011 19:32:55 +0000
Received: from ams3-vpn-dhcp7637.cisco.com (ams3-vpn-dhcp7637.cisco.com [10.61.93.212]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p3MJWsW0026077; Fri, 22 Apr 2011 19:32:54 GMT
Subject: Re: Review of:  draft-iab-dns-applications-01
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
In-Reply-To: <4DAEF008.6040101@dcrocker.net>
Date: Fri, 22 Apr 2011 21:32:54 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <CF47433F-1B69-44FA-A929-7020BAFB1C18@cisco.com>
References: <4DAEF008.6040101@dcrocker.net>
To: Olaf Kolkman <olaf@nlnetlabs.nl>, Jon Peterson <jon.peterson@neustar.biz>,  Hannes Tschofenig <Hannes.Tschofenig@gmx.net>, Bernard Aboba <bernarda@microsoft.com>
X-Mailer: Apple Mail (2.1084)
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: Fri, 22 Apr 2011 19:33:09 -0000

FWIW, in general I think the document is good, and I am not a person =
that get hang up much things... Other people are much better on giving =
such comments ;-)

But, I think there is one section that should have an addition, of =
possible change, end of section 4:

>    In cases where applications require these sorts of features, they =
are
>    simply better instantiated by independent application-layer =
protocols
>    than the DNS.  The query-response semantics of the DNS are easily
>    replicated by HTTP, for example, and the objects which HTTP can =
carry
>    both in queries and responses can easily contain the necessary
>    structure to manage compound queries.  Similarly, HTTP has numerous
>    ways to provide the necessary authentication, authorization and
>    confidentiality properties that some features require.
>=20
>    Where the administrative delegations of the DNS form a necessary
>    component in the instantiation of an application feature, there are
>    various ways that the DNS can bootstrap access to an independent
>    application-layer protocol better suited to field the queries in
>    question.  For example, since NAPTR records can contain URIs, those
>    URI can point to an external query-response service such as HTTP,
>    with a NAPTR service field that signal to applications that =
questions
>    of interest can be answered at that service.

FWIW, I went through (together with Olaf) a registration process of the =
URI Resource Record Type that would help solving exactly this problem. =
To be a tool in between SRV and NAPTR, where a prefix on an owner do sub =
selection of records (like SRV, instead of inside RDATA like NAPTR), and =
the RDATA is ordered set of URIs (instead of more complicated NAPTR =
RDATA structure that require rewrite rules in the DDDS), and be more =
structured that storing URIs in TXT records.

URI is registered as RR TYPE 256 since a while back (not too long =
though).

So, let me suggest the last sentence is changed to the following =
(because I think referencing a NAPTR and because of the requirement of =
defining a DDDS, when in reality the only thing one want is OWNER -> URI =
mapping):

> For example, since URI records can contain URIs, those
> URIs can point to an external query-response service such as HTTP,
> where the prefix of the URI is used by the applications to select
> the RR SET, and because of the HTTP based services, that is of =
interest.

   Patrik


From ben@estacado.net  Fri Apr 22 12:57:49 2011
Return-Path: <ben@estacado.net>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id C9B65E06C0; Fri, 22 Apr 2011 12:57:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.549
X-Spam-Level: 
X-Spam-Status: No, score=-2.549 tagged_above=-999 required=5 tests=[AWL=-0.050, BAYES_00=-2.599, RDNS_DYNAMIC=0.1]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BQfUe+nRu32C; Fri, 22 Apr 2011 12:57:37 -0700 (PDT)
Received: from estacado.net (dsl001-129-069.dfw1.dsl.speakeasy.net [72.1.129.69]) by ietfc.amsl.com (Postfix) with ESMTP id 65D96E0679; Fri, 22 Apr 2011 12:57:37 -0700 (PDT)
Received: from dn3-227.estacado.net (dn3-227.estacado.net [172.16.3.227]) (authenticated bits=0) by estacado.net (8.14.3/8.14.3) with ESMTP id p3MJuICI020612 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 22 Apr 2011 14:56:20 -0500 (CDT) (envelope-from ben@estacado.net)
From: Ben Campbell <ben@estacado.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Gen-ART LC Review of draft-ietf-dnsop-as112-ops-06
Date: Fri, 22 Apr 2011 14:56:18 -0500
Message-Id: <B409BC07-296F-4BE4-AD5D-DBAC5EAEA38F@estacado.net>
To: draft-ietf-dnsop-as112-ops.all@tools.ietf.org
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Cc: General Area 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, 22 Apr 2011 19:57:50 -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-dnsop-as112-ops-06
Reviewer:  Ben Campbell
Review Date: 2011-04-22
IETF LC End Date: 2011-04-28
IESG Telechat date: 2011-04-28

Summary:

This draft is almost ready for publication as an informational RFC. I =
have a small number of minor issue comments that should be considered =
prior to publication.

Major issues:

None

Minor issues:

-- General

The draft seems to take the form of a BCP, in that it proposes certain =
best practices for configuring and operating AS112 servers. I assume =
this has already been considered and discarded--I mention it as an =
observation only, and don't expect it to change unless others think it =
should.

-- Section 2.2:

Are these addresses stable enough to publish them literally?

-- Section 3.3:

Do we really want to be in the business of recommending an operating =
system? Even if the recommendation holds true today, it could easily =
change in the future. (note that I'm not objecting to using a particular =
platform for examples in e doc)

Nits/editorial comments:

-- general

IDNits complains about some obsolete references--please check. It also =
complains about non-RFC2606-compliant FQDNs non-RFC5735-compliant IPv4 =
addresses. I don't think those are applicable since these are, for the =
most part, not example names and addresses. =20

-- Section 1, paragraph 3:

Can you reference something that talks about the AS112 project as a =
whole?

From bernard_aboba@hotmail.com  Fri Apr 22 16:45:45 2011
Return-Path: <bernard_aboba@hotmail.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 188A9E066B for <ietf@ietfc.amsl.com>; Fri, 22 Apr 2011 16:45:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.598
X-Spam-Level: 
X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0LmdvNbCVTjC for <ietf@ietfc.amsl.com>; Fri, 22 Apr 2011 16:45:42 -0700 (PDT)
Received: from blu0-omc2-s32.blu0.hotmail.com (blu0-omc2-s32.blu0.hotmail.com [65.55.111.107]) by ietfc.amsl.com (Postfix) with ESMTP id BB6D6E065F for <ietf@ietf.org>; Fri, 22 Apr 2011 16:45:42 -0700 (PDT)
Received: from BLU152-W56 ([65.55.111.72]) by blu0-omc2-s32.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 22 Apr 2011 16:45:43 -0700
Message-ID: <BLU152-w567DE3D1C85CA216990A7593950@phx.gbl>
Content-Type: multipart/alternative; boundary="_065705d6-0777-432c-bdeb-4b91ceec5457_"
X-Originating-IP: [63.231.32.97]
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: <ietf@ietf.org>, <ops-dir@ops.ietf.org>
Subject: Review of draft-ietf-ecrit-phonebcp
Date: Fri, 22 Apr 2011 16:45:41 -0700
Importance: Normal
MIME-Version: 1.0
X-OriginalArrivalTime: 22 Apr 2011 23:45:43.0493 (UTC) FILETIME=[64F42750:01CC0147]
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 23:45:45 -0000

--_065705d6-0777-432c-bdeb-4b91ceec5457_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


I reviewed the document draft-ietf-ecrit-phonebcp in general
and for its operational impact. =20
=20
Operations directorate reviews are solicited primarily to help the area
directors improve their efficiency=2C particularly when preparing for IESG
telechats=2C and allowing them to focus on documents requiring their attent=
ion
and spend less time on the trouble-free ones.

Improving the documents is important=2C but clearly a secondary purpose.
A third purpose is to broaden the OpsDir reviewers' exposure to work going
on in other parts of the IETF.
=20
Reviews from OpsDir members do not in and of themselves cause the IESG to
raise issue with a document. The reviews may=2C however=2C convince individ=
ual
IESG members to raise concern over a particular document requiring further
discussion. The reviews=2C particularly those conducted in last call and
earlier=2C may also help the document editors improve their documents.

 The views represented here are those of the reviewer and do not represent =
the
opinion of any other entity=2C including the Operations Directorate.=20

------------------------------------------------
Review Summary:=20
Intended status:  Best Current Practice
=20
   This memo describes best current practice for how devices=2C
   networks=2C service providers and Public Safety Answering
   Points (PSAPs) should use IETF standards for emergency calling
   over IP networks.=20
=20
Is the document readable?

In general the document is reasonably well organized.  However=2C there are=
 some requirements
that do not seem easily translated into specific implementation or deployme=
nt guidance.=20
See detailed comments for examples.
=20
Does it contain nits?

Maybe.

idnits 2.12.09=20

tmp/draft-ietf-ecrit-phonebcp-17.txt:
tmp/draft-ietf-ecrit-phonebcp-17.txt(1142): Found possible FQDN 'test.sos.a=
mbulance' in position 3=3B this doesn't match RFC 2606's suggested ".exampl=
e" or ".example.(com|org|net)".
tmp/draft-ietf-ecrit-phonebcp-17.txt(1143): Found possible FQDN 'test.sos.a=
nimal' in position 3=3B this doesn't match RFC 2606's suggested ".example" =
or ".example.(com|org|net)".
tmp/draft-ietf-ecrit-phonebcp-17.txt(1144): Found possible FQDN 'test.sos.f=
ire' in position 3=3B this doesn't match RFC 2606's suggested ".example" or=
 ".example.(com|org|net)".
tmp/draft-ietf-ecrit-phonebcp-17.txt(1145): Found possible FQDN 'test.sos.g=
as' in position 3=3B this doesn't match RFC 2606's suggested ".example" or =
".example.(com|org|net)".
tmp/draft-ietf-ecrit-phonebcp-17.txt(1146): Found possible FQDN 'test.sos.m=
arine' in position 3=3B this doesn't match RFC 2606's suggested ".example" =
or ".example.(com|org|net)".
tmp/draft-ietf-ecrit-phonebcp-17.txt(1147): Found possible FQDN 'test.sos.m=
ountain' in position 3=3B this doesn't match RFC 2606's suggested ".example=
" or ".example.(com|org|net)".
tmp/draft-ietf-ecrit-phonebcp-17.txt(1148): Found possible FQDN 'test.sos.p=
hysician' in position 3=3B this doesn't match RFC 2606's suggested ".exampl=
e" or ".example.(com|org|net)".
tmp/draft-ietf-ecrit-phonebcp-17.txt(1149): Found possible FQDN 'test.sos.p=
oison' in position 3=3B this doesn't match RFC 2606's suggested ".example" =
or ".example.(com|org|net)".
tmp/draft-ietf-ecrit-phonebcp-17.txt(1150): Found possible FQDN 'test.sos.p=
olice' in position 3=3B this doesn't match RFC 2606's suggested ".example" =
or ".example.(com|org|net)".

  Checking boilerplate required by RFC 5378 and the IETF Trust (see
  http://trustee.ietf.org/license-info):
  -------------------------------------------------------------------------=
---

     No issues found here.

  Checking nits according to http://www.ietf.org/id-info/1id-guidelines.txt=
:
  -------------------------------------------------------------------------=
---

     No issues found here.

  Checking nits according to http://www.ietf.org/id-info/checklist :
  -------------------------------------------------------------------------=
---

  =3D=3D There are 9 instances of lines with non-RFC2606-compliant FQDNs in=
 the
     document.


  Miscellaneous warnings:
  -------------------------------------------------------------------------=
---

  =3D=3D The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword=
=2C but
     does not include the phrase in its RFC 2119 key words list.

  =3D=3D The document seems to lack a disclaimer for pre-RFC5378 work=2C bu=
t was
     first submitted before 10 November 2008.  Should you add the disclaime=
r?
     (See the Legal Provisions document at
     http://trustee.ietf.org/license-info for more information.) -- however=
=2C
     there's a paragraph with a matching beginning. Boilerplate error?

     IETF Trust Legal Provisions of 28-dec-2009=2C Section 6.c(iii):
     "This document may contain material from IETF Documents or IETF
      Contributions published or made publicly available before November
      10=2C 2008.  The person(s) controlling the copyright in some of this
      material may not have granted the IETF Trust the right to allow
      modifications of such material outside the IETF Standards Process.
      Without obtaining an adequate license from the person(s)
      controlling the copyright in such materials=2C this document may not
      be modified outside the IETF Standards Process=2C and derivative
      works of it may not be created outside the IETF Standards Process=2C
      except to format it for publication as an RFC or to translate it
      into languages other than English."    =20

     ... text found in draft:
     "Code Components extracted from this document must include Simplified =
BSD
......^
      License text as described in Section 4.e of the Trust Legal
      Provisions and are provided without warranty as described in the
      Simplified BSD License."


  -- The document date (March 28=2C 2011) is 26 days in the past.  Is this
     intentional?


  Checking references for intended status: Best Current Practice
  -------------------------------------------------------------------------=
---

     (See RFCs 3967 and 4897 for information about using normative referenc=
es
     to lower-maturity documents in RFCs)

  =3D=3D Unused Reference: 'RFC3841' is defined on line 999=2C but no expli=
cit
     reference was found in the text
     '[RFC3841]  Rosenberg=2C J.=2C Schulzrinne=2C H.=2C and P. Kyzivat=2C =
"Caller P...'

  ** Downref: Normative reference to an Experimental draft:
     draft-ietf-mmusic-media-loopback (ref. 'I-D.ietf-mmusic-media-loopback=
')

  -- Possible downref: Normative reference to a draft: ref.
     'I-D.ietf-sipcore-location-conveyance'=20

  -- Possible downref: Non-RFC (?) normative reference: ref. 'LLDP-MED'


     Summary: 1 error (**)=2C 4 warnings (=3D=3D)=2C 3 comments (--).=20
=20
Is the document class appropriate?

Probably. =20

However=2C a number of the recommendations made would appear to assume an a=
ll-IP NG911
"NENA i3" architecture=2C as opposed to the "NENA i2" transitional architec=
ture.  In those=20
cases=2C the recommendations would represent "Best Future Practice" rather =
than=20
"Best Current Practice".

In a number of cases normative language appears to be used in ways differen=
t from=20
those described in RFC 2119.  In some cases=2C the term "SHOULD" is used in
situations where statutes or regulations may mandate behavior.  =20

It is my assumption that these issues should be fixed by clarifying individ=
ual
requirements=2C rather than changing the document status.

Is the problem well stated?

Yes.  =20

Is the problem really a problem?

Yes.  There is a need to provide guidance on how to use IETF standards for =
emergency calling.  =20

Does the document consider existing solutions?
=20
There are instances in the document where it is unclear whether the recomme=
ndations refer
to Best Future Practice or Best Current Practice.  In general=2C the transi=
tion to
"all-IP" emergency services will take time so that the capabilities of devi=
ces=2C applications=2C
networks=2C service providers and PSAPs will not all be upgraded at once. =
=20
As a result=2C behavior during the transition needs to considered.
See detailed comments for examples.
=20
Does the solution break existing technology?
=20
There are instances in the document where the recommended behavior will be =
sub-optimal
during the transition.  This makes me uncomfortable because emergency servi=
ces are literally
a matter of life and death. =20

Since SIP has mechanisms to determine the capabilities of other parties=2C =
I'd suggest
that the document describe the adaptation or negotiation process rather tha=
n just
assuming that all elements support "all-IP" emergency services.=20
=20
Does the solution preclude future activity?

No.
=20
Is the solution sufficiently configurable?
=20
There are places where behavior should be configurable or negotiated
to allow for better behavior in a transitional environment.

There are also places where behavior will be prescribed by local statues or=
=20
regulations=2C so that configuration and/or negotiation is a practical requ=
irement.
=20
Can performance be measured? How?

Performance can be measured via metrics such as call failure rates
(which should be REALLY low for emergency calls!)=2C media metrics (latency=
=2C jitter)=2C=20
etc. =20
=20
Does the solution scale well?

There are instances where unnecessary load could be generated
(e.g. use of a Service URN when the service provider doesn't support it). =
=20
=20
Is Security Management discussed?=20
=20
This document relies on RFC 5069 and draft-ietf-geopriv-arch for security c=
onsiderations
in emergency calling=2C so the Security Considerations (Section 16) is skim=
py=2C though=20
security (TLS) is discussed in Secton 9.1.  This is probably ok.=20

-----------------------------------------------

Detailed comments:
http://www.drizzle.com/~aboba/ops-dir/draft-ietf-ecrit-phonebcp 		 	   		  =

--_065705d6-0777-432c-bdeb-4b91ceec5457_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Tahoma
}
--></style>
</head>
<body class=3D'hmmessage'>
I reviewed the document draft-ietf-ecrit-phonebcp in general<br>and for its=
 operational impact.&nbsp=3B <br>&nbsp=3B<br>Operations directorate reviews=
 are solicited primarily to help the area<br>directors improve their effici=
ency=2C particularly when preparing for IESG<br>telechats=2C and allowing t=
hem to focus on documents requiring their attention<br>and spend less time =
on the trouble-free ones.<br><br>Improving the documents is important=2C bu=
t clearly a secondary purpose.<br>A third purpose is to broaden the OpsDir =
reviewers' exposure to work going<br>on in other parts of the IETF.<br>&nbs=
p=3B<br>Reviews from OpsDir members do not in and of themselves cause the I=
ESG to<br>raise issue with a document. The reviews may=2C however=2C convin=
ce individual<br>IESG members to raise concern over a particular document r=
equiring further<br>discussion. The reviews=2C particularly those conducted=
 in last call and<br>earlier=2C may also help the document editors improve =
their documents.<br><br> The views represented here are those of the review=
er and do not represent the<br>opinion of any other entity=2C including the=
 Operations Directorate. <br><br>------------------------------------------=
------<br>Review Summary: <br>Intended status:&nbsp=3B Best Current Practic=
e<br>&nbsp=3B<br>&nbsp=3B&nbsp=3B This memo describes best current practice=
 for how devices=2C<br>&nbsp=3B&nbsp=3B networks=2C service providers and P=
ublic Safety Answering<br>&nbsp=3B&nbsp=3B Points (PSAPs) should use IETF s=
tandards for emergency calling<br>&nbsp=3B&nbsp=3B over IP networks. <br>&n=
bsp=3B<br>Is the document readable?<br><br>In general the document is reaso=
nably well organized.&nbsp=3B However=2C there are some requirements<br>tha=
t do not seem easily translated into specific implementation or deployment =
guidance. <br>See detailed comments for examples.<br>&nbsp=3B<br>Does it co=
ntain nits?<br><br>Maybe.<br><br>idnits 2.12.09 <br><br>tmp/draft-ietf-ecri=
t-phonebcp-17.txt:<br>tmp/draft-ietf-ecrit-phonebcp-17.txt(1142): Found pos=
sible FQDN 'test.sos.ambulance' in position 3=3B this doesn't match RFC 260=
6's suggested ".example" or ".example.(com|org|net)".<br>tmp/draft-ietf-ecr=
it-phonebcp-17.txt(1143): Found possible FQDN 'test.sos.animal' in position=
 3=3B this doesn't match RFC 2606's suggested ".example" or ".example.(com|=
org|net)".<br>tmp/draft-ietf-ecrit-phonebcp-17.txt(1144): Found possible FQ=
DN 'test.sos.fire' in position 3=3B this doesn't match RFC 2606's suggested=
 ".example" or ".example.(com|org|net)".<br>tmp/draft-ietf-ecrit-phonebcp-1=
7.txt(1145): Found possible FQDN 'test.sos.gas' in position 3=3B this doesn=
't match RFC 2606's suggested ".example" or ".example.(com|org|net)".<br>tm=
p/draft-ietf-ecrit-phonebcp-17.txt(1146): Found possible FQDN 'test.sos.mar=
ine' in position 3=3B this doesn't match RFC 2606's suggested ".example" or=
 ".example.(com|org|net)".<br>tmp/draft-ietf-ecrit-phonebcp-17.txt(1147): F=
ound possible FQDN 'test.sos.mountain' in position 3=3B this doesn't match =
RFC 2606's suggested ".example" or ".example.(com|org|net)".<br>tmp/draft-i=
etf-ecrit-phonebcp-17.txt(1148): Found possible FQDN 'test.sos.physician' i=
n position 3=3B this doesn't match RFC 2606's suggested ".example" or ".exa=
mple.(com|org|net)".<br>tmp/draft-ietf-ecrit-phonebcp-17.txt(1149): Found p=
ossible FQDN 'test.sos.poison' in position 3=3B this doesn't match RFC 2606=
's suggested ".example" or ".example.(com|org|net)".<br>tmp/draft-ietf-ecri=
t-phonebcp-17.txt(1150): Found possible FQDN 'test.sos.police' in position =
3=3B this doesn't match RFC 2606's suggested ".example" or ".example.(com|o=
rg|net)".<br><br>&nbsp=3B Checking boilerplate required by RFC 5378 and the=
 IETF Trust (see<br>&nbsp=3B http://trustee.ietf.org/license-info):<br>&nbs=
p=3B ----------------------------------------------------------------------=
------<br><br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B No issues found here.<br><br=
>&nbsp=3B Checking nits according to http://www.ietf.org/id-info/1id-guidel=
ines.txt:<br>&nbsp=3B -----------------------------------------------------=
-----------------------<br><br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B No issues f=
ound here.<br><br>&nbsp=3B Checking nits according to http://www.ietf.org/i=
d-info/checklist :<br>&nbsp=3B --------------------------------------------=
--------------------------------<br><br>&nbsp=3B =3D=3D There are 9 instanc=
es of lines with non-RFC2606-compliant FQDNs in the<br>&nbsp=3B&nbsp=3B&nbs=
p=3B&nbsp=3B document.<br><br><br>&nbsp=3B Miscellaneous warnings:<br>&nbsp=
=3B -----------------------------------------------------------------------=
-----<br><br>&nbsp=3B =3D=3D The document seems to use 'NOT RECOMMENDED' as=
 an RFC 2119 keyword=2C but<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B does not in=
clude the phrase in its RFC 2119 key words list.<br><br>&nbsp=3B =3D=3D The=
 document seems to lack a disclaimer for pre-RFC5378 work=2C but was<br>&nb=
sp=3B&nbsp=3B&nbsp=3B&nbsp=3B first submitted before 10 November 2008.&nbsp=
=3B Should you add the disclaimer?<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B (See=
 the Legal Provisions document at<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B http:=
//trustee.ietf.org/license-info for more information.) -- however=2C<br>&nb=
sp=3B&nbsp=3B&nbsp=3B&nbsp=3B there's a paragraph with a matching beginning=
. Boilerplate error?<br><br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B IETF Trust Leg=
al Provisions of 28-dec-2009=2C Section 6.c(iii):<br>&nbsp=3B&nbsp=3B&nbsp=
=3B&nbsp=3B "This document may contain material from IETF Documents or IETF=
<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B Contributions published or mad=
e publicly available before November<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nb=
sp=3B 10=2C 2008.&nbsp=3B The person(s) controlling the copyright in some o=
f this<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B material may not have gr=
anted the IETF Trust the right to allow<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B=
&nbsp=3B modifications of such material outside the IETF Standards Process.=
<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B Without obtaining an adequate =
license from the person(s)<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B cont=
rolling the copyright in such materials=2C this document may not<br>&nbsp=
=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B be modified outside the IETF Standards =
Process=2C and derivative<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B works=
 of it may not be created outside the IETF Standards Process=2C<br>&nbsp=3B=
&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B except to format it for publication as an =
RFC or to translate it<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B into lan=
guages other than English."&nbsp=3B&nbsp=3B&nbsp=3B &nbsp=3B<br><br>&nbsp=
=3B&nbsp=3B&nbsp=3B&nbsp=3B ... text found in draft:<br>&nbsp=3B&nbsp=3B&nb=
sp=3B&nbsp=3B "Code Components extracted from this document must include Si=
mplified BSD<br>......^<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B License=
 text as described in Section 4.e of the Trust Legal<br>&nbsp=3B&nbsp=3B&nb=
sp=3B&nbsp=3B&nbsp=3B Provisions and are provided without warranty as descr=
ibed in the<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B Simplified BSD Lice=
nse."<br><br><br>&nbsp=3B -- The document date (March 28=2C 2011) is 26 day=
s in the past.&nbsp=3B Is this<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B intentio=
nal?<br><br><br>&nbsp=3B Checking references for intended status: Best Curr=
ent Practice<br>&nbsp=3B --------------------------------------------------=
--------------------------<br><br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B (See RFC=
s 3967 and 4897 for information about using normative references<br>&nbsp=
=3B&nbsp=3B&nbsp=3B&nbsp=3B to lower-maturity documents in RFCs)<br><br>&nb=
sp=3B =3D=3D Unused Reference: 'RFC3841' is defined on line 999=2C but no e=
xplicit<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B reference was found in the text=
<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B '[RFC3841]&nbsp=3B Rosenberg=2C J.=2C =
Schulzrinne=2C H.=2C and P. Kyzivat=2C "Caller P...'<br><br>&nbsp=3B ** Dow=
nref: Normative reference to an Experimental draft:<br>&nbsp=3B&nbsp=3B&nbs=
p=3B&nbsp=3B draft-ietf-mmusic-media-loopback (ref. 'I-D.ietf-mmusic-media-=
loopback')<br><br>&nbsp=3B -- Possible downref: Normative reference to a dr=
aft: ref.<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B 'I-D.ietf-sipcore-location-co=
nveyance' <br><br>&nbsp=3B -- Possible downref: Non-RFC (?) normative refer=
ence: ref. 'LLDP-MED'<br><br><br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B Summary: =
1 error (**)=2C 4 warnings (=3D=3D)=2C 3 comments (--). <br>&nbsp=3B<br>Is =
the document class appropriate?<br><br>Probably. &nbsp=3B<br><br>However=2C=
 a number of the recommendations made would appear to assume an all-IP NG91=
1<br>"NENA i3" architecture=2C as opposed to the "NENA i2" transitional arc=
hitecture.&nbsp=3B In those <br>cases=2C the recommendations would represen=
t "Best Future Practice" rather than <br>"Best Current Practice".<br><br>In=
 a number of cases normative language appears to be used in ways different =
from <br>those described in RFC 2119.&nbsp=3B In some cases=2C the term "SH=
OULD" is used in<br>situations where statutes or regulations may mandate be=
havior.&nbsp=3B &nbsp=3B<br><br>It is my assumption that these issues shoul=
d be fixed by clarifying individual<br>requirements=2C rather than changing=
 the document status.<br><br>Is the problem well stated?<br><br>Yes.&nbsp=
=3B &nbsp=3B<br><br>Is the problem really a problem?<br><br>Yes.&nbsp=3B Th=
ere is a need to provide guidance on how to use IETF standards for emergenc=
y calling.&nbsp=3B &nbsp=3B<br><br>Does the document consider existing solu=
tions?<br>&nbsp=3B<br>There are instances in the document where it is uncle=
ar whether the recommendations refer<br>to Best Future Practice or Best Cur=
rent Practice.&nbsp=3B In general=2C the transition to<br>"all-IP" emergenc=
y services will take time so that the capabilities of devices=2C applicatio=
ns=2C<br>networks=2C service providers and PSAPs will not all be upgraded a=
t once. &nbsp=3B<br>As a result=2C behavior during the transition needs to =
considered.<br>See detailed comments for examples.<br>&nbsp=3B<br>Does the =
solution break existing technology?<br>&nbsp=3B<br>There are instances in t=
he document where the recommended behavior will be sub-optimal<br>during th=
e transition.&nbsp=3B This makes me uncomfortable because emergency service=
s are literally<br>a matter of life and death. &nbsp=3B<br><br>Since SIP ha=
s mechanisms to determine the capabilities of other parties=2C I'd suggest<=
br>that the document describe the adaptation or negotiation process rather =
than just<br>assuming that all elements support "all-IP" emergency services=
. <br>&nbsp=3B<br>Does the solution preclude future activity?<br><br>No.<br=
>&nbsp=3B<br>Is the solution sufficiently configurable?<br>&nbsp=3B<br>Ther=
e are places where behavior should be configurable or negotiated<br>to allo=
w for better behavior in a transitional environment.<br><br>There are also =
places where behavior will be prescribed by local statues or <br>regulation=
s=2C so that configuration and/or negotiation is a practical requirement.<b=
r>&nbsp=3B<br>Can performance be measured? How?<br><br>Performance can be m=
easured via metrics such as call failure rates<br>(which should be REALLY l=
ow for emergency calls!)=2C media metrics (latency=2C jitter)=2C <br>etc. &=
nbsp=3B<br>&nbsp=3B<br>Does the solution scale well?<br><br>There are insta=
nces where unnecessary load could be generated<br>(e.g. use of a Service UR=
N when the service provider doesn't support it). &nbsp=3B<br>&nbsp=3B<br>Is=
 Security Management discussed? <br>&nbsp=3B<br>This document relies on RFC=
 5069 and draft-ietf-geopriv-arch for security considerations<br>in emergen=
cy calling=2C so the Security Considerations (Section 16) is skimpy=2C thou=
gh <br>security (TLS) is discussed in Secton 9.1.&nbsp=3B This is probably =
ok. <br><br>-----------------------------------------------<br><br>Detailed=
 comments:<br>http://www.drizzle.com/~aboba/ops-dir/draft-ietf-ecrit-phoneb=
cp 		 	   		  </body>
</html>=

--_065705d6-0777-432c-bdeb-4b91ceec5457_--

From glen@amsl.com  Sun Apr 24 22:00:52 2011
Return-Path: <glen@amsl.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 02F72E06A4; Sun, 24 Apr 2011 22:00:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.979
X-Spam-Level: 
X-Spam-Status: No, score=-103.979 tagged_above=-999 required=5 tests=[AWL=0.543, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SUBJ_ALL_CAPS=2.077, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id snNCZBtKmafd; Sun, 24 Apr 2011 22:00:51 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [64.170.98.20]) by ietfc.amsl.com (Postfix) with ESMTP id 722F7E0673; Sun, 24 Apr 2011 22:00:51 -0700 (PDT)
Received: by c1a.amsl.com (Postfix, from userid 1000) id 2E5C3E08D1; Sun, 24 Apr 2011 22:00:51 -0700 (PDT)
Date: Sun, 24 Apr 2011 22:00:51 -0700
From: Glen Barney <glen@amsl.com>
To: ietf-announce@ietf.org, ietf@ietf.org
Subject: REMINDER - IETF OUTAGE SCHEDULED FOR TODAY, MONDAY APRIL 25TH
Message-ID: <20110425050051.GC21867@amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.17 (2007-11-01)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 05:00:52 -0000

Dear IETF Community -

For the past two weeks we have been operating out of our backup colocated
datacenter, for the dual purposes of (a) testing and verifying that such 
operation would work as expected, and (b) moving us to upgraded server
hardware and operating software.  The testing was done at the request of
the IETF Leadership, and the upgrades were done as a part of this process,
enabling us to make improvements in the services provided to the community.

I'm pleased to report that, having reached the end of the two-week period,
it appears that everything has gone extremely well.

It is now time to bring things back to our primary data center in Fremont,
and to the now newly-upgraded-and-cloned servers ready to go here, and we
will, as previously announced,  perform that process today, Monday, April 25th.

As before, we will bring the Orlando server down into a standby mode, do
a final controlled synchronization of data from the Orlando server to the 
Fremont server, update the zone files, and then bring the Fremont server 
online.

This procedure will begin at 1PM Pacific, 4PM Eastern, 2000GMT, and is
expected to take approximately 2-3 hours.  IETF Leadership will be kept
constantly apprised of any delays, and AMS (IETF Secretariat) staff will
be working continuously until the process is completed.

Please be prepared for this outage today, and plan accordingly.  Thank you 
all for your patience as we bring this upgrade and test to a close.

Glen
Glen Barney
IT Director
AMS (IETF Secretariat)


From glen@amsl.com  Sun Apr 24 23:30:19 2011
Return-Path: <glen@amsl.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 3C536E06DC; Sun, 24 Apr 2011 23:30:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.153
X-Spam-Level: 
X-Spam-Status: No, score=-105.153 tagged_above=-999 required=5 tests=[AWL=1.446, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JAcBSnFzBcml; Sun, 24 Apr 2011 23:30:18 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [64.170.98.20]) by ietfc.amsl.com (Postfix) with ESMTP id C2BE7E06D6; Sun, 24 Apr 2011 23:30:18 -0700 (PDT)
Received: by c1a.amsl.com (Postfix, from userid 1000) id 7A62CE08D1; Sun, 24 Apr 2011 23:30:18 -0700 (PDT)
Date: Sun, 24 Apr 2011 23:30:18 -0700
From: Glen Barney <glen@amsl.com>
To: ietf-announce@ietf.org, ietf@ietf.org
Subject: Reminder - Contacting the IETF
Message-ID: <20110425063018.GA3039@amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.17 (2007-11-01)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 06:30:19 -0000

Dear IETF Community -

As a follow-up to the outage reminder sent earlier, please be advised and
reminded that you can report technical and/or website problems to the IETF
by sending email to the IETF Secretariat staff at:  ietf-action@ietf.org

Further information about ways to contact the secretariat and report problems
can be seen at:  http://www.ietf.org/secretariat/

All community members should be aware of this contact information, in the
event it is ever required.  As always, if there are any questions, please
let us know.

Glen
Glen Barney
IT Director
AMS (IETF Secretariat)


From hartmans@mit.edu  Mon Apr 25 09:02:54 2011
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 0D9B8E075C; Mon, 25 Apr 2011 09:02:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.698
X-Spam-Level: 
X-Spam-Status: No, score=-102.698 tagged_above=-999 required=5 tests=[AWL=-0.433, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AnCdoMwH5Jxp; Mon, 25 Apr 2011 09:02:53 -0700 (PDT)
Received: from mail.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by ietfc.amsl.com (Postfix) with ESMTP id 7F60EE0665; Mon, 25 Apr 2011 09:02:53 -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 7480920378; Mon, 25 Apr 2011 11:59:15 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id E821C4543; Mon, 25 Apr 2011 12:02:40 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Stephen Kent <kent@bbn.com>
Subject: Re: [secdir] Secdir review of draft-ietf-sidr-res-certs
References: <tslhbbag9m1.fsf@mit.edu> <4D791B26.8020001@vpnc.org> <tsl4o7ag5fw.fsf@mit.edu> <4D79271E.6080707@vpnc.org> <tslzkp2elyf.fsf@mit.edu> <p06240801c9ce424e70b1@[128.89.89.62]>
Date: Mon, 25 Apr 2011 12:02:40 -0400
In-Reply-To: <p06240801c9ce424e70b1@[128.89.89.62]> (Stephen Kent's message of "Fri\, 15 Apr 2011 14\:45\:46 -0400")
Message-ID: <tsl62q2tj33.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-ietf-sidr-res-certs@tools.ietf.org, Sam Hartman <hartmans-ietf@mit.edu>, 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: Mon, 25 Apr 2011 16:02:54 -0000

Steve, thanks for your note.
I realize the certificate resource profile document has been approved,
but I'd still like to understand what is happening here.


I'm having trouble reconciling the new text  you've added to the
document with draft-ietf-sidr-signed-object.

        2- During phase 2 CAs MUST issue certificates under the new profile,
and these certificates MUST co-exist with certificates issued under the old
format. (CAs will continue to issue certificates under the old OID/format as
well.) The old and new certificates MUST be identical, except for the policy
OID and any new extensions, encodings, etc. Relying parties MAY make use of the
old or the new certificate formats when processing signed objects retrieved
from the RPKI repository system. During this phase, a relying party that elects
to process both formats will acquire the same values for all certificate fields
that overlap between the old and new formats. Thus if either certificate format
is verifiable, the relying party accepts the data from that certificate. This
allows CAs to issue certificates under


However, when I look at section 2.1.4 in the signed-object document ,
the signer can only include one certificate.
How does that work during phase 2 when some of the RPs support the new
format and some only support the old format?
Your text above suggests that RPs grab the certificates from the RPKI
repository, but it seems at least for end entity certificates they are
included in the signed object.
What happens for end entity certificates during this form of upgrade?

From sm@resistor.net  Mon Apr 25 10:06:37 2011
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 5AEEBE0774 for <ietf@ietfc.amsl.com>; Mon, 25 Apr 2011 10:06:37 -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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mCQb8coPguFi for <ietf@ietfc.amsl.com>; Mon, 25 Apr 2011 10:06:35 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfc.amsl.com (Postfix) with ESMTP id 65BEFE0767 for <ietf@ietf.org>; Mon, 25 Apr 2011 10:06:34 -0700 (PDT)
Received: from subman.resistor.net (IDENT:sm@localhost [127.0.0.1]) by mx.elandsys.com (8.14.4/8.14.5.Beta0) with ESMTP id p3PH6NF5004692;  Mon, 25 Apr 2011 10:06:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1303751192; bh=jfJWXrKn8fppC4tN9W7UK4aCdvkPha7jDB58hmLGN6E=; h=Message-Id:X-Mailer:Date:To:From:Subject:Cc:In-Reply-To: References:Mime-Version:Content-Type; b=mygy/QV7eh6m5ANkEAYDer052/VK9XxPFggZBmVO1y7Cf4ejruVrRI9gdWYOuB2ip SQsB4m1NKo+M26aE/VTQVzHliLt2D9K0J31vYjzRg/Z4p4TkBlTDMkvURWqFUi9M9O i6HFtKhXI2fBbiZ18oKN7rwep5DIzBRQixBjTczg=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1303751192; bh=jfJWXrKn8fppC4tN9W7UK4aCdvkPha7jDB58hmLGN6E=; h=Message-Id:X-Mailer:Date:To:From:Subject:Cc:In-Reply-To: References:Mime-Version:Content-Type; b=zk/KD8nK/AQpY+v1lSjPH3awLENndT666zNbUCsvqAKmvd2+oddpbv8SFmVNu1IWu dTYKoPv0IydO39u/il08B4GyT+w0VM8U1x704IjJfFHb9yowluN0+wl7FNBY5SXB1G uf3fgNuWAqLcXNgj55U7ODGxt2wcLIxfMxncc0x0=
Message-Id: <6.2.5.6.2.20110425064026.03e7b6c8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 25 Apr 2011 07:31:28 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-ietf-mif-current-practices-09.txt> (Current Practices for Multiple Interface Hosts) to Informational RFC
In-Reply-To: <20110328163814.1159.77824.idtracker@localhost>
References: <20110328163814.1159.77824.idtracker@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: Margaret Wasserman <mrw@painless-security.com>, Pierrick Seite <pierrick.seite@orange-ftgroup.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, 25 Apr 2011 17:06:37 -0000

At 09:38 28-03-2011, The IESG wrote:
>The IESG has received a request from the Multiple Interfaces WG (mif) to
>consider the following document:
>- 'Current Practices for Multiple Interface Hosts'
>   <draft-ietf-mif-current-practices-09.txt> as an 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 2011-04-11. Exceptionally, comments may be

I missed the Last Call deadline.  This I-D is worth reading if the 
person is interested in multiple-interface solutions implemented in 
some widely used operating systems.

In Section 2.3.1:

   "On hosts with per-interface DNS server lists, different mechanisms
    are used to determine which DNS server is contacted for a given
    query.  In most cases, the first DNS server listed on the "primary"
    interface is queried first, with back off to other servers if an
    answer is not received."

This can result in the application trying to connect to the wrong 
destination node  (Section 4.1 of draft-ietf-mif-problem-statement-13).

In Section 3.1.3:

   "Depending on the network configuration, applications in reasearch In
    Motion (RIM) BlackBerry devices [BLACKBERRY] can use can use direct
    TCP/IP connectivity or different application proxys to establish
    connections over the wireless network."

There is a typo for "Research".  See also "can use".

In Section 3.2.1.3:

   "Windows uses a host-wide "effective" server list for an actual query,
    where the effective server list may be different for different names.
    In the list of DNS server addresses, the first server is considered
    the "primary" server, with all other servers being secondary."

I suggest using "preferred" and avoid "primary" or "secondary" when 
discussing DNS servers in this context.

In Section 3.2.1.3:

   "The Internet Systems Consortium (ISC) DHCP Client [ISCDHCP] and its
    derivative for OpenBSD [OPENBSDDHCLIENT] can be configured with
    specific instructions for each interface.  However, each time new
    configuration data is received by the host from a DHCP server,
    regardless of which interface it is received on, the DHCP client
    rewrites the global configuration data, such as the default routes
    and the DNS server list (in /etc/resolv.conf) with the most recent
    information received.  Therefore, the last configured interface
    always become the primary one.  The ISC DHCPv6 client behaves
    similarly.:

That rewrite can be overridden for OpenBSD dhclient ( 
http://www.openbsd.org/faq/faq6.html#DHCPclient ).

Regards,
-sm


From glen@amsl.com  Mon Apr 25 15:21:42 2011
Return-Path: <glen@amsl.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 9B2F2E0697; Mon, 25 Apr 2011 15:21:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.299
X-Spam-Level: 
X-Spam-Status: No, score=-105.299 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BZokMeti5l6B; Mon, 25 Apr 2011 15:21:41 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [64.170.98.20]) by ietfa.amsl.com (Postfix) with ESMTP id A5C5CE068C; Mon, 25 Apr 2011 15:21:41 -0700 (PDT)
Received: by c1a.amsl.com (Postfix, from userid 1000) id 9F4C4E08A4; Mon, 25 Apr 2011 15:21:41 -0700 (PDT)
Date: Mon, 25 Apr 2011 15:21:41 -0700
From: Glen Barney <glen@amsl.com>
To: ietf-announce@ietf.org, ietf@ietf.org
Subject: We are back online!
Message-ID: <20110425222141.GA5951@amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.17 (2007-11-01)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 22:21:42 -0000

Dear IETF Membership -

Our failover/failback/upgrade procedures have all been completed, and we
are now running on our newly-upgraded primary production servers once again.

Thank you all for your patience and support during this time.

Regards,

Glen
Glen Barney
IT Director
AMS (IETF Secretariat)

From ron.even.tlv@gmail.com  Tue Apr 26 01:23:17 2011
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 BC12EE0709; Tue, 26 Apr 2011 01:23:17 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SuRFIOQ6ve0c; Tue, 26 Apr 2011 01:23:16 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 4AD26E06E4; Tue, 26 Apr 2011 01:23:16 -0700 (PDT)
Received: by wyb29 with SMTP id 29so293290wyb.31 for <multiple recipients>; Tue, 26 Apr 2011 01:23:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:to:cc:subject:date:message-id:mime-version :content-type:x-mailer:thread-index:content-language; bh=s7xE8qG0SERgZzVfXX6MTDEN31ZdqGRkDGpJrYvTCoU=; b=aXL0bFzsx6iol7FNZuylM8kf9Rj32SBPJnjez1OsNISEsvuASglWzoqepD1u21+VD+ TOQGmRIyc/HAWjvTpiNwvOJIfY4hK4KVl/C3lvhR1EgZTk6ZEzWFIwG4Co65XvxwVy6A H3dvztUUMHd/fOF+CWosSV+pT2M4UBfQB5+kc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:subject:date:message-id:mime-version:content-type :x-mailer:thread-index:content-language; b=i2LhA+yXnZamIj/bWL/Tlfy5/Cz7LLAjkRA7CwU2WvGs+Fw/JvdS2QiVDvILIkSMvj dd9EzHiZ4mE+iD+aFwfRsEYYsXA5KcMOQg3i32rtoVpnkf7gMCuj5qMVAFT41ah3Hyzo TGZTk6kb/mdahvzrlupcv6Ej3+Ycs5gVcufDA=
Received: by 10.216.62.137 with SMTP id y9mr4195330wec.107.1303806195394; Tue, 26 Apr 2011 01:23:15 -0700 (PDT)
Received: from windows8d787f9 (bzq-79-176-19-159.red.bezeqint.net [79.176.19.159]) by mx.google.com with ESMTPS id ed10sm3682831wbb.49.2011.04.26.01.23.11 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 26 Apr 2011 01:23:13 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-ietf-grow-geomrt.all@tools.ietf.org>
Subject: Gen-ART LC review of draft-ietf-grow-geomrt-01
Date: Tue, 26 Apr 2011 11:22:13 +0300
Message-ID: <4db680f1.cac3e30a.1c28.2085@mx.google.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00E1_01CC0404.3363CAA0"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcwD6wbOwmqW7fASSRiM+pToVKF8Pg==
Content-Language: en-us
Cc: gen-art@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, 26 Apr 2011 08:23:17 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_00E1_01CC0404.3363CAA0
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-grow-geomrt-01

Reviewer: Roni Even

Review Date:2011-4-26

IETF LC End Date: 2011-4-29

IESG Telechat date:

 

Summary: This draft is ready for publication as an Informational RFC.

 

Major issues:

 

 

Minor issues:

This is more out of curiosity

1.       Why not include it in draft-ietf-grow-mrt-14

2.  Why is it an Informational RFC and not standard track like the mrt
draft.

 

 

 

Nits/editorial comments:

 

1.       Need to expand MRT when first mentioned.

 

 


------=_NextPart_000_00E1_01CC0404.3363CAA0
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;}
span.h11
	{mso-style-name:h11;
	font-family:"Courier New";
	font-weight:bold;}
.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:901602645;
	mso-list-type:hybrid;
	mso-list-template-ids:986983972 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;}
@list l1
	{mso-list-id:1090463919;
	mso-list-type:hybrid;
	mso-list-template-ids:-1044579784 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1: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-=
grow-geomrt-01<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:2011&#8211;4&#8211;26<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: 2011&#8211;4&#8211;29<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 </span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Information=
al </span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>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"'><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"'>This is =
more out of curiosity<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 =
lfo1'><![if !supportLists]><span class=3Dh11><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";font-weight:=
normal'><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></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Why not =
include it in </span><span class=3Dh11><span lang=3DEN =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";font-weight:=
normal'>draft-ietf-grow-mrt-14</span></span><span class=3Dh11><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";font-weight:=
normal'><o:p></o:p></span></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 =
lfo1'><![if !supportLists]><span style=3D'mso-list:Ignore'>2.<span =
style=3D'font:7.0pt "Times New Roman"'>&nbsp; =
</span></span><![endif]><span dir=3DLTR></span><span class=3Dh11><span =
lang=3DEN =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";font-weight:=
normal'>Why is it an Informational RFC and not standard track like the =
mrt draft.</span></span><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"'><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 =
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"'>Need to =
expand MRT when first mentioned.<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=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_00E1_01CC0404.3363CAA0--


From pekkas@netcore.fi  Tue Apr 26 02:51:18 2011
Return-Path: <pekkas@netcore.fi>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F001E06B2; Tue, 26 Apr 2011 02:51: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=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6GC5sDMnIG2H; Tue, 26 Apr 2011 02:51:17 -0700 (PDT)
Received: from netcore.fi (eunet-gw.ipv6.netcore.fi [IPv6:2001:670:86:3001::1]) by ietfa.amsl.com (Postfix) with ESMTP id BA583E06B1; Tue, 26 Apr 2011 02:51:16 -0700 (PDT)
Received: from netcore.fi (localhost [127.0.0.1]) by netcore.fi (8.13.8/8.13.8) with ESMTP id p3Q9p6pl023739 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 26 Apr 2011 12:51:06 +0300
Received: from localhost (pekkas@localhost) by netcore.fi (8.13.8/8.13.8/Submit) with ESMTP id p3Q9p5i1023735; Tue, 26 Apr 2011 12:51:06 +0300
Date: Tue, 26 Apr 2011 12:51:05 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03.txt> (IPv6 AAAA DNS Whitelisting Implications) to Informational RFC
In-Reply-To: <20110415205113.13704.48681.idtracker@ietfc.amsl.com>
Message-ID: <alpine.LRH.2.02.1104261249510.23669@netcore.fi>
References: <20110415205113.13704.48681.idtracker@ietfc.amsl.com>
User-Agent: Alpine 2.02 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Virus-Scanned: clamav-milter 0.97 at otso.netcore.fi
X-Virus-Status: Clean
Cc: v6ops@ietf.org, v6ops-chairs@tools.ietf.org, draft-ietf-v6ops-v6-aaaa-whitelisting-implications@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, 26 Apr 2011 09:51:18 -0000

On Fri, 15 Apr 2011, The IESG wrote:
> The IESG has received a request from the IPv6 Operations WG (v6ops) to
> consider the following document:
> - 'IPv6 AAAA DNS Whitelisting Implications'
>  <draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03.txt> as an
> Informational RFC

This is an ops-dir review of
draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03.

The document is readable and could be published as-is.  I share some of the
concerns already expressed in the document, but I think the doc strikes a
reasonable balance between the concerns and practical points.

One bigger comment:
-------------------

Section 6 on deployment scenarios seems too black and white: either it is
done ad-hoc or (completely) universally.  The latter is unfeasible.

The document should cover a middle ground which is already discussed in
[NW-Article-DNS-WL], i.e., one or more whitelisting information providers
would be used by multiple content networks.  This has many benefits compared
to completely ad-hoc model, and is feasible compared to universal model.

The "universal deployment model" proposition has created ripples throughout
the document (one such place is S 7.3.7), and I think the document might
have been clearer if that was taken out completely -- or at least, issues
related to each deployment model would be more clearly separated.

......


8.3.1. Solving Current End User IPv6 Impairments
...
    One challenge with this option is the potential difficulty of
    motivating members of the Internet community to work collectively
    towards this goal, sharing the labor, time, and costs related to such
    an effort.  Of course, since just such a community effort is now
    underway for IPv6, it is possible that this would call for only a
    moderate amount of additional work.

... I would observe that ad-hoc whitelisting is already requiring a lot of
work from each of whitelisting providers.  Would this require more than
that?  If the alternative is to do nothing (no whitelisting, no user
impairment notification) that is clear the winner from the selfish POV. But
if the choice is between whitelisting and alerting, I don't see much
difference between the two.  Both could benefit from joint activities, but
both can also be operated in an ad-hoc fashion.


editorial:
----------

7.3.7. Additional Implications If Deployed On An Ad Hoc Basis

    Additional implications, should this be deployed on an ad hoc basis,
    could include scalability problems relating to operational processes,
    monitoring, and ACL updates.

... this could be read to imply that S 7.3.1-6 would be applicable to
universal deployment.  This is not what is meant.  Maybe clarify somewhat
like as follows:

    Previous subsections described implications that apply to both ad-hoc and
    universal deployment models.  Some additional implications are specific
    to ad-hoc deployment models, namely ...

S 7.5

    governmental, and/or cultural conflicts, given the new control point
    which has be established with DNS whitelisting.  For example, in one

s/be/been/

    [IPv6 Brokenness]
               Anderson, T., "Measuring and Combating IPv6 Brokenness",
               Reseaux IP Europeens (RIPE) 61st Meeting, November 2011,
               <http://ripe61.ripe.net/presentations/162-ripe61.pdf>.


s/2011/2010/

From john.elwell@siemens-enterprise.com  Tue Apr 26 06:37:42 2011
Return-Path: <john.elwell@siemens-enterprise.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 ACD40E07A1; Tue, 26 Apr 2011 06:37:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.591
X-Spam-Level: 
X-Spam-Status: No, score=-104.591 tagged_above=-999 required=5 tests=[AWL=2.008, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 59ydLdL9i9eF; Tue, 26 Apr 2011 06:37:42 -0700 (PDT)
Received: from mail182.messagelabs.com (mail182.messagelabs.com [85.158.139.83]) by ietfa.amsl.com (Postfix) with SMTP id 7D09EE0793; Tue, 26 Apr 2011 06:37:41 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: john.elwell@siemens-enterprise.com
X-Msg-Ref: server-10.tower-182.messagelabs.com!1303825059!5622519!1
X-StarScan-Version: 6.2.9; banners=-,-,-
X-Originating-IP: [62.134.46.10]
Received: (qmail 28558 invoked from network); 26 Apr 2011 13:37:39 -0000
Received: from unknown (HELO senmx12-mx) (62.134.46.10) by server-10.tower-182.messagelabs.com with SMTP; 26 Apr 2011 13:37:39 -0000
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx12-mx (Server) with ESMTP id 9054423F03E2; Tue, 26 Apr 2011 15:37:39 +0200 (CEST)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Tue, 26 Apr 2011 15:37:39 +0200
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: "ietf@ietf.org" <ietf@ietf.org>, "sipping@ietf.org" <sipping@ietf.org>
Date: Tue, 26 Apr 2011 15:37:37 +0200
Subject: Late comment on draft-ietf-sippping-sip-offeranswer-14
Thread-Topic: Late comment on draft-ietf-sippping-sip-offeranswer-14
Thread-Index: AcwEFxtQP2WQ8OP3Tnm7SkCj3hScBA==
Message-ID: <A444A0F8084434499206E78C106220CA0875F83F02@MCHP058A.global-ad.net>
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, 26 Apr 2011 13:37:42 -0000

I know last call finished already, but the following has just been brought =
to my attention:

In section 5.2.5
"Changing the o-line,
      except version number value, during the session is an error case.
      The behavior when receiving such a non-compliant offer/answer SDP
      body is implementation dependent. "
I would content this is NOT an error situation, or at least not an error in=
 the case where a NEW session is being signalled.

Consider a 3PCC situation along the lines described in section 7 of RFC 372=
5. The controlling B2BUA converts a session between UA A and UA B into a se=
ssion between UA B and UA C. Prior to this conversion, UA B has received UA=
 A's SDP (SDP A). As a result of the conversion, UA B receives UA C's SDP (=
SDP C).

SDP C is likely to be completely different from SDP A. Therefore just a cha=
nge of version number in the o-line is insufficient and would probably viol=
ate RFC 3264. In particular, if SDP A has 2 m-lines and SDP C has only one =
m-line, the change from 2 m-lines to 1 m-line is not permitted according to=
 RFC 3264. So although RFC 3725 talks about the controlling B2BUA adjusting=
 version numbers, that is insufficient in some cases.

The text of 5.2.5 then goes on to say:
"The behavior when receiving such a non-compliant offer/answer SDP
      body is implementation dependent."
It is not clear what this fails to comply with. I can find nothing in RFC 3=
264 that stops you sending a new o-line if there is a new session. Yes, it =
would be non-compliant if only modifying an existing session, but how does =
the recipient know whether or not it is a new session, and therefore whethe=
r or not it is valid?

It then goes on to recommend use of Replaces in this situation (i.e. change=
 of session):
"If a UA needs to negotiate a
      'new' SDP session, it should use the INVITE/Replaces method."
But Replaces is not feasible if the UA concerned does not support it (and h=
ence "should", presumably). So there will still be cases where a controllin=
g B2BUA is forced to change the o-line (not just the version) in order to c=
omply with RFC 3264.

So there needs to be a mechanism for changing to a 'new' session without re=
lying on Replaces. As far as I can see, there is no standards track RFC tha=
t forbids changing the o-line to achieve this, so this new Informational dr=
aft should not attempt to make that change, and in particular should not do=
 so without proposing an alternative solution.

A simple fix would be to delete the entire bullet beginning "In the o-line,=
 only the version number may change".

John=

From lear@cisco.com  Tue Apr 26 08:30:31 2011
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 63908E07F0; Tue, 26 Apr 2011 08:30:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.922
X-Spam-Level: 
X-Spam-Status: No, score=-109.922 tagged_above=-999 required=5 tests=[AWL=0.677, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vmSX1ShpLHJW; Tue, 26 Apr 2011 08:30:30 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id 3D368E07ED; Tue, 26 Apr 2011 08:30:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=lear@cisco.com; l=1134; q=dns/txt; s=iport; t=1303831830; x=1305041430; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=jGNjLXvslFPm939pelaM6rKAt82DtumpL8fFLNemCC0=; b=jS0flB+Z/zP7BjqzoegUKc2dTgGGTk27mUzfwBN4rYYTQw/31JRRvAHL a2rCZzd34x0v/fnZ2vf0TsPqpRRKYU3RtUs1ax3YLEsL3jFOMVwuh6S57 BBFPbK7+semmQJqIpnmmXHRfhsiBGAfO7UNG9a7VT1NAmBLM+j/FFHUvI g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Au8DAOLjtk2Q/khMgWdsb2JhbACEUqB2FAEBFiYliHCfWYtgkTmBKYNQfQSOQY4i
X-IronPort-AV: E=Sophos;i="4.64,268,1301875200"; d="scan'208";a="27259342"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-2.cisco.com with ESMTP; 26 Apr 2011 15:30:29 +0000
Received: from ams3-vpn-dhcp8029.cisco.com (ams3-vpn-dhcp8029.cisco.com [10.61.95.92]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p3QFUTbG028517; Tue, 26 Apr 2011 15:30:29 GMT
Message-ID: <4DB6E4FB.9040909@cisco.com>
Date: Tue, 26 Apr 2011 17:30:03 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.15) Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: Elwyn Davies <elwynd@dial.pipex.com>
Subject: Re: Gen-art review of draft-lear-iana-timezone-database-03
References: <1303475830.21284.19230.camel@mightyatom.folly.org.uk>
In-Reply-To: <1303475830.21284.19230.camel@mightyatom.folly.org.uk>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: draft-lear-iana-timezone-database.all@tools.ietf.org, General Area Review Team <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: Tue, 26 Apr 2011 15:30:31 -0000

Hi Elwyn,

Thank you again for the review.  Please see below.

> Summary:
> Almost ready for the IESG.  This is my second review of the document.  
>
> I suggested in the previous review that it might make life easier, particularly 
> if an appeal was ever entered, if the document didn't use the RFC 5226 Designated 
> Expert mechanism but defined the role separately.  This hasn't happened but the 
> distinction is now clearer.  To make it quite clear I would be inclined to add 
> 'except as regards appeals against decisions of the Designated Expert 
> (see Section 5)' after [RFC5226] in the definition of TZ Coordinator in Section 2.

I've adopted your above suggested wording.

> Otherwise there are a couple of editorial nits.   
>
> .
> Nits/Editorial:
> s3: s/policy policy/policy/ (repeated word)

Corrected.
> s8, first para: s/filling/filling the role/ (maybe 'post')

This text changed based on another review.

> s8, last para: s/TZ Coordinators/TZ Coordinator/

Corrected.
> s10: s/Elwin/Elwyn/ (thanks for the ack!)

Corrected and apologies! I hate when that happens to me!

Eliot

From hilarie@purplestreak.com  Mon Apr 25 12:24:03 2011
Return-Path: <hilarie@purplestreak.com>
X-Original-To: ietf@ietfc.amsl.com
Delivered-To: ietf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 8F3A0E0691; Mon, 25 Apr 2011 12:24: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=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3FptqUzqYsS1; Mon, 25 Apr 2011 12:24:03 -0700 (PDT)
Received: from out01.mta.xmission.com (out01.mta.xmission.com [166.70.13.231]) by ietfc.amsl.com (Postfix) with ESMTP id D1360E067C; Mon, 25 Apr 2011 12:24:02 -0700 (PDT)
Received: from mx02.mta.xmission.com ([166.70.13.212]) by out01.mta.xmission.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <hilarie@purplestreak.com>) id 1QERO1-0007y4-WE; Mon, 25 Apr 2011 13:23:58 -0600
Received: from 166-70-57-249.ip.xmission.com ([166.70.57.249] helo=fermat.rhmr.com) by mx02.mta.xmission.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <hilarie@purplestreak.com>) id 1QERO1-0006Ng-1I; Mon, 25 Apr 2011 13:23:57 -0600
Received: from fermat.rhmr.com (localhost [127.0.0.1]) by fermat.rhmr.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id p3PJLkkd020708; Mon, 25 Apr 2011 13:21:46 -0600
Received: (from ho@localhost) by fermat.rhmr.com (8.14.3/8.14.3/Submit) id p3PJLi6R020707; Mon, 25 Apr 2011 13:21:44 -0600
Date: Mon, 25 Apr 2011 13:21:44 -0600
Message-Id: <201104251921.p3PJLi6R020707@fermat.rhmr.com>
X-Authentication-Warning: fermat.rhmr.com: ho set sender to hilarie using -f
From: "Hilarie Orman" <hilarie@purplestreak.com>
To: ietf@ietf.org, secdir@ietf.org, draft-ietf-ippm-tcp-throughput-tm@tools.ietf.org
X-XM-SPF: eid=; ; ; mid=; ; ; hst=mx02.mta.xmission.com; ; ; ip=166.70.57.249; ; ; frm=hilarie@purplestreak.com; ; ; spf=none
X-XM-DomainKey: sender_domain=purplestreak.com; ; ; sender=hilarie@purplestreak.com; ; ; status=error
X-SA-Exim-Connect-IP: 166.70.57.249
X-SA-Exim-Mail-From: hilarie@purplestreak.com
X-Spam-DCC: XMission; sa07 1397; Body=1 Fuz1=1 Fuz2=1 
X-Spam-Combo: ;ietf@ietf.org, secdir@ietf.org, draft-ietf-ippm-tcp-throughput-tm@tools.ietf.org
X-Spam-Relay-Country: 
Subject: Review of draft-ietf-ippm-tcp-throughput-tm-12.txt
X-SA-Exim-Version: 4.2.1 (built Fri, 06 Aug 2010 16:31:04 -0600)
X-SA-Exim-Scanned: Yes (on mx02.mta.xmission.com)
X-Mailman-Approved-At: Tue, 26 Apr 2011 08:53:32 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Hilarie Orman <hilarie@purplestreak.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, 25 Apr 2011 19:24:03 -0000

Security review of draft-ietf-ippm-tcp-throughput-tm-12.txt

Do not be alarmed.  I have reviewed this document as part of the
security directorate's ongoing effort to review all IETF documents
being processed by the IESG.  These comments were written primarily
for the benefit of the security area directors. Document editors and
WG chairs should treat these comments just like any other review
comments.

>From the document Intro:
   This framework recommends a methodology for measuring TCP
   Throughput in order to provide meaningful results with respect to
   user experience.

I had a little bit of trouble understanding the purpose of the
document, having stumbled across these two statements which when
juxtaposed, seem to contradict one another:

 Introduction
...
  Note that the primary focus of this methodology is managed business 
  class IP networks; i.e. those Ethernet terminated services for which 
  organizations are provided an SLA from the network provider.  Because 
  of the SLA, the expectation is that the TCP Throughput should achieve
  the guaranteed bandwidth.  

... 

  2. Scope and Goals
...
     - This methodology is not intended to measure TCP Throughput as part 
     of an SLA

[Remember the New Yorker magazine's "Our Forgetful Authors"?]

It is difficult to frame the security requirements for a measurement
framework, and this document does not try:

  6. Security Considerations

     The security considerations that apply to any active measurement of
     live networks are relevant here as well.  See [RFC4656] and
    [RFC5357].

I am not sure what to infer from this statement.  That the RFCs define
all possible security requirements and considerations?  That their
definitions coincide with what the authors of the current document
recommend?  That the solutions defined by the other RFCs SHOULD be
be part of the framework defined by the current document?  MAY?  It
depends?

It's my recommendation that the security considerations be expanded
to explicitly list the security requirements for the framework.


From pierrick.seite@orange-ftgroup.com  Tue Apr 26 02:56:13 2011
Return-Path: <pierrick.seite@orange-ftgroup.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 3FAB0E06B2 for <ietf@ietfa.amsl.com>; Tue, 26 Apr 2011 02:56:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aBBvI8PP0xQu for <ietf@ietfa.amsl.com>; Tue, 26 Apr 2011 02:56:12 -0700 (PDT)
Received: from p-mail2.rd.francetelecom.com (p-mail2.rd.francetelecom.com [195.101.245.16]) by ietfa.amsl.com (Postfix) with ESMTP id E6663E06B1 for <ietf@ietf.org>; Tue, 26 Apr 2011 02:56:11 -0700 (PDT)
Received: from p-mail2.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id AB46D85800F; Tue, 26 Apr 2011 12:02:42 +0200 (CEST)
Received: from ftrdsmtp1.rd.francetelecom.fr (unknown [10.192.128.46]) by p-mail2.rd.francetelecom.com (Postfix) with ESMTP id 9975B85800D; Tue, 26 Apr 2011 12:02:42 +0200 (CEST)
Received: from ftrdmel0.rd.francetelecom.fr ([10.192.128.56]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 26 Apr 2011 11:55:46 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Last Call: <draft-ietf-mif-current-practices-09.txt> (Current Practices for Multiple Interface Hosts) to Informational RFC
Date: Tue, 26 Apr 2011 11:55:45 +0200
Message-ID: <843DA8228A1BA74CA31FB4E111A5C46201A8EAFB@ftrdmel0.rd.francetelecom.fr>
In-Reply-To: <6.2.5.6.2.20110425064026.03e7b6c8@resistor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Last Call: <draft-ietf-mif-current-practices-09.txt> (Current Practices for Multiple Interface Hosts) to Informational RFC
Thread-Index: AcwDayQTYvLfHY+jTieRitCxn2m9SAAiP+2Q
References: <20110328163814.1159.77824.idtracker@localhost> <6.2.5.6.2.20110425064026.03e7b6c8@resistor.net>
From: <pierrick.seite@orange-ftgroup.com>
To: <sm@resistor.net>, <ietf@ietf.org>
X-OriginalArrivalTime: 26 Apr 2011 09:55:46.0784 (UTC) FILETIME=[1D745E00:01CC03F8]
X-Mailman-Approved-At: Tue, 26 Apr 2011 08:53:32 -0700
Cc: mrw@painless-security.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, 26 Apr 2011 09:56:13 -0000

Thanks for the review. I've modified the draft according to your =
comments. Please see inline for more details.


BR,
Pierrick

> -----Message d'origine-----
> De=A0: SM [mailto:sm@resistor.net]
> Envoy=E9=A0: lundi 25 avril 2011 16:31
> =C0=A0: ietf@ietf.org
> Cc=A0: Margaret Wasserman; SEITE Pierrick RD-RESA-REN
> Objet=A0: Re: Last Call: <draft-ietf-mif-current-practices-09.txt> =
(Current
> Practices for Multiple Interface Hosts) to Informational RFC
>=20
> At 09:38 28-03-2011, The IESG wrote:
> >The IESG has received a request from the Multiple Interfaces WG (mif) =
to
> >consider the following document:
> >- 'Current Practices for Multiple Interface Hosts'
> >   <draft-ietf-mif-current-practices-09.txt> as an 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 2011-04-11. Exceptionally, comments =
may be
>=20
> I missed the Last Call deadline.  This I-D is worth reading if the
> person is interested in multiple-interface solutions implemented in
> some widely used operating systems.
>=20
> In Section 2.3.1:
>=20
>    "On hosts with per-interface DNS server lists, different mechanisms
>     are used to determine which DNS server is contacted for a given
>     query.  In most cases, the first DNS server listed on the =
"primary"
>     interface is queried first, with back off to other servers if an
>     answer is not received."
>=20
> This can result in the application trying to connect to the wrong
> destination node  (Section 4.1 of =
draft-ietf-mif-problem-statement-13).
>=20
> In Section 3.1.3:
>=20
>    "Depending on the network configuration, applications in reasearch =
In
>     Motion (RIM) BlackBerry devices [BLACKBERRY] can use can use =
direct
>     TCP/IP connectivity or different application proxys to establish
>     connections over the wireless network."
>=20
> There is a typo for "Research".  See also "can use".
>=20

Thanks.

> In Section 3.2.1.3:
>=20
>    "Windows uses a host-wide "effective" server list for an actual =
query,
>     where the effective server list may be different for different =
names.
>     In the list of DNS server addresses, the first server is =
considered
>     the "primary" server, with all other servers being secondary."
>=20
> I suggest using "preferred" and avoid "primary" or "secondary" when
> discussing DNS servers in this context.
>=20

I see your point, but the section describes the behaviour of a =
particular OS and "primary" or "secondary" is the terminology used by =
this OS. =20

> In Section 3.2.1.3:
>=20
>    "The Internet Systems Consortium (ISC) DHCP Client [ISCDHCP] and =
its
>     derivative for OpenBSD [OPENBSDDHCLIENT] can be configured with
>     specific instructions for each interface.  However, each time new
>     configuration data is received by the host from a DHCP server,
>     regardless of which interface it is received on, the DHCP client
>     rewrites the global configuration data, such as the default routes
>     and the DNS server list (in /etc/resolv.conf) with the most recent
>     information received.  Therefore, the last configured interface
>     always become the primary one.  The ISC DHCPv6 client behaves
>     similarly.:
>=20
> That rewrite can be overridden for OpenBSD dhclient (
> http://www.openbsd.org/faq/faq6.html#DHCPclient ).
>=20


Good point, I've modified the draft accordingly. Thanks.

> Regards,
> -sm


From sm@resistor.net  Tue Apr 26 11:03:34 2011
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 559EBE0785 for <ietf@ietfa.amsl.com>; Tue, 26 Apr 2011 11:03:34 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YJQHYYfOP68b for <ietf@ietfa.amsl.com>; Tue, 26 Apr 2011 11:03:31 -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 D942BE075F for <ietf@ietf.org>; Tue, 26 Apr 2011 11:03:30 -0700 (PDT)
Received: from subman.resistor.net (IDENT:sm@localhost [127.0.0.1]) by mx.elandsys.com (8.14.4/8.14.5.Beta0) with ESMTP id p3QI3Jh3006003;  Tue, 26 Apr 2011 11:03:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1303841009; bh=xgGSsME3ymYwAEipfwi6i1IfRSfvmI6xItGQcm1Chhw=; h=Message-Id:X-Mailer:Date:To:From:Subject:Cc:In-Reply-To: References:Mime-Version:Content-Type; b=xam99/CuLbMW8YbvZU3MlhFMbkW2ft0wrOVyrrWdO72JQaeR2q7fo6SUT58O959Ej fbu65KA2JcuIs4QyL+XI+3KF+AQyYTYM+zns+/hADS5BPHu02vFiVMBofo3Rlhib2+ 5QP+Zwhh8xBgG+e9TecHhCkcn+cYnHE70EGTDDrE=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1303841009; bh=xgGSsME3ymYwAEipfwi6i1IfRSfvmI6xItGQcm1Chhw=; h=Message-Id:X-Mailer:Date:To:From:Subject:Cc:In-Reply-To: References:Mime-Version:Content-Type; b=ol32Bf7w2BBr3SKB11PFdE+JBZwkFtZyidNvGCOVZFgnSYSAQ6OrnDOP0viR7NQ0M 74pv/cvUGa5DvkDynSvqAwPCmz7xEBlBTRWL/SIWNgBZ7SOMgOPXUPjI5JctiOnLWB Pi2GOJQGPuk3emy9RZZ8NKzK/Edn9sv/vwudV5A4=
Message-Id: <6.2.5.6.2.20110426093245.0385a570@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 26 Apr 2011 09:49:21 -0700
To: <pierrick.seite@orange-ftgroup.com>
From: SM <sm@resistor.net>
Subject: RE: Last Call: <draft-ietf-mif-current-practices-09.txt>  (Current Practices for Multiple Interface Hosts) to Informational RFC
In-Reply-To: <843DA8228A1BA74CA31FB4E111A5C46201A8EAFB@ftrdmel0.rd.franc etelecom.fr>
References: <20110328163814.1159.77824.idtracker@localhost> <6.2.5.6.2.20110425064026.03e7b6c8@resistor.net> <843DA8228A1BA74CA31FB4E111A5C46201A8EAFB@ftrdmel0.rd.francetelecom.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: mrw@painless-security.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: Tue, 26 Apr 2011 18:03:34 -0000

Hi Pierrick,
At 02:55 26-04-2011, pierrick.seite@orange-ftgroup.com wrote:
>I see your point, but the section describes the behaviour of a 
>particular OS and "primary" or "secondary" is the terminology used by this OS.

Thanks for the explanation.  I see the same terminology being used in 
draft-montenegro-mif-multihoming-00.

Regards,
-sm 


From haibin.song@huawei.com  Tue Apr 26 20:45:29 2011
Return-Path: <haibin.song@huawei.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 7B0E4E0685; Tue, 26 Apr 2011 20:45:29 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hmVnWpugOxUo; Tue, 26 Apr 2011 20:45:28 -0700 (PDT)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id 69008E0699; Tue, 26 Apr 2011 20:45:28 -0700 (PDT)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LKA004BML09FM@szxga03-in.huawei.com>; Wed, 27 Apr 2011 11:43:21 +0800 (CST)
Received: from szxeml207-edg.china.huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTP id <0LKA00B52L0807@szxga03-in.huawei.com>; Wed, 27 Apr 2011 11:43:21 +0800 (CST)
Received: from SZXEML404-HUB.china.huawei.com (10.82.67.59) by szxeml207-edg.china.huawei.com (172.24.2.59) with Microsoft SMTP Server (TLS) id 14.1.270.1; Wed, 27 Apr 2011 11:43:20 +0800
Received: from SZXEML505-MBS.china.huawei.com ([169.254.1.24]) by szxeml404-hub.china.huawei.com ([fe80::75b7:3db9:fedc:a56d%13]) with mapi id 14.01.0270.001; Wed, 27 Apr 2011 11:43:20 +0800
Date: Wed, 27 Apr 2011 03:43:19 +0000
From: Songhaibin <haibin.song@huawei.com>
Subject: TSVDIR review of draft-ietf-mif-current-practices-10
X-Originating-IP: [10.138.41.119]
To: "tsv-dir@ietf.org" <tsv-dir@ietf.org>
Message-id: <E33E01DFD5BEA24B9F3F18671078951F10B727@SZXEML505-MBS.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-language: zh-CN
Content-transfer-encoding: 7BIT
Accept-Language: en-US, zh-CN
Thread-topic: TSVDIR review of draft-ietf-mif-current-practices-10
Thread-index: AcwEjT94f5cFrLDDQnmx/e6koQnb/w==
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Mailman-Approved-At: Wed, 27 Apr 2011 08:27:10 -0700
Cc: "tsv-ads@tools.ietf.org" <tsv-ads@tools.ietf.org>, "draft-ietf-mif-current-practices@tools.ietf.org" <draft-ietf-mif-current-practices@tools.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, 27 Apr 2011 03:45:29 -0000

Hi, all,

I've reviewed this document as part of the transport area directorate's ongoing effort to review key IETF documents. These comments were written primarily for the transport area directors, but are copied to the document's authors for their information and to allow them to address any issues raised. The authors should consider this review together with any other last-call comments they receive. Please always CC tsv-dir@ietf.org if you reply to or forward this review.

The document describes how the current practices cope with challenges raised by multiple interfaces. This draft is very good to read. And the content is complete in my opinion. But I also have one main comment and two minor comments.
--------
The main comment:

Section 3.3.  Focus on access network selection
This section describes the current practices about how to select the access network/points, especially how connection manager deal with the list of preferred SSID and how does it select the access point for attachment. I think this is out of the scope of MIF WG, which is aimed to address the problems raised by multiple interfaces, instead of attachment network/point selection for one interface. And the charter explicitly says: " Network discovery and selection on lower layers as defined by RFC 5113 is out of scope."

-------
Two minor comments:

3.1.1 Nokia S60 3rd Edition, Feature Pack 2

Paragraph " When SNAPs are used, it is possibly for the operating system to notify applications when a preferred IAP, leading to the same destination, becomes available...."

When the word "possibly" is used here, I am a little confused. I guess the authors mean the operating system provides the capability to notify the applications, but the applications may/may not use it. Or does it mean the operating system can decide whether to notify the applications?

Section 3.3.1 and 3.3.2

These two sections describe the access network selection for Android/HTC Magic and RIM BlackBerry. But they use the similar method and most of the text are the same. So it is possible to merge these two sections. But my this comment is useless if the main comment is accepted.

By the way, in Section 3.1.3 line 2, delete duplicate "can use".

I hope this feedback will be useful to the authors.

-Haibin

From pierrick.seite@orange-ftgroup.com  Wed Apr 27 01:21:00 2011
Return-Path: <pierrick.seite@orange-ftgroup.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 90631E06C3; Wed, 27 Apr 2011 01:21:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LTwKuiKrxOHB; Wed, 27 Apr 2011 01:20:59 -0700 (PDT)
Received: from r-mail2.rd.francetelecom.com (r-mail2.rd.francetelecom.com [217.108.152.42]) by ietfa.amsl.com (Postfix) with ESMTP id 95719E06AD; Wed, 27 Apr 2011 01:20:59 -0700 (PDT)
Received: from r-mail2.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id C19A2FC40A1; Wed, 27 Apr 2011 10:16:29 +0200 (CEST)
Received: from ftrdsmtp2.rd.francetelecom.fr (unknown [10.192.128.47]) by r-mail2.rd.francetelecom.com (Postfix) with ESMTP id 60C71FC415F; Wed, 27 Apr 2011 09:59:51 +0200 (CEST)
Received: from ftrdmel0.rd.francetelecom.fr ([10.192.128.56]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 27 Apr 2011 09:58:07 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: TSVDIR review of draft-ietf-mif-current-practices-10
Date: Wed, 27 Apr 2011 09:58:06 +0200
Message-ID: <843DA8228A1BA74CA31FB4E111A5C46201A8ECC4@ftrdmel0.rd.francetelecom.fr>
In-Reply-To: <E33E01DFD5BEA24B9F3F18671078951F10B727@SZXEML505-MBS.china.huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: TSVDIR review of draft-ietf-mif-current-practices-10
Thread-Index: AcwEjT94f5cFrLDDQnmx/e6koQnb/wAIoiCA
References: <E33E01DFD5BEA24B9F3F18671078951F10B727@SZXEML505-MBS.china.huawei.com>
From: <pierrick.seite@orange-ftgroup.com>
To: <haibin.song@huawei.com>, <tsv-dir@ietf.org>
X-OriginalArrivalTime: 27 Apr 2011 07:58:07.0361 (UTC) FILETIME=[D81FA710:01CC04B0]
X-Mailman-Approved-At: Wed, 27 Apr 2011 08:27:10 -0700
Cc: tsv-ads@tools.ietf.org, draft-ietf-mif-current-practices@tools.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, 27 Apr 2011 08:21:00 -0000

Hi Haibin,

Thanks for the review. The draft has been updated accordingly. Please =
see inline for more details.

Br,
Pierrick

> -----Message d'origine-----
> De=A0: Songhaibin [mailto:haibin.song@huawei.com]
> Envoy=E9=A0: mercredi 27 avril 2011 05:43
> =C0=A0: tsv-dir@ietf.org
> Cc=A0: tsv-ads@tools.ietf.org; ietf@ietf.org; draft-ietf-mif-current-
> practices@tools.ietf.org
> Objet=A0: TSVDIR review of draft-ietf-mif-current-practices-10
>=20
> Hi, all,
>=20
> I've reviewed this document as part of the transport area =
directorate's
> ongoing effort to review key IETF documents. These comments were =
written
> primarily for the transport area directors, but are copied to the
> document's authors for their information and to allow them to address =
any
> issues raised. The authors should consider this review together with =
any
> other last-call comments they receive. Please always CC =
tsv-dir@ietf.org
> if you reply to or forward this review.
>=20
> The document describes how the current practices cope with challenges
> raised by multiple interfaces. This draft is very good to read. And =
the
> content is complete in my opinion. But I also have one main comment =
and
> two minor comments.
> --------
> The main comment:
>=20
> Section 3.3.  Focus on access network selection
> This section describes the current practices about how to select the
> access network/points, especially how connection manager deal with the
> list of preferred SSID and how does it select the access point for
> attachment. I think this is out of the scope of MIF WG, which is aimed =
to
> address the problems raised by multiple interfaces, instead of =
attachment
> network/point selection for one interface. And the charter explicitly
> says: " Network discovery and selection on lower layers as defined by =
RFC
> 5113 is out of scope."
>=20

ok, section 3.3 is removed.

> -------
> Two minor comments:
>=20
> 3.1.1 Nokia S60 3rd Edition, Feature Pack 2
>=20
> Paragraph " When SNAPs are used, it is possibly for the operating =
system
> to notify applications when a preferred IAP, leading to the same
> destination, becomes available...."
>=20

Rewording:

When SNAPs are used, the operating system can notify applications when a =
preferred IAP, leading to the same destination, becomes available (for =
example, when a user comes within range of his home WLAN access point), =
or when the currently used IAP is no longer available. If so, =
applications have to reconnect via another IAP (for example, when a user =
goes out of range of his home WLAN and must move to the cellular =
network).

> When the word "possibly" is used here, I am a little confused. I guess =
the
> authors mean the operating system provides the capability to notify =
the
> applications, but the applications may/may not use it. Or does it mean =
the
> operating system can decide whether to notify the applications?
>=20
> Section 3.3.1 and 3.3.2
>=20
> These two sections describe the access network selection for =
Android/HTC
> Magic and RIM BlackBerry. But they use the similar method and most of =
the
> text are the same. So it is possible to merge these two sections. But =
my
> this comment is useless if the main comment is accepted.
>=20

n/a since section is removed.

> By the way, in Section 3.1.3 line 2, delete duplicate "can use".
>=20

Done.

> I hope this feedback will be useful to the authors.
>=20

Yes, thanks.

> -Haibin

From rjsparks@nostrum.com  Wed Apr 27 08:44:47 2011
Return-Path: <rjsparks@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 71488E06F7; Wed, 27 Apr 2011 08:44: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=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X0U3eKRZt4mY; Wed, 27 Apr 2011 08:44:46 -0700 (PDT)
Received: from nostrum.com (shaman.nostrum.com [72.232.179.90]) by ietfa.amsl.com (Postfix) with ESMTP id BADE0E06CE; Wed, 27 Apr 2011 08:44:46 -0700 (PDT)
Received: from dn3-177.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 p3RFhLZm060407 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 27 Apr 2011 10:43:25 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Subject: Re: Late comment on draft-ietf-sippping-sip-offeranswer-14
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Robert Sparks <rjsparks@nostrum.com>
In-Reply-To: <A444A0F8084434499206E78C106220CA0875F83F02@MCHP058A.global-ad.net>
Date: Wed, 27 Apr 2011 10:43:21 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <2DAC5182-ACDF-4DD9-9B7E-256D00C3E51E@nostrum.com>
References: <A444A0F8084434499206E78C106220CA0875F83F02@MCHP058A.global-ad.net>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>
X-Mailer: Apple Mail (2.1084)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Cc: "rai-ads@tools.ietf.org ADs" <rai-ads@tools.ietf.org>, SIPCORE Chairs <sipcore-chairs@tools.ietf.org>, mmusic-chairs@tools.ietf.org, sipping LIST <sipping@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, 27 Apr 2011 15:44:47 -0000

I believe the current text in the draft reflects the discussion from =
2007 at
<http://www.ietf.org/mail-archive/web/sipping/current/msg13812.html>

To summarize, while we think there may be implementations that interpret =
a change of session-id as a session reset,
RFC3264 doesn't support the notion. The top-level assumption of 3264 is =
that there is one SDP session associated
with a SIP dialog. (See in particular:
<http://www.ietf.org/mail-archive/web/sipping/current/msg13845.html>
<http://www.ietf.org/mail-archive/web/sipping/current/msg13870.html>
and
<http://www.ietf.org/mail-archive/web/sipping/current/msg13912.html>)

The thread explores places where some folks would like to things to be =
different, but those
things will need normative updates, probably to more than one RFC.

I believe the text in the draft is consistent with what our current =
specs say.

For the normative updates we would need to make for this particular =
topic, I think=20
restarting the debate on the RAI list (with pointers to SIPCORE and =
MMUSIC) is the right thing to do.
=09
RjS

On Apr 26, 2011, at 8:37 AM, Elwell, John wrote:

> I know last call finished already, but the following has just been =
brought to my attention:
>=20
> In section 5.2.5
> "Changing the o-line,
>      except version number value, during the session is an error case.
>      The behavior when receiving such a non-compliant offer/answer SDP
>      body is implementation dependent. "
> I would content this is NOT an error situation, or at least not an =
error in the case where a NEW session is being signalled.
>=20
> Consider a 3PCC situation along the lines described in section 7 of =
RFC 3725. The controlling B2BUA converts a session between UA A and UA B =
into a session between UA B and UA C. Prior to this conversion, UA B has =
received UA A's SDP (SDP A). As a result of the conversion, UA B =
receives UA C's SDP (SDP C).
>=20
> SDP C is likely to be completely different from SDP A. Therefore just =
a change of version number in the o-line is insufficient and would =
probably violate RFC 3264. In particular, if SDP A has 2 m-lines and SDP =
C has only one m-line, the change from 2 m-lines to 1 m-line is not =
permitted according to RFC 3264. So although RFC 3725 talks about the =
controlling B2BUA adjusting version numbers, that is insufficient in =
some cases.
>=20
> The text of 5.2.5 then goes on to say:
> "The behavior when receiving such a non-compliant offer/answer SDP
>      body is implementation dependent."
> It is not clear what this fails to comply with. I can find nothing in =
RFC 3264 that stops you sending a new o-line if there is a new session. =
Yes, it would be non-compliant if only modifying an existing session, =
but how does the recipient know whether or not it is a new session, and =
therefore whether or not it is valid?
>=20
> It then goes on to recommend use of Replaces in this situation (i.e. =
change of session):
> "If a UA needs to negotiate a
>      'new' SDP session, it should use the INVITE/Replaces method."
> But Replaces is not feasible if the UA concerned does not support it =
(and hence "should", presumably). So there will still be cases where a =
controlling B2BUA is forced to change the o-line (not just the version) =
in order to comply with RFC 3264.
>=20
> So there needs to be a mechanism for changing to a 'new' session =
without relying on Replaces. As far as I can see, there is no standards =
track RFC that forbids changing the o-line to achieve this, so this new =
Informational draft should not attempt to make that change, and in =
particular should not do so without proposing an alternative solution.
>=20
> A simple fix would be to delete the entire bullet beginning "In the =
o-line, only the version number may change".
>=20
> John
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From Ed.Lewis@neustar.biz  Thu Apr 28 07:42:21 2011
Return-Path: <Ed.Lewis@neustar.biz>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EEB0E06BA for <ietf@ietfa.amsl.com>; Thu, 28 Apr 2011 07:42:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.459
X-Spam-Level: 
X-Spam-Status: No, score=-106.459 tagged_above=-999 required=5 tests=[AWL=0.140, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9WOz0bqDuwq8 for <ietf@ietfa.amsl.com>; Thu, 28 Apr 2011 07:42:20 -0700 (PDT)
Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by ietfa.amsl.com (Postfix) with ESMTP id 78666E0669 for <ietf@ietf.org>; Thu, 28 Apr 2011 07:42:19 -0700 (PDT)
Received: from Work-Laptop-2.local (nyttbox.md.ogud.com [10.20.30.4]) by stora.ogud.com (8.14.4/8.14.4) with ESMTP id p3SEh5mU059878; Thu, 28 Apr 2011 10:43:05 -0400 (EDT) (envelope-from Ed.Lewis@neustar.biz)
Received: from [10.31.203.186] by Work-Laptop-2.local (PGP Universal service); Thu, 28 Apr 2011 10:42:12 -0400
X-PGP-Universal: processed; by Work-Laptop-2.local on Thu, 28 Apr 2011 10:42:12 -0400
Mime-Version: 1.0
Message-Id: <a06240800c9df29c0bf75@[10.31.203.186]>
Date: Thu, 28 Apr 2011 10:40:06 -0400
To: ietf@ietf.org
From: Edward Lewis <Ed.Lewis@neustar.biz>
Subject: Comments surrounding draft-iab-dns-applications-01
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Scanned-By: MIMEDefang 2.68 on 10.20.30.4
Cc: ed.lewis@neustar.biz
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 14:42:21 -0000

These comments were sent to the IAB already.  I was encouraged to 
send them to the general IETF list.  This is mostly a re-posting of 
the comments, with one added paragraph (there's marker there).

The referenced document is:
http://www.ietf.org/internet-drafts/draft-iab-anycast-arch-implications-01.txt

It's hard to make comments on a document whose mission is not at all 
clear.  The problem I have is that the document has a faulty baseline 
and incorrectly assesses extensions and variations.  Having spent 15 
years with the DNS and having to come to a deep architectural 
understanding of it in order to define DNSSEC, my view of the DNS is 
vastly different than that documented by the IAB.  With this it is 
hard to tell what the document is trying to guard against.  Or push 
towards.

Starting with what the DNS is and why it exists has to recognize that 
a lot of work we think is native to it actually preceded it in the 
/etc/hosts.txt file and in similarly built systems.  DNS is not 
principally there to translate names to numbers as the draft opens 
with, although that is a high-profile use case.  The DNS did not 
define a uniform naming scheme.  DNS is there principally to build on 
the previous solution (a text file distributed once a week from a 
central location).

If I were asked to list the bullet points that describe the DNS core 
competency, they would be
  - availability
  - resilience
  - speed in response
  - speed in propagating data
  - distributed management
  - neutral
Where the DNS is weak is in the data plane and the management plane. 
The basic lookup/search algorithm is stilted, inflexible, and hard 
for many to understand.  The biggest dilemma that it faces is that in 
order to be strong it uses an unreliable transport substrate as it's 
primary communication mechanism, the same substrate that is the 
source of the protocol's chief technical challenges.

In a way, DNS is a balancing act, it is all about using UDP "right."

To a lesser extent, the fact that the DNS is not a client-server 
protocol, as it is usually treated in text, but a client-cache-server 
protocol complicates understanding it's architecture.  This is the 
very reason DNSSEC exists, the ingrained middle-man in the 
client-server exchange.  Attempts to empower the middle-man are the 
chief obstacle to improving the overall health of the DNS and it's 
cooperation with other protocol systems.

Over time there really hasn't been progress in the way of making the 
DNS support applications.  Despite what is in the IAB draft, there 
has been just one application that is built into the DNS, done at the 
"dawn of time" and not even in a significant way.  Mail is the only 
application with built in support in DNS.  No other application has 
ever changed the DNS definition.  To understand this we should look a 
chronology of changes to the DNS concept and specification.

The original DNS specification is as defined in STD 13's documents. 
I won't bore you with repeating what's there, except to point out 
that a few seminal types are included in the original set.

It is also important to quantify what's meant by DNS support for an 
application.  The baseline for any type is, given a name, class, and 
type, the returned value will have a set of data.  Any resource 
record type that follows this baseline is considered to have "no 
special processing," the label put on sensitive types.

Types that have no special processing include the A, AAAA, and PTR 
records.  Some of these types do contain domain name that can be 
compressed and this is confused as special processing - but that is 
not special to the protocol, just special to the marshalling of the 
parameters.  Surprising to some folks, SRV and NAPTR also have no 
special processing, in fact aren't even subject to message 
compression.  This point is one I have to make because the draft uses 
SRV and NAPTR as evidence of application scope creep into the DNS.

Types that do have special processing include this list (not 
exclusively) SOA, NS, MX, CNAME, DNAME, and the DNSSEC types.  These 
are the types that are cause considerations for the DNS.  MX is the 
mail application dedicated type.  It's impact is that it causes 
additional data (address records) to be included in a response.  A 
very lightweight action, but special processing nonetheless.

One of the concerns that is conflated with NAPTR, TXT, DNSSEC and 
IPv6 records is the concern over protocol data unit size.  This issue 
is generic to the DNS and stems from the UDP transport "dependency" 
and not on application demands.  (Back to the balancing act involving 
UDP.)

Back to the chronology, looking for application-intelligence creep.

These are what I consider to be the turning points in DNS history:

RFC 1995/1996 - event-driven and incremental updates of zone contents
RFC 2136 - dynamic updating of a zone's contents
RFC 2181 - reduction in gullibility of caches
RFC 2308 - negative caching and the introduction of mnemonics
RFC 2671 - extended DNS header/trailer
RFC 2672 - DNAME (non-terminal query redirection)
"Views" - BIND's feature supporting query-source tailored responses
RFC 4033 - DNSSEC (cache poisoning defense)

If one gains an understanding of those RFCs (and the BIND feature), 
they will have a workable impression of the DNS.  Not complete and 
with some gaps, but the architecture would be roughed in.

Internationalized domain names have no impact on the architecture of 
the DNS, the same as for the DDDS and SRV record.  IDNs and SRVs do 
rely on their own naming conventions, but that isn't an issue for the 
DNS.  SRV's naming convention obviates the use of wildcards, but that 
is not a concern for the DNS protocol's architecture.

The recent push to support tailored responses, that is, responses 
based on QNAME, QTYPE, QCLASS plus information about or inside the 
query message, has been happening for nearly a decade.  I don't 
recall the exact version of BIND that introduced Views, but I do know 
I was using it in 2003 when I worked at ARIN.  Views was in response 
to outside demands, unknown to me, and I was aware of statefull 
firewalls that did something similar back into the late 90's.  This 
effort is sustained by latent demand, not a provider's recent desire.

(Paragraph added for IETF list) In my opinion, merely adding a RR 
type to the DNS does not represent an architectural change which is 
why I launched in to this history.  Applications have added record 
types over time.  The addition of a type is not a significant event, 
in fact, it is an event that has not happened frequently enough.  To 
me, significant changes to the architecture would include  updates to 
the algorithm in RFC 1034, section 4.3.2.  To date though, that 
section has only been updated for DNAME and fixed for CNAME (in RFC 
2672 and 4592 respectively).  Architectural changes may not impact 
that algorithm, but such changes signal architectural impacts more so 
than a newly defined type.

So far I've summed up the reasons why I disagree with the beginning 
of the document.  After writing this I went back to the document 
again to see if I better understood the point of the draft.

In section 4 there are four guiding principles that center on 
enforcing the idea that there is complete coherency across queries 
for QNAME, QTYPE, and QCLASS.  In my opinion this is archaic. 
Although the IETF has ignored in-coherency in DNS (the failure of 
http://tools.ietf.org/html/draft-krishnaswamy-dnsop-dnssec-split-view-04 
to even become an WG item) in the "real world" this has been going on 
since the late 90's.

One reason why such in-coherency exists today, having stood the test 
of at least a decade in operations (running code) is that 
in-coherency is not a radical idea despite the perception.  In the 
original framing of the DNS data was static, quickly a dynamic nature 
was added.  In a static world, coherency is a measurable and 
achievable condition, with dynamic elements, it is not.  Seeing a 
zone change rapidly is isomorphic to a server responding differently 
based on source IP address when examining the traffic crossing port 
53.  From this observation, combining the concept of tailored 
responses with the DNS is fairly easy.

Later in section 4 there are five other cautionary tales.  Most of 
these are "not a problem" today.

One of these describes a true concern - relying on knowledge of the 
DNS management model to assist in authorization determination, that 
is, knowing where zone cuts exist.  An application that relies on the 
management of data in another application has abdicated it's 
authority and will suffer the consequences at some point.  This is 
not unique to the DNS.

Mapping real world objects or concepts to domain names can be as 
complicated as anyone wants.  For example, naming routers with 
multiple interfaces, a problem seen on NOG lists periodically.  The 
complexity in the mapping is immaterial, so long as the application 
developers can do it consistently.  Perhaps the most complex mapping 
is hashing, as is done for DNSSEC's NSEC3.

Sensitive data can be in the DNS if other protections are taken. 
E.g., most companies consider their internal hardware topology to be 
sensitive but still run DNS for the benefit of their employees.  They 
then keep this DNS "private."  (Again, this practice is not 
documented by the IETF.)  Some ENUM work has been done to make ENUM 
work in places where telephone number information is considered 
sensitive.

The remaining points are outmoded.  While it is true that 
synchronizing zone contents with external sources of data take work, 
it can be made to work.  Maybe the misperception is that this is only 
about the DNS.  But sometimes putting more work on the DNS alleviates 
other systems.  In this case, the DNS can be operated as it should 
be, making use of the dynamic update features the IETF approved and 
the zone data propagation approaches already defined with the result 
of assisting in traffic management.  Not perfectly, but helping.

The recommendations in section 4 are arguable.  There are fairly 
solid arguments why the recommendations (except perhaps one of them) 
are wrong.  I am not saying the recommendations mentioned have merit, 
but they are not worthy of being backed by the IAB.

In section 3, well, in trying not to get into a blow-by-blow 
discussion, I'll summarize my thoughts that the IAB appears to be 
saying "avoid these things because they will be bad" even though some 
of them have been in play for more than a decade.  It's like a parent 
telling their teenager not to smoke after the teen has already 
developed the habit.

I have to mention 3.3.1.  The red herring about the size of data in 
DNS has been around for a long time.  There is no issue.  TCP is not 
a problem for DNS, at least architecturally speaking.  Yes, some 
implementations don't have this right, but the situation can be 
fixed.  Inside the DNS, size is just a number.  All applications have 
size issues.  All that is needed is to keep in mind what the 
strengths of the DNS are, and let applications try to live within the 
constraints.

If the IAB is going to make such a statement, they should remind 
applications what the strengths and limitations of the DNS are and 
have recommendations on who to solve generic problems.  As written 
the document sounds like a sad, almost pathetic plea for folks to 
stop innovating with the DNS.  It's almost as bad as the IAB 
statement on a unique root, which caused more problems than it 
solved.  (I've never bothered to read the the "extend DNS" document 
after the first few revisions of it.)

Finally, as the document stands now, I'd rather not be listed as a 
contributor.  It's not fair to me to be associated with the draft's 
architectural view.  It is fair to say I've submitted comments, but 
don't give the impression I endorse the document as it is.

-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis
NeuStar                    You can leave a voice message at +1-571-434-5468

Me to infant son: "Waah! Waah! Is that all you can say?  Waah?"
Son: "Waah!"

From evnikita2@gmail.com  Thu Apr 28 10:22:13 2011
Return-Path: <evnikita2@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 18F03E070C; Thu, 28 Apr 2011 10:22:13 -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=[AWL=-1.142,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LrH+RjjI8f6x; Thu, 28 Apr 2011 10:22:12 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id 712B9E0701; Thu, 28 Apr 2011 10:22:11 -0700 (PDT)
Received: by fxm15 with SMTP id 15so2305605fxm.31 for <multiple recipients>; Thu, 28 Apr 2011 10:22:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type; bh=eVRHyV5f5ieKi5JGE5RrbXajcQzxOxFVHxyhL43LDBg=; b=CXjoTkmEmNasVtQjh+V9t1NbTCK2fnhTeiVZtAkQqma4s1Gld4I71lfPLldwBG8Kwl b9pgzWNQFBa4U/fn83qd5NYOyjGgGv6R0t5LkSqQtSgu3iytpuVsoA0CLgS8TReRlBvP ntAnTpulcgz0mhxfoLHdBS3M0YArwZQDIDxTc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type; b=N2M7cXn2/gstLaC01gP3eoBehJLWMjbZP8dsRszvwMlg2bmNkNwnP8kT0JQCmbwpOB 0B1jCGI4kDyzTU+GN/khBMPzx9Laoo6C8IG3P3Ey6QzhJ/z71SKaRxwwC9orFbnuV/N/ bqk9ZFGVyVq7sxYN7LVvIrIlMSk4zPIu+QLjQ=
Received: by 10.223.83.3 with SMTP id d3mr1515738fal.89.1304011330531; Thu, 28 Apr 2011 10:22:10 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id p16sm648754fax.21.2011.04.28.10.22.07 (version=SSLv3 cipher=OTHER); Thu, 28 Apr 2011 10:22:08 -0700 (PDT)
Message-ID: <4DB9A26C.9010303@gmail.com>
Date: Thu, 28 Apr 2011 20:22:52 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-mmusic-ice-options-registry-01.txt> (IANA Registry for Interactive Connectivity Establishment (ICE)	Options) to Proposed Standard
References: <20110428160138.13587.58242.idtracker@ietfa.amsl.com>
In-Reply-To: <20110428160138.13587.58242.idtracker@ietfa.amsl.com>
Content-Type: multipart/alternative; boundary="------------060409000201000508080501"
Cc: draft-ietf-mmusic-ice-options-registry@tools.ietf.org, mmusic@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 Apr 2011 17:22:13 -0000

This is a multi-part message in MIME format.
--------------060409000201000508080501
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hello,

Some comments on this document, currently in Last Call.

> Network Working Group                                      M. Westerlund
> Internet-Draft                                                  Ericsson
> Updates:5245  <http://tools.ietf.org/html/rfc5245>  (if approved)                                   C. Perkins
> Intended status: Standards Track                   University of Glasgow
> Expires: September 29, 2011                               March 28, 2011
I don't see why the intended status for this document is Standards 
Track.  Wouldn't Informational be enough?  Could you please justify why 
have you chosen it?

Your registry description does not mention what is the precise name of 
the registry.  While everybody understands that is sands for ICE 
options, it would be useful to give IANA distinctive guidelines on its 
name (this is also required in RFC5226, Section 4.2, 1) in the list; 
http://tools.ietf.org/html/rfc5226#section-4.2).

 From RFC 5226, also Section 4.2:

>   5) Initial assignments and reservations.  Clear instructions
>           should be provided to identify any initial assignments or
>           registrations.  In addition, any ranges that are to be reserved
>   for "Private Use", "Reserved", "Unassigned", etc. should be
>           clearly indicated.

Are there any initial assignments?  Your document mentions one option; 
shouldn't it be registered?

>   A registration request MUST include the following information:
>
>     [ . . . ]
Shall this be mentioned as a registration template?

> o  Email and Address of the Contact person
I think you should add the name of the contact person to the name of 
this field as well.

I see, except some aforementioned issues, this document conforms to RFC 
5226, particularly Section 4.2.

Thanks in advance for considering my comments.

Mykyta Yevstifeyev

28.04.2011 19:01, The IESG wrote:
> The IESG has received a request from the Multiparty Multimedia Session
> Control WG (mmusic) to consider the following document:
> - 'IANA Registry for Interactive Connectivity Establishment (ICE)
> Options'
>    <draft-ietf-mmusic-ice-options-registry-01.txt>  as a 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 2011-05-12. 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.
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-mmusic-ice-options-registry/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-mmusic-ice-options-registry/
>
>
>
> No IPR declarations have been submitted directly on this I-D.
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce
>


--------------060409000201000508080501
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#ffffff" text="#000000">
    Hello,<br>
    <br>
    Some comments on this document, currently in Last Call.<br>
    <br>
    <blockquote type="cite">
      <pre>Network Working Group                                      M. Westerlund
Internet-Draft                                                  Ericsson
Updates: <a href="http://tools.ietf.org/html/rfc5245">5245</a> (if approved)                                   C. Perkins
Intended status: Standards Track                   University of Glasgow
Expires: September 29, 2011                               March 28, 2011
</pre>
    </blockquote>
    I don't see why the intended status for this document is Standards
    Track.&nbsp; Wouldn't Informational be enough?&nbsp; Could you please justify
    why have you chosen it?<br>
    <br>
    Your registry description does not mention what is the <span
      id="result_box" class="short_text" lang="en"><span title="&#1053;&#1072;&#1078;&#1084;&#1080;&#1090;&#1077;,
        &#1095;&#1090;&#1086;&#1073;&#1099; &#1091;&#1074;&#1080;&#1076;&#1077;&#1090;&#1100; &#1072;&#1083;&#1100;&#1090;&#1077;&#1088;&#1085;&#1072;&#1090;&#1080;&#1074;&#1085;&#1099;&#1081; &#1087;&#1077;&#1088;&#1077;&#1074;&#1086;&#1076;" class="hps">precise name
        of the registry.&nbsp; While everybody understands </span></span>that
    is sands for ICE options, it would be useful to give IANA
    distinctive guidelines on its name (this is also required in
    RFC5226, Section 4.2, 1) in the list;
    <a class="moz-txt-link-freetext" href="http://tools.ietf.org/html/rfc5226#section-4.2">http://tools.ietf.org/html/rfc5226#section-4.2</a>).<br>
    <br>
    From RFC 5226, also Section 4.2:<br>
    <br>
    <blockquote type="cite">
      <pre class="newpage"> 5) Initial assignments and reservations.  Clear instructions
         should be provided to identify any initial assignments or
         registrations.  In addition, any ranges that are to be reserved</pre>
      <pre class="newpage"> for "Private Use", "Reserved", "Unassigned", etc. should be
         clearly indicated.</pre>
    </blockquote>
    <br>
    Are there any initial assignments?&nbsp; Your document mentions one
    option; shouldn't it be registered?<br>
    <br>
    <blockquote type="cite">
      <pre class="newpage"> A registration request MUST include the following information:

   [ . . . ]</pre>
    </blockquote>
    Shall this be mentioned as a registration template?<br>
    <br>
    <blockquote type="cite">
      <pre class="newpage">o  Email and Address of the Contact person</pre>
    </blockquote>
    I think you should add the name of the contact person to the name of
    this field as well.<br>
    <br>
    I see, except some aforementioned issues, this document conforms to
    RFC 5226, particularly Section 4.2. <br>
    <br>
    Thanks in advance for considering my comments.<br>
    <br>
    Mykyta Yevstifeyev<br>
    <br>
    28.04.2011 19:01, The IESG wrote:
    <blockquote
      cite="mid:20110428160138.13587.58242.idtracker@ietfa.amsl.com"
      type="cite">
      <pre wrap="">
The IESG has received a request from the Multiparty Multimedia Session
Control WG (mmusic) to consider the following document:
- 'IANA Registry for Interactive Connectivity Establishment (ICE)
Options'
  &lt;draft-ietf-mmusic-ice-options-registry-01.txt&gt; as a 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
<a class="moz-txt-link-abbreviated" href="mailto:ietf@ietf.org">ietf@ietf.org</a> mailing lists by 2011-05-12. Exceptionally, comments may be
sent to <a class="moz-txt-link-abbreviated" href="mailto:iesg@ietf.org">iesg@ietf.org</a> instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

The file can be obtained via
<a class="moz-txt-link-freetext" href="http://datatracker.ietf.org/doc/draft-ietf-mmusic-ice-options-registry/">http://datatracker.ietf.org/doc/draft-ietf-mmusic-ice-options-registry/</a>

IESG discussion can be tracked via
<a class="moz-txt-link-freetext" href="http://datatracker.ietf.org/doc/draft-ietf-mmusic-ice-options-registry/">http://datatracker.ietf.org/doc/draft-ietf-mmusic-ice-options-registry/</a>



No IPR declarations have been submitted directly on this I-D.
_______________________________________________
IETF-Announce mailing list
<a class="moz-txt-link-abbreviated" href="mailto:IETF-Announce@ietf.org">IETF-Announce@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/ietf-announce">https://www.ietf.org/mailman/listinfo/ietf-announce</a>

</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------060409000201000508080501--

From touch@isi.edu  Thu Apr 28 13:38:53 2011
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 C81ABE06C3 for <ietf@ietfa.amsl.com>; Thu, 28 Apr 2011 13:38:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.895
X-Spam-Level: 
X-Spam-Status: No, score=-104.895 tagged_above=-999 required=5 tests=[AWL=1.704, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f3hWte6BG1kO for <ietf@ietfa.amsl.com>; Thu, 28 Apr 2011 13:38:52 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 19A12E0669 for <ietf@ietf.org>; Thu, 28 Apr 2011 13:38:52 -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 p3SKcJph027514 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Thu, 28 Apr 2011 13:38:19 -0700 (PDT)
Message-ID: <4DB9D03B.4070707@isi.edu>
Date: Thu, 28 Apr 2011 13:38:19 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: "tsv-ads@tools.ietf.org" <tsv-ads@tools.ietf.org>, IETF discussion list <ietf@ietf.org>, draft-ietf-v6ops-v6-aaaa-whitelisting-implications@tools.ietf.org
Subject: TSVDIR review of draft-ietf-v6ops-v6-aaaa-whitelisting-implications
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: Thu, 28 Apr 2011 20:38:53 -0000

Hi, all,

I've reviewed this document as part of the transport area directorate's
ongoing effort to review key IETF documents. These comments were written
primarily for the transport area directors, but are copied to the
document's authors for their information and to allow them to address
any issues raised. The authors should consider this review together with
any other last-call comments they receive. Please always CC
tsv-dir@ietf.org if you reply to or forward this review.

The document describes the issues associated with the practice of 
whitelisting in DNS servers, in an attempt to limit which recursive 
resolvers receive responses to requests for AAAA (IPv6) records.

The practice of whitelisting can have significant impact on transport 
protocols in the reachability of IPv6 endpoints. There are no transport 
issues of a more specific nature discussed or determined as part of this 
review.

I do have some other concerns which are noted below, and which are 
offered for consideration.

I hope this feedback will be useful to the authors, and will be glad to
provide further assistance either on- or off-list as useful.

Joe

---------------------------------------------------------------------

Overall, this document is quite long and has many gratuitous digressions 
which could easily be omitted. It is unnecessarily verbose and lengthy 
for its topic. E.g., the architectural implications that stretch this 
issue into network heterogeneity are a bit of a stretch, and the 
discussion (and citation) for Newton's notion of momentum is unnecessary.

Blacklisting is noted in other environments in Sec 6, and noted as an 
alternative for the DNS AAAA issue in a cursory fashion in Sec 7.3.7. It 
should certainly be introduced and defined earlier, and included in the 
alternatives discussed in Sec 8. Blacklisting provides a useful 
alternative because it requires explicit action to inhibit, rather than 
requiring explicit action to avoid, and the tradeoff between 
blacklisting and whitelisting should be discussed in more detail.

The list of alternate solutions (Sec 8) might be placed much earlier 
(Sec 2, after an intro), as it provides the background for the rest of 
the discussion.

The document might also benefit from a brief discussion of how users are 
rarely in control of their DNS, given hijacking that currently occurs in 
ISPs. I.e., even when they could use a whitelisted recursive resolver, 
that might be impossible due to current ISP practices.

Sec 6.2 notes that deployment of whitelisting might require an Internet 
Draft; this should be replaced with "RFC" (presumably standards track or 
BCP).

-----

From johnl@iecc.com  Thu Apr 28 19:36:55 2011
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 16434E0713 for <ietf@ietfa.amsl.com>; Thu, 28 Apr 2011 19:36:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.12
X-Spam-Level: 
X-Spam-Status: No, score=-109.12 tagged_above=-999 required=5 tests=[AWL=2.079, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7SC0VBQNOflk for <ietf@ietfa.amsl.com>; Thu, 28 Apr 2011 19:36:54 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by ietfa.amsl.com (Postfix) with ESMTP id B9378E0684 for <ietf@ietf.org>; Thu, 28 Apr 2011 19:36:53 -0700 (PDT)
Received: (qmail 61464 invoked from network); 29 Apr 2011 02:36:52 -0000
Received: from mail1.iecc.com (64.57.183.56) by mail1.iecc.com with QMQP; 29 Apr 2011 02:36:52 -0000
Date: 29 Apr 2011 02:36:30 -0000
Message-ID: <20110429023630.46187.qmail@joyce.lan>
From: "John Levine" <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: Comments surrounding draft-iab-dns-applications-01
In-Reply-To: <a06240800c9df29c0bf75@[10.31.203.186]>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Cc: Ed.Lewis@neustar.biz
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 02:36:55 -0000

>It's hard to make comments on a document whose mission is not at all 
>clear.  The problem I have is that the document has a faulty baseline 
>and incorrectly assesses extensions and variations. ...

My experience with the DNS is nowhere near as deep as Ed's but having
done my share of DNS hackery (production special purpose DNS servers
written in perl), I have to agree with him.  This document starts by
conflating the DNS and applications built on top of the DNS, and goes
downhill from there.  I agree that there have been some pretty crufty
applications built on top of the DNS, but that cruftitude doesn't
affect the simple query and answer that the DNS does underneath.

The two points that do seem to apply to the DNS are, as Ed said,
larger responses and split horizon DNS.  Both of those have been
around for at least a decade without causing the world to collapse,
and neither is going away, particularly as DNSSEC becomes real, so
I don't understand what problem is to be solved.

So my advice would be to back up and write down in one or two
sentences what problem this document is supposed to fix or at least
describe, and then see how much of the rest of it might be salvaged.

This might be also a good time to write a DNS architecture document
analogous to Dave Crocker's mail architecture, that shows the layering
of the queries to authoritative servers, queries to caches, and the
applications built on top of them such as locating mail servers and
doing whatever NAPTR and DDNS do.

Regards,
John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. http://jl.ly

From narten@us.ibm.com  Thu Apr 28 21:53:11 2011
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 B6E80E0724 for <ietf@ietfa.amsl.com>; Thu, 28 Apr 2011 21:53:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.949
X-Spam-Level: 
X-Spam-Status: No, score=-105.949 tagged_above=-999 required=5 tests=[AWL=0.650, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZcbHJDU25Jaw for <ietf@ietfa.amsl.com>; Thu, 28 Apr 2011 21:53:10 -0700 (PDT)
Received: from e7.ny.us.ibm.com (e7.ny.us.ibm.com [32.97.182.137]) by ietfa.amsl.com (Postfix) with ESMTP id A8042E065B for <ietf@ietf.org>; Thu, 28 Apr 2011 21:53:08 -0700 (PDT)
Received: from d01relay03.pok.ibm.com (d01relay03.pok.ibm.com [9.56.227.235]) by e7.ny.us.ibm.com (8.14.4/8.13.1) with ESMTP id p3T4Ubgr007600 for <ietf@ietf.org>; Fri, 29 Apr 2011 00:30:37 -0400
Received: from d01av03.pok.ibm.com (d01av03.pok.ibm.com [9.56.224.217]) by d01relay03.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p3T4r7oS090814 for <ietf@ietf.org>; Fri, 29 Apr 2011 00:53:07 -0400
Received: from d01av03.pok.ibm.com (loopback [127.0.0.1]) by d01av03.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id p3T0qtRU016283 for <ietf@ietf.org>; Thu, 28 Apr 2011 21:52:55 -0300
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.151.17]) by d01av03.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id p3T0qtS4015883 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 28 Apr 2011 21:52:55 -0300
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id p3T4r6fY022073 for <ietf@ietf.org>; Fri, 29 Apr 2011 00:53:06 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.4/8.14.4/Submit) id p3T4r1C6021969 for ietf@ietf.org; Fri, 29 Apr 2011 00:53:01 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201104290453.p3T4r1C6021969@rotala.raleigh.ibm.com>
Date: Fri, 29 Apr 2011 00:53:01 -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-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Apr 2011 04:53:11 -0000

Total of 37 messages in the last 7 days.
 
script run at: Fri Apr 29 00:53:01 EDT 2011
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  5.41% |    2 |  8.41% |    22954 | ron.even.tlv@gmail.com
  8.11% |    3 |  4.45% |    12159 | glen@amsl.com
  2.70% |    1 |  9.67% |    26401 | bernard_aboba@hotmail.com
  5.41% |    2 |  5.76% |    15717 | pierrick.seite@orange-ftgroup.com
  5.41% |    2 |  4.83% |    13192 | sm@resistor.net
  5.41% |    2 |  3.63% |     9901 | john-ietf@jck.com
  2.70% |    1 |  5.79% |    15819 | ed.lewis@neustar.biz
  5.41% |    2 |  2.95% |     8068 | francis.dupont@fdupont.fr
  2.70% |    1 |  4.87% |    13301 | evnikita2@gmail.com
  2.70% |    1 |  3.61% |     9850 | jmh@joelhalpern.com
  2.70% |    1 |  3.04% |     8299 | rjsparks@nostrum.com
  2.70% |    1 |  2.88% |     7870 | hannes.tschofenig@gmx.net
  2.70% |    1 |  2.66% |     7269 | narten@us.ibm.com
  2.70% |    1 |  2.65% |     7244 | pekkas@netcore.fi
  2.70% |    1 |  2.60% |     7107 | brian.e.carpenter@gmail.com
  2.70% |    1 |  2.59% |     7082 | gwz@net-zen.net
  2.70% |    1 |  2.53% |     6922 | paf@cisco.com
  2.70% |    1 |  2.47% |     6754 | haibin.song@huawei.com
  2.70% |    1 |  2.47% |     6744 | hilarie@purplestreak.com
  2.70% |    1 |  2.45% |     6696 | john.elwell@siemens-enterprise.com
  2.70% |    1 |  2.35% |     6420 | amorris@amsl.com
  2.70% |    1 |  2.34% |     6386 | touch@isi.edu
  2.70% |    1 |  2.05% |     5606 | lear@cisco.com
  2.70% |    1 |  2.05% |     5598 | hartmans-ietf@mit.edu
  2.70% |    1 |  1.93% |     5280 | msk@cloudmark.com
  2.70% |    1 |  1.89% |     5160 | ben@estacado.net
  2.70% |    1 |  1.87% |     5100 | johnl@iecc.com
  2.70% |    1 |  1.81% |     4953 | alexey.melnikov@isode.com
  2.70% |    1 |  1.74% |     4742 | elwynd@dial.pipex.com
  2.70% |    1 |  1.64% |     4479 | tme@americafree.tv
--------+------+--------+----------+------------------------
100.00% |   37 |100.00% |   273073 | Total

From magnus.westerlund@ericsson.com  Fri Apr 29 01:47:19 2011
Return-Path: <magnus.westerlund@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 18718E06B2; Fri, 29 Apr 2011 01:47:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.541
X-Spam-Level: 
X-Spam-Status: No, score=-106.541 tagged_above=-999 required=5 tests=[AWL=0.058, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KlTg6m6byUWk; Fri, 29 Apr 2011 01:47:15 -0700 (PDT)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by ietfa.amsl.com (Postfix) with ESMTP id AEDD5E0678; Fri, 29 Apr 2011 01:47:14 -0700 (PDT)
X-AuditID: c1b4fb39-b7cc5ae000006f6d-17-4dba7b11695b
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id D5.4A.28525.11B7ABD4; Fri, 29 Apr 2011 10:47:13 +0200 (CEST)
Received: from [147.214.183.89] (153.88.115.8) by esessmw0197.eemea.ericsson.se (153.88.115.88) with Microsoft SMTP Server id 8.3.137.0; Fri, 29 Apr 2011 10:47:13 +0200
Message-ID: <4DBA7B11.8080708@ericsson.com>
Date: Fri, 29 Apr 2011 10:47:13 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; sv-SE; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Mykyta Yevstifeyev <evnikita2@gmail.com>
Subject: Re: Last Call: <draft-ietf-mmusic-ice-options-registry-01.txt> (IANA Registry for Interactive Connectivity Establishment (ICE)	Options) to Proposed Standard
References: <20110428160138.13587.58242.idtracker@ietfa.amsl.com> <4DB9A26C.9010303@gmail.com>
In-Reply-To: <4DB9A26C.9010303@gmail.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
Cc: "draft-ietf-mmusic-ice-options-registry@tools.ietf.org" <draft-ietf-mmusic-ice-options-registry@tools.ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "mmusic@ietf.org" <mmusic@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 Apr 2011 08:47:19 -0000

Hi Mykyta,

Thanks for the review.

See inline for response.

Mykyta Yevstifeyev skrev 2011-04-28 19:22:
> Hello,
> 
> Some comments on this document, currently in Last Call.
> 
>> Network Working Group                                      M. Westerlund
>> Internet-Draft                                                  Ericsson
>> Updates: 5245 <http://tools.ietf.org/html/rfc5245> (if approved)                                   C. Perkins
>> Intended status: Standards Track                   University of Glasgow
>> Expires: September 29, 2011                               March 28, 2011

> I don't see why the intended status for this document is Standards
> Track.  Wouldn't Informational be enough?  Could you please justify why
> have you chosen it?

I don't think we have put much thought into it. But one reason I can
think of is to have it on the same maturity level as the ICE
specification itself. Thus enabling a merge of this registry into an
update of RFC 5245 without forcing it to be recycled as proposed.

> 
> Your registry description does not mention what is the precise name of
> the registry.  While everybody understands that is sands for ICE
> options, it would be useful to give IANA distinctive guidelines on its
> name (this is also required in RFC5226, Section 4.2, 1) in the list;
> http://tools.ietf.org/html/rfc5226#section-4.2).


Yes, I agree that it should be included in Section 3.1 of our document
rather than only in the title which says "Interactive Connectivity
Establishment (ICE) Options"

> 
> From RFC 5226, also Section 4.2:
> 
>>  5) Initial assignments and reservations.  Clear instructions
>>          should be provided to identify any initial assignments or
>>          registrations.  In addition, any ranges that are to be reserved
>>  for "Private Use", "Reserved", "Unassigned", etc. should be
>>          clearly indicated.
> 
> Are there any initial assignments?  Your document mentions one option;
> shouldn't it be registered?

No, because when draft-ietf-avtcore-rtp-ecn gets published that will
actually do the registration. As that document isn't approved yet and in
fact still not WG last called this registry will first be created empty
and then populated.

> 
>>  A registration request MUST include the following information:
>>
>>    [ . . . ]
> Shall this be mentioned as a registration template?

It isn't written as one. It is a list of what needs to be present in the
registration. And I think a template would be more focused on what needs
to the general categories rather than the information. Thus I don't want
this as registration template.

> 
>> o  Email and Address of the Contact person
> I think you should add the name of the contact person to the name of
> this field as well.

As the two first bullets are:

   o  Name of contact person for the registration

   o  Email and Address of the Contact person

I don't quite understand your comment. Do you want us to merge the two
entries? This as the contact persons will need to provide name, email
and address. I am fine with merging them and this is likely a slight
improvement.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------

From evnikita2@gmail.com  Fri Apr 29 09:03:47 2011
Return-Path: <evnikita2@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 0A4F5E06A7; Fri, 29 Apr 2011 09:03:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.577
X-Spam-Level: 
X-Spam-Status: No, score=-4.577 tagged_above=-999 required=5 tests=[AWL=-0.978, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J4QpyDj7ip-B; Fri, 29 Apr 2011 09:03:43 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id 7C7FBE06A2; Fri, 29 Apr 2011 09:03:32 -0700 (PDT)
Received: by fxm15 with SMTP id 15so3009380fxm.31 for <multiple recipients>; Fri, 29 Apr 2011 09:03:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=+AKobDRo/SnBE04OibQ/c3A8r/dOvOkK7HDXldEmZ7E=; b=ToIdKbyVRMiDRPfkdWlVWM4y/KyZKuIbFRHzZBhPbPa/ocUhWTzZ831qdCDmEBKXT1 pYKMn9I/GsPemgga3LgSG+yDrPiYr/SaTBzDFWp/3a2lrbYh+V+4Jv6oTgnEMVOxVD49 BHqghoOBI0xJ6ppSB3SYFKEIRWMXX0QAqawuQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=V/K+HUsHsUEIXc0WDZZfoSfEbXX9jKsy3iW9WMSVk7knO+qwMrClp5Qsmww8759sZ8 omF1FQgLR2r2tmDtc/0nOEklPC8NgTKfBbYexL6ZMDDgxgFTGucdSmhzgsQcctP6KSa6 4Pg+bHzSVr9jdo1I2eTAQvUuUrQFR6VWqTm2k=
Received: by 10.223.100.15 with SMTP id w15mr296252fan.11.1304093011583; Fri, 29 Apr 2011 09:03:31 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id j12sm940093fax.9.2011.04.29.09.03.29 (version=SSLv3 cipher=OTHER); Fri, 29 Apr 2011 09:03:30 -0700 (PDT)
Message-ID: <4DBAE17E.6050807@gmail.com>
Date: Fri, 29 Apr 2011 19:04:14 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Subject: Re: Last Call: <draft-ietf-mmusic-ice-options-registry-01.txt> (IANA Registry for Interactive Connectivity Establishment (ICE)	Options) to Proposed Standard
References: <20110428160138.13587.58242.idtracker@ietfa.amsl.com> <4DB9A26C.9010303@gmail.com> <4DBA7B11.8080708@ericsson.com>
In-Reply-To: <4DBA7B11.8080708@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: "draft-ietf-mmusic-ice-options-registry@tools.ietf.org" <draft-ietf-mmusic-ice-options-registry@tools.ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "mmusic@ietf.org" <mmusic@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 Apr 2011 16:03:47 -0000

Magnus,

29.04.2011 11:47, Magnus Westerlund wrote:
> Hi Mykyta,
>
> Thanks for the review.
>
> See inline for response.
>
> Mykyta Yevstifeyev skrev 2011-04-28 19:22:
>> Hello,
>>
>> Some comments on this document, currently in Last Call.
>>
>>> Network Working Group                                      M. Westerlund
>>> Internet-Draft                                                  Ericsson
>>> Updates: 5245 (if approved)                                   C. Perkins
>>> Intended status: Standards Track                   University of Glasgow
>>> Expires: September 29, 2011                               March 28, 2011
>> I don't see why the intended status for this document is Standards
>> Track.  Wouldn't Informational be enough?  Could you please justify why
>> have you chosen it?
> I don't think we have put much thought into it. But one reason I can
> think of is to have it on the same maturity level as the ICE
> specification itself. Thus enabling a merge of this registry into an
> update of RFC 5245 without forcing it to be recycled as proposed.
This is a good reason, so I'll agree with it.
>> Your registry description does not mention what is the precise name of
>> the registry.  While everybody understands that is sands for ICE
>> options, it would be useful to give IANA distinctive guidelines on its
>> name (this is also required in RFC5226, Section 4.2, 1) in the list;
>> http://tools.ietf.org/html/rfc5226#section-4.2).
>
> Yes, I agree that it should be included in Section 3.1 of our document
> rather than only in the title which says "Interactive Connectivity
> Establishment (ICE) Options"
Agreed on this.  Such name is fine, IMO.
>>  From RFC 5226, also Section 4.2:
>>
>>>   5) Initial assignments and reservations.  Clear instructions
>>>           should be provided to identify any initial assignments or
>>>           registrations.  In addition, any ranges that are to be reserved
>>>   for "Private Use", "Reserved", "Unassigned", etc. should be
>>>           clearly indicated.
>> Are there any initial assignments?  Your document mentions one option;
>> shouldn't it be registered?
> No, because when draft-ietf-avtcore-rtp-ecn gets published that will
> actually do the registration. As that document isn't approved yet and in
> fact still not WG last called this registry will first be created empty
> and then populated.
So you should have mentioned this in the draft as well.
>>>   A registration request MUST include the following information:
>>>
>>>     [ . . . ]
>> Shall this be mentioned as a registration template?
> It isn't written as one. It is a list of what needs to be present in the
> registration. And I think a template would be more focused on what needs
> to the general categories rather than the information. Thus I don't want
> this as registration template.
OK, this matter is not very important.
>>> o  Email and Address of the Contact person
>> I think you should add the name of the contact person to the name of
>> this field as well.
> As the two first bullets are:
>
>     o  Name of contact person for the registration
>
>     o  Email and Address of the Contact person
>
> I don't quite understand your comment. Do you want us to merge the two
> entries? This as the contact persons will need to provide name, email
> and address. I am fine with merging them and this is likely a slight
> improvement.
No, I didn't propose to merge it.  I just proposed to rename this field 
as "Name, Email and Addresses of the Contact Person".

Thanks for taking time to response to my comments.

Mykyta Yevstifeyev
> Cheers
>
> Magnus Westerlund
>
> ----------------------------------------------------------------------
> Multimedia Technologies, Ericsson Research EAB/TVM
> ----------------------------------------------------------------------
> Ericsson AB                | Phone  +46 10 7148287
> Färögatan 6                | Mobile +46 73 0949079
> SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
>


From ben@estacado.net  Fri Apr 29 14:48:28 2011
Return-Path: <ben@estacado.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 AB8B3E0670; Fri, 29 Apr 2011 14:48:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.399
X-Spam-Level: 
X-Spam-Status: No, score=-2.399 tagged_above=-999 required=5 tests=[AWL=0.200,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bV1zuqh+gIsI; Fri, 29 Apr 2011 14:48:28 -0700 (PDT)
Received: from estacado.net (estacado-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:266::2]) by ietfa.amsl.com (Postfix) with ESMTP id 4441CE0593; Fri, 29 Apr 2011 14:48:27 -0700 (PDT)
Received: from [10.0.1.6] (cpe-76-183-178-106.tx.res.rr.com [76.183.178.106]) (authenticated bits=0) by estacado.net (8.14.3/8.14.3) with ESMTP id p3TLmDo5072298 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 29 Apr 2011 16:48:18 -0500 (CDT) (envelope-from ben@estacado.net)
From: Ben Campbell <ben@estacado.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Gen-ART LC review of RFC5591 to DS
Date: Fri, 29 Apr 2011 16:48:12 -0500
Message-Id: <4628632B-5C8D-4E14-9380-303D73B4E01E@estacado.net>
To: The IETF <ietf@ietf.org>, David Harrington <ietfdbh@comcast.net>, ietf@hardakers.net, Sean Turner <turners@ieca.com>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Cc: "gen-art@ietf.org Review Team" <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: Fri, 29 Apr 2011 21:48:28 -0000

(resending due to an addressing problem--please forgive the repeat)

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: RFC5591 and report-rfc5343-5590-5591-5953.txt
Reviewer: Ben Campbell=09
Review Date: 2011-04-29
IETF LC End Date: 2011-05-03

Summary: RFC5591 is likely ready to progress to draft standard. However, =
there are some features of the RFC for which it is not clear to me if =
they have been sufficiently tested.

Major issues:

None

Minor issues:

Section 6 of the interoperability report describes a failure to interop =
due to one implementation incorrectly not setting the security =
parameters of a response to match those of the request. The report =
recognized that implementations should do this--but I must point out =
this is a MUST level requirement in RFC5591. The report recognized that =
this was an implementation bug. But the report does not explicitly =
indicate whether a successful test when (and if) the bug was fixed. (I =
can only assume it was fixed and retested, since this would seem to =
block the other test results.)

Both section 6 and 7 of the interoperability report list the =
snmpTsmConfigurationUsePrefix configuration feature as untestable or =
untested. It's not clear to me why this was considered untestable, and I =
am agnostic on whether it's okay to progress without testing this =
feature. I mention it only to to make sure people better suited to judge =
the subtleties have noticed and thought about it.

Nits/editorial comments:

None=

From dhc@dcrocker.net  Fri Apr 29 16:32:39 2011
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 4ACA7E074B; Fri, 29 Apr 2011 16:32:39 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id htsCb10xWS+X; Fri, 29 Apr 2011 16:32:34 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 29A0CE06DC; Fri, 29 Apr 2011 16:32:31 -0700 (PDT)
Received: from [192.168.5.61] ([64.134.238.192]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p3TNWNHw032000 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Fri, 29 Apr 2011 16:32:29 -0700
Message-ID: <4DBB4A83.7010408@dcrocker.net>
Date: Fri, 29 Apr 2011 16:32:19 -0700
From: Dave CROCKER <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: IETF Discussion <ietf@ietf.org>
Subject: Review of:  draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03
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]); Fri, 29 Apr 2011 16:32:29 -0700 (PDT)
Cc: v6ops@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: Fri, 29 Apr 2011 23:32:39 -0000

Review:

Title:  IPv6 AAAA DNS Whitelisting Implications
I-D:    draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03

By:     D. Crocker <dcrocker@bbiw.net>
Date:   29 April 2011


Summary:

This draft is a discussion of a technique for resolving a dual-stack problem 
between IPv4 and IPv6, through the use of special DNS records.

The document appears to continue a recent use of the term 'whitelisting' that 
strongly conflicts with long-standing use of the term by the anti-abuse community.

The document needs to do a more careful job of introducing the problem it is 
solving and the explaining the way the 'whitelisting' mechanism works.

I also very strongly encourage finding a different term.

d/


> Abstract
>
>    The objective of this document is to describe what the whitelisting
>    of DNS AAAA resource records is, hereafter referred to as DNS

RRs are whitelisted?  Isn't it the addresses and not the records that are 
whitelisted?

Does this mean putting whitelisting records into the DNS or does it mean 
something else?

Comcast's own considerable expertise notwithstanding, has this doc been vetted 
with a range of organizations that actually DO whitelisting?  Has it been 
circulated through MAAWG and APWG?  Any comments from Spamhaus?  The 
Acknowledgements list does not seem to indicate a range of whitelist ops folks 
whose names I know.  (But then, I only know a few...)


>    whitelisting, as well as the implications of this emerging practice
>    and what alternatives may exist.  The audience for this document is
>    the Internet community generally, including the IETF and IPv6
>    implementers.

I suspect that product marketers won't have much interest in this.  I suspect 
that the target for this is anti-abuse technical and operations staff.


> Status of this Memo
>
>    This Internet-Draft is submitted in full conformance with the
>    provisions of BCP 78 and BCP 79.
>
>    Internet-Drafts are working documents of the Internet Engineering
>    Task Force (IETF).  Note that other groups may also distribute
>    working documents as Internet-Drafts.  The list of current Internet-
>    Drafts is at http://datatracker.ietf.org/drafts/current/.
>
>    Internet-Drafts are draft documents valid for a maximum of six months
>    and may be updated, replaced, or obsoleted by other documents at any
>    time.  It is inappropriate to use Internet-Drafts as reference
>    material or to cite them other than as "work in progress."
>
>    This Internet-Draft will expire on August 26, 2011.
>
> Copyright Notice
>
>    Copyright (c) 2011 IETF Trust and the persons identified as the
>    document authors.  All rights reserved.
>
>    This document is subject to BCP 78 and the IETF Trust's Legal
>    Provisions Relating to IETF Documents
>    (http://trustee.ietf.org/license-info) in effect on the date of
>    publication of this document.  Please review these documents
>    carefully, as they describe your rights and restrictions with respect
>    to this document.  Code Components extracted from this document must
>    include Simplified BSD License text as described in Section 4.e of
>    the Trust Legal Provisions and are provided without warranty as
>
>
>
> Livingood                Expires August 26, 2011                [Page 1]
> 
> Internet-Draft   IPv6 AAAA DNS Whitelisting Implications   February 2011
>
>
>    described in the Simplified BSD License.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Livingood                Expires August 26, 2011                [Page 2]
> 
> Internet-Draft   IPv6 AAAA DNS Whitelisting Implications   February 2011
>
>
> Table of Contents
>
>    1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  5
>    2.  How DNS Whitelisting Works . . . . . . . . . . . . . . . . . .  6
>      2.1.  Description of the Operation of DNS Whitelisting . . . . .  7
>    3.  What Problems Are Implementers Trying To Solve?  . . . . . . .  8
>    4.  Concerns Regarding DNS Whitelisting  . . . . . . . . . . . . .  9
>    5.  Similarities to Other DNS Operations . . . . . . . . . . . . . 12
>      5.1.  Similarities to Split DNS  . . . . . . . . . . . . . . . . 12
>      5.2.  Similarities to DNS Load Balancing . . . . . . . . . . . . 12
>    6.  Likely Deployment Scenarios  . . . . . . . . . . . . . . . . . 13
>      6.1.  Deploying DNS Whitelisting On An Ad Hoc Basis  . . . . . . 13
>      6.2.  Deploying DNS Whitelisting Universally . . . . . . . . . . 14
>    7.  Implications of DNS Whitelisting . . . . . . . . . . . . . . . 15
>      7.1.  Architectural Implications . . . . . . . . . . . . . . . . 15
>      7.2.  Public IPv6 Address Reachability Implications  . . . . . . 16
>      7.3.  Operational Implications . . . . . . . . . . . . . . . . . 17
>        7.3.1.  De-Whitelisting May Occur  . . . . . . . . . . . . . . 17
>        7.3.2.  Authoritative DNS Server Operational Implications  . . 17
>        7.3.3.  DNS Recursive Resolver Server Operational
>                Implications . . . . . . . . . . . . . . . . . . . . . 18
>        7.3.4.  Monitoring Implications  . . . . . . . . . . . . . . . 19
>        7.3.5.  Implications of Operational Momentum . . . . . . . . . 19
>        7.3.6.  Troubleshooting Implications . . . . . . . . . . . . . 20
>        7.3.7.  Additional Implications If Deployed On An Ad Hoc
>                Basis  . . . . . . . . . . . . . . . . . . . . . . . . 20
>      7.4.  Homogeneity May Be Encouraged  . . . . . . . . . . . . . . 20
>      7.5.  Technology Policy Implications . . . . . . . . . . . . . . 21
>      7.6.  IPv6 Adoption Implications . . . . . . . . . . . . . . . . 22
>    8.  Solutions  . . . . . . . . . . . . . . . . . . . . . . . . . . 23
>      8.1.  Implement DNS Whitelisting Universally . . . . . . . . . . 23
>      8.2.  Implement DNS Whitelisting On An Ad Hoc Basis  . . . . . . 23
>      8.3.  Do Not Implement DNS Whitelisting  . . . . . . . . . . . . 23
>        8.3.1.  Solving Current End User IPv6 Impairments  . . . . . . 24
>        8.3.2.  Gain Experience Using IPv6 Transition Names  . . . . . 24
>    9.  Is DNS Whitelisting a Recommended Practice?  . . . . . . . . . 24
>    10. Security Considerations  . . . . . . . . . . . . . . . . . . . 25
>      10.1. DNSSEC Considerations  . . . . . . . . . . . . . . . . . . 25
>      10.2. Authoritative DNS Response Consistency Considerations  . . 26
>    11. Privacy Considerations . . . . . . . . . . . . . . . . . . . . 26
>    12. IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 27
>    13. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 27
>    14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 27
>    15. References . . . . . . . . . . . . . . . . . . . . . . . . . . 28
>      15.1. Normative References . . . . . . . . . . . . . . . . . . . 28
>      15.2. Informative References . . . . . . . . . . . . . . . . . . 29
>    Appendix A.  Document Change Log . . . . . . . . . . . . . . . . . 31
>    Appendix B.  Open Issues . . . . . . . . . . . . . . . . . . . . . 32
>
>
>
> Livingood                Expires August 26, 2011                [Page 3]
> 
> Internet-Draft   IPv6 AAAA DNS Whitelisting Implications   February 2011
>
>
>    Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 32
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Livingood                Expires August 26, 2011                [Page 4]
> 
> Internet-Draft   IPv6 AAAA DNS Whitelisting Implications   February 2011
>
>
> 1.  Introduction
>
>    This document describes the emerging practice of whitelisting of DNS
>    AAAA resource records (RRs), which contain IPv6 addresses, hereafter
>    referred to as DNS whitelisting.  The document explores the
>    implications of this emerging practice are and what alternatives may
>    exist.
>
>    The practice of DNS whitelisting appears to have first been used by
>    major web content sites (sometimes described herein as "highly-

Really?  Not for email first?


>    trafficked domains" or "major domains").  These web site operators,
>    or domain operators, observed that when they added AAAA resource
>    records to their authoritative DNS servers in order to support IPv6

Oh.  You mean /IPv6/ whitelisting.


>    access to their content that a small fraction of end users had slow
>    or otherwise impaired access to a given web site with both AAAA and A
>    resource records.  The fraction of users with such impaired access
>    has been estimated to be roughly 0.078% of total Internet users
>    [IETF-77-DNSOP] [NW-Article-DNSOP] [Evaluating IPv6 Adoption] [IPv6
>    Brokenness].  Thus, in an example Internet Service Provider (ISP)
>    network of 10 million users, approximately 7,800 of those users may
>    experience such impaired access.

At a minimum, these sorts of statistics need to be normalized across IPv6 
users/traffic, given how small a percentage that is in total users and total 
traffice.  If that's what is meant it should be stated.  If it isn't, the 
statistic should be recalculated.


>    As a result of this impairment affecting end users of a given domain,
>    a few major domains have either implemented DNS whitelisting or are
>    considering doing so [NW-Article-DNS-WL] [IPv6 Whitelist Operations].

How or why does whitelisting affect slow performance for these folk?


>    When implemented, DNS whitelisting in practice means that a domain's
>    authoritative DNS will return a AAAA resource record to DNS recursive
>    resolvers [RFC1035] on the whitelist, while returning no AAAA
>    resource records to DNS resolvers which are not on the whitelist.  It

Oh.  The whitelisting is for resolving a conflict between AAAA and A record choices?

Normally, the term 'whitelisting' is used to refer to bypass anti-abuse 
mechanisms.  This appears to be for something else and it seems odd to call it 
whitelisting.

Note the more typical use of the term:

    <http://www.dnswl.org/>

    <http://en.wikipedia.org/wiki/DNSBL>

 
<http://publib.boulder.ibm.com/infocenter/domhelp/v8r0/index.jsp?topic=/com.ibm.help.domino.admin.doc/DOC/H_USING_DNS_whitelists_OVER.html>

It appears that some v6 folks have chosen to co-opt a distinctive and very well 
established anti-abuse term for an entirely different purpose.



>    is important to note that these major domains are motivated by a
>    desire to maintain a high-quality user experience for all of their
>    users.  By engaging in DNS whitelisting, they are attempting to
>    shield users with impaired access from the symptoms of those
>    impairments.
>
>    Critics of the practice of DNS whitelisting have articulated several
>    concerns.  Among these are that:
>
>    o  DNS whitelisting is a very different behavior from the current
>       practice concerning the publishing of IPv4 address resource
>       records,
>
>    o  that it may create a two-tiered Internet,
>
>    o  that policies concerning whitelisting and de-whitelisting are
>       opaque,
>
>
>
>
>
> Livingood                Expires August 26, 2011                [Page 5]
> 
> Internet-Draft   IPv6 AAAA DNS Whitelisting Implications   February 2011
>
>
>    o  that DNS whitelisting reduces interest in the deployment of IPv6,

Well, it certainly suggests that there is a problem handling v4/v6 in dual stack 
environments cleanly.  And it certainly seems that dealing with the underlying 
problem would be better.

Beyond that, this appears to be a hack that is useful but not scalable.


>
>    o  that new operational and management burdens are created,

well, yeah...


>    o  and that the costs and negative implications of DNS whitelisting
>       outweigh the perceived benefits, compared to fixing underlying
>       impairments.
>
>    This document explores the reasons and motivations for DNS
>    whitelisting.  It also explores the outlined concerns regarding this
>    practice.  Readers will hopefully better understand what DNS
>    whitelisting is, why some parties are implementing it, and what
>    criticisms of the practice exist.



-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From sm@resistor.net  Sat Apr 30 16:26:52 2011
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 BCCAEE06E7; Sat, 30 Apr 2011 16:26:52 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v0HIJHBkm7io; Sat, 30 Apr 2011 16:26:47 -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 169A8E0593; Sat, 30 Apr 2011 16:26:46 -0700 (PDT)
Received: from subman.resistor.net (IDENT:sm@localhost [127.0.0.1]) by mx.elandsys.com (8.14.4/8.14.5.Beta0) with ESMTP id p3UNQbu7023592;  Sat, 30 Apr 2011 16:26:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1304206003; bh=VqNu3n3vUUefMc2nFhaviAxojX6gkyf+nz1NkLqk3VU=; h=Message-Id:X-Mailer:Date:To:From:Subject:Cc:In-Reply-To: References:Mime-Version:Content-Type; b=WiqAx0xQyiJ8wJG1/TZKHTdWuQENOtLqZA2zM5d9kCvm/srgEO+/fUM8+aZNYhZd4 xoxInkAcHnkrE9v2VZMpNK1dxD4y4gF87LeQceI6XaXzYg+9t+aRB7fHYkXJAZpQOl rCM78O0zRkY3J3eu7GyWAQ2Litw1TbWirQ4Gafd8=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1304206003; bh=VqNu3n3vUUefMc2nFhaviAxojX6gkyf+nz1NkLqk3VU=; h=Message-Id:X-Mailer:Date:To:From:Subject:Cc:In-Reply-To: References:Mime-Version:Content-Type; b=cXX11dQ8WzuO/ImZup+qehevYfgdHQSUHw5VqWuf9bgunERMar7kLSq+XBzhQOuhr KrSfPVZzHCnQO5pyz9Y6d761SkleBA5R0ZWU/Eh3fvQbQF8nw4c1VLTYeZI6OAbmBW D3Z56tszX0US138JTRs0gElzVro3d1k3eDajhG4k=
Message-Id: <6.2.5.6.2.20110430150731.029f3fd8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 30 Apr 2011 15:41:15 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: rfc5953 (Transport Layer Security (TLS) Transport Model for the Simple Network Management Protocol (SNMP)) to Draft Standard
In-Reply-To: <20110419211456.203DAE084A@ietfc.amsl.com>
References: <20110419211456.203DAE084A@ietfc.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: isms@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, 30 Apr 2011 23:26:52 -0000

At 14:14 19-04-2011, The IESG wrote:
>The IESG has received a request from the isms WG (isms) to consider the
>following document:
>
>- 'Transport Layer Security (TLS) Transport Model for the Simple Network
>    Management Protocol (SNMP) '
>   RFC 5953 as a Draft 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 2011-05-03. 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.
>
>This specification contains eight normative references to standards
>track documents of lower maturity: RFCs 1033, 3490, 3584, 4347, 4366,
>5246, 5280, and 5952.

In Section 7:

   "A hostname is always in US-ASCII (as per [RFC1033]);
    internationalized hostnames are encoded in US-ASCII as domain
    names after transformation via the ToASCII operation specified
    in [RFC3490]."

As a quick comment, RFC 1033 is a down-ref.  A better reference is 
RFC 1123.  As it is part of STD 3, a down-ref is no longer 
needed.  The reference to RFC 3490 could be updated to RFC 
5890.  That also avoids a down-ref in a Draft Standard to a document 
that has an Obsolete status.

Regards,
-sm 

