
From stpeter@stpeter.im  Wed Sep  1 14:10:10 2010
Return-Path: <stpeter@stpeter.im>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4729F3A69CD for <apps-discuss@core3.amsl.com>; Wed,  1 Sep 2010 14:10:10 -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.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zlu+kCsKjeeT for <apps-discuss@core3.amsl.com>; Wed,  1 Sep 2010 14:10:02 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id 299A53A6910 for <apps-discuss@ietf.org>; Wed,  1 Sep 2010 14:10:02 -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 6509F400EE for <apps-discuss@ietf.org>; Wed,  1 Sep 2010 15:13:33 -0600 (MDT)
Message-ID: <4C7EC146.8030906@stpeter.im>
Date: Wed, 01 Sep 2010 15:10:30 -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.1.11) Gecko/20100711 Thunderbird/3.0.6
MIME-Version: 1.0
To: "apps-discuss@ietf.org" <apps-discuss@ietf.org>
X-Enigmail-Version: 1.0.1
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: [apps-discuss] AppsArea BoFs at IETF 79
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Sep 2010 21:10:10 -0000

Folks, if you would like to hold a birds-of-a-feather (BoF) session at
IETF 79, time is running short. The cutoff date is Monday, September 13:

http://www.ietf.org/meeting/cutoff-dates-2010.html#IETF79

Instructions are here:

http://www.ietf.org/iesg/bof-procedures.html

Alexey and I welcome BoF proposals -- feel free to send them directly to
your friendly Area Directors, or to this list for wider discussion.

Thanks!

Peter

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



From sm@elandsys.com  Wed Sep  1 17:40:20 2010
Return-Path: <sm@elandsys.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2E9F73A6A0F; Wed,  1 Sep 2010 17:40:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.966
X-Spam-Level: 
X-Spam-Status: No, score=-101.966 tagged_above=-999 required=5 tests=[AWL=0.633, 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 sm0LyF5Zhhws; Wed,  1 Sep 2010 17:40:18 -0700 (PDT)
Received: from mail.elandsys.com (mail.elandsys.com [208.69.177.125]) by core3.amsl.com (Postfix) with ESMTP id D64C63A6814; Wed,  1 Sep 2010 17:40:18 -0700 (PDT)
Received: from sm-PC.elandsys.com (miranda.controlfreak.co.za [196.36.80.182]) (authenticated bits=0) by mail.elandsys.com (8.13.8/8.13.8) with ESMTP id o820edmG029199; Wed, 1 Sep 2010 17:40:45 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=elandsys.com; s=mail; t=1283388047; bh=Ey9LtIf8+kmCQGhukjT0Gj5WkYg=; h=Message-Id:Date:To:From:Subject:Cc:Mime-Version:Content-Type; b=V+0vNVwZotbVlcMuyDc4nhsd/G/9XfztsAKO/qo/mviT6RSvv9YosH19uSzeQyuEQ oGyQchTUgYlGtgJf5/7K7pNgQ2eG8/IE0B4PKtpqHz/90Dd58yMh5vIeQXHaaPrU7C ZImvbx46kWBdbwwgld6gk38jgYJr7SpRHbNpveiE=
Message-Id: <6.2.5.6.2.20100901173558.07897f30@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 01 Sep 2010 17:40:16 -0700
To: apps-discuss@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: apps-review@ietf.org
Subject: [apps-discuss] Apps Area Review Team Report for August 2010
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Sep 2010 00:40:20 -0000

Hello,

The Applications Area Review Team provides semi-formal reviews of 
Internet-Drafts as a way to improve the quality of IETF 
specifications.  The members of the team are selected from the IETF 
community, especially from among active participants and recognized 
experts in the Applications Area.

The following reviews have been performed in August 2010:

  draft-gennai-smime-cnipa-pec-08 was reviewed by Dave Crocker.

Pending reviews:

  draft-ietf-netmod-dsdl-map-05 assigned to Aaron Stone
  draft-ietf-ecrit-lost-sync-08 assigned to Aaron Stone

Regards,
S. Moonesamy
On behalf of the Apps Review Team
http://www.apps.ietf.org/content/applications-area-review-team


From dhc@dcrocker.net  Sun Sep  5 08:57:43 2010
Return-Path: <dhc@dcrocker.net>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E40A23A6823 for <apps-discuss@core3.amsl.com>; Sun,  5 Sep 2010 08:57:43 -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 nNEn6gMrLpH1 for <apps-discuss@core3.amsl.com>; Sun,  5 Sep 2010 08:57:42 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id E16833A6818 for <discuss@apps.ietf.org>; Sun,  5 Sep 2010 08:57:42 -0700 (PDT)
Received: from [192.168.1.108] (cpe-76-175-134-213.socal.res.rr.com [76.175.134.213]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id o85Fw4ak024186 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <discuss@apps.ietf.org>; Sun, 5 Sep 2010 08:58:11 -0700
Message-ID: <4C83BE0C.6090802@dcrocker.net>
Date: Sun, 05 Sep 2010 08:58:04 -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.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: Apps Discuss <discuss@apps.ietf.org>
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, 05 Sep 2010 08:58:11 -0700 (PDT)
Subject: [apps-discuss] "organization's top level domain"
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Sep 2010 15:57:44 -0000

Folks,

Howdy.

I'm looking for a nomenclature suggestion...

RFC 2142 user the phrase "organization's top level domain".  This refers to the 
string that is delegated to the organization and provides the root of any 
sub-tree to the DNS that they create.  Around the world and around the DNS, this 
'root' will have two or more fields, such as bbiw.net or ucl.ac.uk.

An erratum has been filed on the phrase.  I take it as being a result of "top 
level domain" becoming entrenched to mean only the right-most field of a domain 
name. The stuff that is delegated from the root of the DNS.

The problem is that I do not know of an alternative name to use, when referring 
to the string that is delegated to an organization.  (And, no, I don not 
consider "string that is delegated to a domain" to be a candidate.)

I can't even think of one to suggest.

So I'm asking you folks what you recommend.

Thanks.

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From john-ietf@jck.com  Sun Sep  5 09:43:48 2010
Return-Path: <john-ietf@jck.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 712093A682B for <apps-discuss@core3.amsl.com>; Sun,  5 Sep 2010 09:43:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.455
X-Spam-Level: 
X-Spam-Status: No, score=-101.455 tagged_above=-999 required=5 tests=[AWL=-0.715, BAYES_20=-0.74, 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 899UsIyh645b for <apps-discuss@core3.amsl.com>; Sun,  5 Sep 2010 09:43:46 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 50FA83A67E1 for <discuss@apps.ietf.org>; Sun,  5 Sep 2010 09:43:44 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1OsIJt-000FXh-Bi; Sun, 05 Sep 2010 12:43:55 -0400
Date: Sun, 05 Sep 2010 12:43:39 -0400
From: John C Klensin <john-ietf@jck.com>
To: dcrocker@bbiw.net, Apps Discuss <discuss@apps.ietf.org>
Message-ID: <B998663D5F10090142884058@[192.168.1.128]>
In-Reply-To: <4C83BE0C.6090802@dcrocker.net>
References: <4C83BE0C.6090802@dcrocker.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Subject: Re: [apps-discuss] "organization's top level domain"
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Sep 2010 16:43:48 -0000

Dave,

I've occasionally used "enterprise primary domain" or
"organizational primary domain" in my writing, just to avoid the
use of "top-level".  I've also used some convolutions to
distinguish enterprise-managed domains from domains managed by
registries that serve many enterprises and that consist primary
or exclusively of delegation records and records needed to
support them, but that isn't quite the same thing and I've never
found crisp wording.  My recollection is that some folks in the
DNS community have used something like "all-delegation domains"
to refer to the next level up from what you are talking about,
but the term is not precisely accurate (given SOA records, glue,
etc.).

Also note that, if current ICANN plans continue, your "two or
more fields" requirement may soon be incorrect.  Under their
proposed model, nothing would prevent an organization that has
the needed operational capability and that is willing to spend
the money from acquiring a TLD and trying to put, e.g., MX
records in it.   The SMTP spec isn't happy about that idea, but
that is not a DNS issue and various specs that depend on SRV or
NAPTR records impose no such restrictions.   And, fwiw, one of
the few clear bits of DNS terminology (see below) is that what
you are referring to as a "field" is called a "label" and, as
far as I know, nothing else. 

I'd suggest raising this with the DNS Directorate (assuming it
is still functional) and/or the DNSOPS and DNSEXT WGs.  As you
probably know, there are periodic discussions about putting
together a document to specify and clarify all of the sloppy
terminology that surrounds the DNS --the question you ask is by
no measure the worse case.  I don't think the effort is going
anywhere, but perhaps someone is keeping a list of concepts that
need standard terminology and rigorous definitions some day. 

      john


--On Sunday, September 05, 2010 8:58 AM -0700 Dave CROCKER
<dhc@dcrocker.net> wrote:

> Folks,
> 
> Howdy.
> 
> I'm looking for a nomenclature suggestion...
> 
> RFC 2142 user the phrase "organization's top level domain".
> This refers to the string that is delegated to the
> organization and provides the root of any sub-tree to the DNS
> that they create.  Around the world and around the DNS, this
> 'root' will have two or more fields, such as bbiw.net or
> ucl.ac.uk.
> 
> An erratum has been filed on the phrase.  I take it as being a
> result of "top level domain" becoming entrenched to mean only
> the right-most field of a domain name. The stuff that is
> delegated from the root of the DNS.
> 
> The problem is that I do not know of an alternative name to
> use, when referring to the string that is delegated to an
> organization.  (And, no, I don not consider "string that is
> delegated to a domain" to be a candidate.)
> 
> I can't even think of one to suggest.
> 
> So I'm asking you folks what you recommend.
> 
> Thanks.
> 
> d/





From paul.hoffman@vpnc.org  Sun Sep  5 10:51:25 2010
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3F5173A681E for <apps-discuss@core3.amsl.com>; Sun,  5 Sep 2010 10:51:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.825
X-Spam-Level: 
X-Spam-Status: No, score=-99.825 tagged_above=-999 required=5 tests=[AWL=-0.379, BAYES_50=0.001, HELO_MISMATCH_COM=0.553, 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 6Z59dAzKIdDG for <apps-discuss@core3.amsl.com>; Sun,  5 Sep 2010 10:51:24 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 7216B3A67E1 for <discuss@apps.ietf.org>; Sun,  5 Sep 2010 10:51:24 -0700 (PDT)
Received: from [10.20.30.158] (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o85HppAA044798 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 5 Sep 2010 10:51:52 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p06240803c8a988ecfc71@[10.20.30.158]>
In-Reply-To: <B998663D5F10090142884058@[192.168.1.128]>
References: <4C83BE0C.6090802@dcrocker.net> <B998663D5F10090142884058@[192.168.1.128]>
Date: Sun, 5 Sep 2010 10:51:49 -0700
To: John C Klensin <john-ietf@jck.com>, dcrocker@bbiw.net, Apps Discuss <discuss@apps.ietf.org>
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
Subject: Re: [apps-discuss] "organization's top level domain"
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Sep 2010 17:51:25 -0000

At 12:43 PM -0400 9/5/10, John C Klensin wrote:
>I've occasionally used "enterprise primary domain" or
>"organizational primary domain" in my writing, just to avoid the
>use of "top-level".

Both of those seem good to me, for that very reason.

--Paul Hoffman, Director
--VPN Consortium

From peter@denic.de  Sun Sep  5 11:23:29 2010
Return-Path: <peter@denic.de>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5BB0A3A6825 for <apps-discuss@core3.amsl.com>; Sun,  5 Sep 2010 11:23:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.724
X-Spam-Level: 
X-Spam-Status: No, score=-4.724 tagged_above=-999 required=5 tests=[AWL=-0.889, BAYES_40=-0.185, HELO_EQ_DE=0.35, 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 Aa9pcCyJrRPK for <apps-discuss@core3.amsl.com>; Sun,  5 Sep 2010 11:23:27 -0700 (PDT)
Received: from office.denic.de (gw-office.denic.de [81.91.160.182]) by core3.amsl.com (Postfix) with ESMTP id 38C3A3A67E1 for <discuss@apps.ietf.org>; Sun,  5 Sep 2010 11:23:26 -0700 (PDT)
Received: from x27.adm.denic.de ([10.122.64.128]) by office.denic.de with esmtp  id 1OsJsg-0006SS-IB; Sun, 05 Sep 2010 20:23:54 +0200
Received: from localhost by x27.adm.denic.de with local  id 1OsJsg-0001HM-EK; Sun, 05 Sep 2010 20:23:54 +0200
Date: Sun, 5 Sep 2010 20:23:54 +0200
From: Peter Koch <pk@DENIC.DE>
To: Apps Discuss <discuss@apps.ietf.org>
Message-ID: <20100905182354.GB30466@x27.adm.denic.de>
Mail-Followup-To: Apps Discuss <discuss@apps.ietf.org>
References: <4C83BE0C.6090802@dcrocker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4C83BE0C.6090802@dcrocker.net>
User-Agent: Mutt/1.4.2.3i
Sender: Peter Koch <peter@denic.de>
Subject: Re: [apps-discuss] "organization's top level domain"
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Sep 2010 18:23:29 -0000

Hi Dave, all,

> The problem is that I do not know of an alternative name to use, when 
> referring to the string that is delegated to an organization.  (And, no, I 

the text in the RFC doesn't meet today's terminology, but it also isn't
(any longer) a good fit for operational reality. There is no 1:1 mapping
between organisation and domain (at whatever level) and the hierarchy
in the domain name space doesn't necessarily meet or imply organisational
hierarchy.  Therefore, I think the best way to deal with the erratum is
to postpone it for an update of the RFC.

That said, there are some recommendations in there that were good ideas at the
time but are out of sync with today's practice or the IETF's scope of
influence (see section 3; also mail addresses at "ra.net" are no longer
deliverable).  I'd suggest to declare this RFC "Historic" and, assuming enough
interest and momentum, work towards a BCP that deals with those remaining
mailboxes which are of importance today.

-Peter

From James.H.Manger@team.telstra.com  Sun Sep  5 19:47:12 2010
Return-Path: <James.H.Manger@team.telstra.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 794363A672F for <apps-discuss@core3.amsl.com>; Sun,  5 Sep 2010 19:47:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.489
X-Spam-Level: 
X-Spam-Status: No, score=-0.489 tagged_above=-999 required=5 tests=[AWL=0.412,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, RELAY_IS_203=0.994]
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 ZZy3WJ-C2Kw3 for <apps-discuss@core3.amsl.com>; Sun,  5 Sep 2010 19:47:09 -0700 (PDT)
Received: from ipxano.tcif.telstra.com.au (ipxano.tcif.telstra.com.au [203.35.82.200]) by core3.amsl.com (Postfix) with ESMTP id 8F20C3A65A6 for <discuss@apps.ietf.org>; Sun,  5 Sep 2010 19:47:06 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.56,322,1280671200"; d="scan'208";a="12871381"
Received: from unknown (HELO ipcbni.tcif.telstra.com.au) ([10.97.216.204]) by ipoani.tcif.telstra.com.au with ESMTP; 06 Sep 2010 12:47:29 +1000
X-IronPort-AV: E=McAfee;i="5400,1158,6096"; a="7921469"
Received: from wsmsg3705.srv.dir.telstra.com ([172.49.40.203]) by ipcbni.tcif.telstra.com.au with ESMTP; 06 Sep 2010 12:47:28 +1000
Received: from WSMSG3153V.srv.dir.telstra.com ([172.49.40.159]) by WSMSG3705.srv.dir.telstra.com ([172.49.40.203]) with mapi; Mon, 6 Sep 2010 12:47:28 +1000
From: "Manger, James H" <James.H.Manger@team.telstra.com>
To: "dcrocker@bbiw.net" <dcrocker@bbiw.net>, Apps Discuss <discuss@apps.ietf.org>
Date: Mon, 6 Sep 2010 12:47:26 +1000
Thread-Topic: [apps-discuss] "organization's top level domain"
Thread-Index: ActNEygSjfUTzjS5TwehTcqp6SoWDAAWQ3jw
Message-ID: <255B9BB34FB7D647A506DC292726F6E1126A3190E0@WSMSG3153V.srv.dir.telstra.com>
References: <4C83BE0C.6090802@dcrocker.net>
In-Reply-To: <4C83BE0C.6090802@dcrocker.net>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-AU
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [apps-discuss] "organization's top level domain"
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Sep 2010 02:47:13 -0000

Dave,

Another phrase could be an "organization's domain immediately below a publi=
c suffix", where a public suffix is defined by referring to http://publicsu=
ffix.org/. That isn't a short catchy phrase, but at least the "public suffi=
x" portion is well defined.

--
James Manger

-----Original Message-----
From: apps-discuss-bounces@ietf.org [mailto:apps-discuss-bounces@ietf.org] =
On Behalf Of Dave CROCKER
Sent: Monday, 6 September 2010 1:58 AM
To: Apps Discuss
Subject: [apps-discuss] "organization's top level domain"

Folks,

Howdy.

I'm looking for a nomenclature suggestion...

RFC 2142 user the phrase "organization's top level domain".  This refers to=
 the
string that is delegated to the organization and provides the root of any
sub-tree to the DNS that they create.  Around the world and around the DNS,=
 this
'root' will have two or more fields, such as bbiw.net or ucl.ac.uk.

An erratum has been filed on the phrase.  I take it as being a result of "t=
op
level domain" becoming entrenched to mean only the right-most field of a do=
main
name. The stuff that is delegated from the root of the DNS.

The problem is that I do not know of an alternative name to use, when refer=
ring
to the string that is delegated to an organization.  (And, no, I don not
consider "string that is delegated to a domain" to be a candidate.)

I can't even think of one to suggest.

So I'm asking you folks what you recommend.

Thanks.

d/
--

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From ajs@shinkuro.com  Mon Sep  6 06:51:55 2010
Return-Path: <ajs@shinkuro.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E9DBD3A6942 for <apps-discuss@core3.amsl.com>; Mon,  6 Sep 2010 06:51:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.622
X-Spam-Level: 
X-Spam-Status: No, score=-100.622 tagged_above=-999 required=5 tests=[AWL=-0.437, BAYES_40=-0.185, 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 3dIkwjnFDYD1 for <apps-discuss@core3.amsl.com>; Mon,  6 Sep 2010 06:51:46 -0700 (PDT)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id 2964C3A693F for <apps-discuss@ietf.org>; Mon,  6 Sep 2010 06:51:45 -0700 (PDT)
Received: from crankycanuck.ca (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 2D2181ECB41D for <apps-discuss@ietf.org>; Mon,  6 Sep 2010 13:52:10 +0000 (UTC)
Date: Mon, 6 Sep 2010 09:52:08 -0400
From: Andrew Sullivan <ajs@shinkuro.com>
To: apps-discuss@ietf.org
Message-ID: <20100906135207.GU34607@shinkuro.com>
References: <4C83BE0C.6090802@dcrocker.net> <B998663D5F10090142884058@[192.168.1.128]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <B998663D5F10090142884058@[192.168.1.128]>
User-Agent: Mutt/1.5.18 (2008-05-17)
Subject: Re: [apps-discuss] "organization's top level domain"
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Sep 2010 13:51:55 -0000

On Sun, Sep 05, 2010 at 12:43:39PM -0400, John C Klensin wrote:
> found crisp wording.  My recollection is that some folks in the
> DNS community have used something like "all-delegation domains"
> to refer to the next level up from what you are talking about,
> but the term is not precisely accurate (given SOA records, glue,
> etc.).

That's why we use the term "delegation-centric" as opposed to
"all-delegation".  Even a delegation-centric domain will likely have A
records, for glue.

> NAPTR records impose no such restrictions.   And, fwiw, one of
> the few clear bits of DNS terminology (see below) is that what
> you are referring to as a "field" is called a "label" and, as
> far as I know, nothing else. 

Yes.

> I'd suggest raising this with the DNS Directorate (assuming it
> is still functional) and/or the DNSOPS and DNSEXT WGs.  As you
> probably know, there are periodic discussions about putting
> together a document to specify and clarify all of the sloppy
> terminology that surrounds the DNS --the question you ask is by
> no measure the worse case.  I don't think the effort is going
> anywhere, but perhaps someone is keeping a list of concepts that
> need standard terminology and rigorous definitions some day. 

We tried to do that, in dnsext, about the time that I was asked to
serve as co-chair.  Indeed, I think part of the reason for appointing
a co-chair and semi-reviving the WG was because of the potential work
represented by such an all-encompassing terminological effort.  The
effort went nowhere: of the various volunteers we had as co-editors,
almost none of them produced any text.  Neither did anyone else.  So I
think it won't happen.

(As an aside, If someone wants to take this on, I think it would be
worthwhile.  But the truth is that I think it can't be done by a
volunteer: it needs to be someone paid for a short while to focus on
this problem and to produce a meaningful set of initial drafts,
because it's an enormous task.)

As for Dave's problem: you could close one can of worms by opening
another.  Call it the "organization's root."  ;-) Seriously, I don't
believe there's a good term for this, and I'd be delighted if someone
offered one.  But keep in mind that you might face abuse of the term.
Peter Koch in particular gets quite annoyed when people talk about a
host being "in" a domain, especially when the search path is what's
used to determine that.  I'd be amazed if people didn't start using
any term for "part of the namespace tree delegated to the
organization" to stand in for "part of the namespace tree in which
organization's hosts live."

A


-- 
Andrew Sullivan
ajs@shinkuro.com
Shinkuro, Inc.

From ajs@shinkuro.com  Mon Sep  6 06:54:39 2010
Return-Path: <ajs@shinkuro.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E1B0A3A692B for <apps-discuss@core3.amsl.com>; Mon,  6 Sep 2010 06:54:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.824
X-Spam-Level: 
X-Spam-Status: No, score=-101.824 tagged_above=-999 required=5 tests=[AWL=0.775, 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 yM5jb5KeVYXD for <apps-discuss@core3.amsl.com>; Mon,  6 Sep 2010 06:54:38 -0700 (PDT)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id 4F5463A67D6 for <apps-discuss@ietf.org>; Mon,  6 Sep 2010 06:54:38 -0700 (PDT)
Received: from crankycanuck.ca (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 B2CE61ECB41D for <apps-discuss@ietf.org>; Mon,  6 Sep 2010 13:55:06 +0000 (UTC)
Date: Mon, 6 Sep 2010 09:55:04 -0400
From: Andrew Sullivan <ajs@shinkuro.com>
To: apps-discuss@ietf.org
Message-ID: <20100906135504.GV34607@shinkuro.com>
References: <4C83BE0C.6090802@dcrocker.net> <255B9BB34FB7D647A506DC292726F6E1126A3190E0@WSMSG3153V.srv.dir.telstra.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <255B9BB34FB7D647A506DC292726F6E1126A3190E0@WSMSG3153V.srv.dir.telstra.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Subject: Re: [apps-discuss] "organization's top level domain"
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Sep 2010 13:54:40 -0000

On Mon, Sep 06, 2010 at 12:47:26PM +1000, Manger, James H wrote:
> Dave,
> 
> Another phrase could be an "organization's domain immediately below a public suffix", where a public suffix is defined by referring to http://publicsuffix.org/. That isn't a short catchy phrase, but at least the "public suffix" portion is well defined.
> 

Please, no!  In my (quite ornery, on this topic) opinion, the list at
publicsuffix.org is a miserable hack that is doomed to failure and is
wrong in principle.  I've made that rant before, however, so I won't
repeat it here.  And even if you liked the publicsuffix stuff, it's
completely wrong for these purposes.

A

-- 
Andrew Sullivan
ajs@shinkuro.com
Shinkuro, Inc.

From claudio.allocchio@garr.it  Mon Sep  6 07:59:06 2010
Return-Path: <claudio.allocchio@garr.it>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2FF4E3A6819 for <apps-discuss@core3.amsl.com>; Mon,  6 Sep 2010 07:59:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.881
X-Spam-Level: *
X-Spam-Status: No, score=1.881 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
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 ErsgHSG6JeQW for <apps-discuss@core3.amsl.com>; Mon,  6 Sep 2010 07:59:05 -0700 (PDT)
Received: from cyrus.dir.garr.it (cyrus.dir.garr.it [IPv6:2001:760:0:158::29]) by core3.amsl.com (Postfix) with ESMTP id 1BF2D3A67B5 for <apps-discuss@ietf.org>; Mon,  6 Sep 2010 07:59:03 -0700 (PDT)
Received: from mac-allocchio3.elettra.trieste.it (mac-allocchio3.elettra.trieste.it [140.105.2.18]) by cyrus.dir.garr.it (8.14.4/8.14.4) with ESMTP id o86ExTo8057839 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <apps-discuss@ietf.org>; Mon, 6 Sep 2010 16:59:29 +0200 (CEST)
Date: Mon, 6 Sep 2010 16:40:47 +0200 (CEST)
From: Claudio Allocchio <Claudio.Allocchio@garr.it>
X-X-Sender: claudio@mac-allocchio3.elettra.trieste.it
To: apps-discuss@ietf.org, subir@research.Telcordia.com, gabor.bajko@nokia.com, vijay@wichorus.com, iesg@ietf.org
Message-ID: <Pine.OSX.4.64.1009061616080.2959@mac-allocchio3.elettra.trieste.it>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
ReSent-Date: Mon, 6 Sep 2010 16:59:20 +0200 (CEST)
ReSent-From: Claudio Allocchio <claudio.allocchio@garr.it>
ReSent-To: apps-discuss@ietf.org
ReSent-Subject: apps-team review of draft-das-mipshop-andsf-dhcp-options
ReSent-Message-ID: <Pine.OSX.4.64.1009061659200.2959@mac-allocchio3.elettra.trieste.it>
Subject: [apps-discuss] apps-team review of draft-das-mipshop-andsf-dhcp-options
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Sep 2010 14:59:06 -0000

I have been selected as the Applications Area Review Team reviewer for 
this draft (for background on apps-review, please see 
http://www.apps.ietf.org/content/applications-area-review-team).

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

Document: draft-das-mipshop-andsf-dhcp-options
Reviewer: Claudio Allocchio (GARR, Italian Research and Academic Network)
Review Date: 2010-09-06
IETF Last Call Date: 2010-08-09 (?)
IESG Telechat Date: 2010-09-09

Summary: This draft has not any specific Application Area issues (use of 
XML, date/time format, URIs, Internationalization conformance, IDNA, 
etc.), hence fro this point of view it is ready for publication as 
Proposed Standard.

Major Issues: None.

Minor Issues:

- section 2: maybe I'm just overconcerned with clarity, but I would 
rephrase the second senctence and schema repeating "IPv4 address" instead 
of only "IP address(es)"

The Option begins with an option code followed by a length and one
or more IPv4 addresses. The option layout is depicted below:

      0  1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
                                      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                      | Option Code   |    Length     |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                     IPv4 Address                              |
      .                                                               .
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

- Section 3:

same as above: use "IPv6 address(es)" all the time, instead of only "IP 
address(es)".

Nits: None.

I hope this helps!   ;-)

Best Regards!
Claudio

------------------------------------------------------------------------------
Claudio Allocchio             G   A   R   R          Claudio.Allocchio@garr.it
                         Senior Technical Officer
tel: +39 040 3758523      Italian Academic and       G=Claudio; S=Allocchio;
fax: +39 040 3758565        Research Network         P=garr; A=garr; C=it;

            PGP Key: http://www.cert.garr.it/PGP/keys.php3#ca

From john-ietf@jck.com  Mon Sep  6 09:09:36 2010
Return-Path: <john-ietf@jck.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A9DF83A6783 for <apps-discuss@core3.amsl.com>; Mon,  6 Sep 2010 09:09:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.623
X-Spam-Level: 
X-Spam-Status: No, score=-101.623 tagged_above=-999 required=5 tests=[AWL=-0.513, BAYES_05=-1.11, 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 XC9OgAEnrNN7 for <apps-discuss@core3.amsl.com>; Mon,  6 Sep 2010 09:09:32 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id D1BB63A67B5 for <apps-discuss@ietf.org>; Mon,  6 Sep 2010 09:09:30 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1OseGD-000CQR-2h; Mon, 06 Sep 2010 12:09:34 -0400
Date: Mon, 06 Sep 2010 12:09:18 -0400
From: John C Klensin <john-ietf@jck.com>
To: Andrew Sullivan <ajs@shinkuro.com>, apps-discuss@ietf.org
Message-ID: <6F3DDCE5D87E04A3F2DC80B1@[192.168.1.128]>
In-Reply-To: <20100906135207.GU34607@shinkuro.com>
References: <4C83BE0C.6090802@dcrocker.net> <B998663D5F10090142884058@[192.168.1.128]> <20100906135207.GU34607@shinkuro.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
Subject: Re: [apps-discuss] "organization's top level domain"
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Sep 2010 16:09:36 -0000

--On Monday, September 06, 2010 9:52 AM -0400 Andrew Sullivan
<ajs@shinkuro.com> wrote:

>...
> (As an aside, If someone wants to take this on, I think it
> would be worthwhile.  But the truth is that I think it can't
> be done by a volunteer: it needs to be someone paid for a
> short while to focus on this problem and to produce a
> meaningful set of initial drafts, because it's an enormous
> task.)

It seems to me that this is work that ICANN ought to be willing
to support because terminology confusion has the potential (and
some history) of causing their discussions about policy to
deteriorate into total confusion.  I understand that they are
pleading poverty whenever suggestions for work that might
actually improve their ability to make progress comes up, but
perhaps this would be a small enough exception in their
multi-million dollar budget to be possible.  Anyone know a
convenient Board member or two?

> As for Dave's problem: you could close one can of worms by
> opening another.  Call it the "organization's root."  ;-)
> Seriously, I don't believe there's a good term for this, and
> I'd be delighted if someone offered one.  But keep in mind
> that you might face abuse of the term. Peter Koch in
> particular gets quite annoyed when people talk about a host
> being "in" a domain, especially when the search path is what's
> used to determine that.  I'd be amazed if people didn't start
> using any term for "part of the namespace tree delegated to the
> organization" to stand in for "part of the namespace tree in
> which organization's hosts live."

And, of course, even that sort of concept/term is vastly
complicated by the existence of aliases in general and tree or
sub-tree aliases in particular.

While anything can be abused and probably will, any clear set of
definitions would probably be helpful even if they were all
debatable when compared with contemporary practice (which is all
over the map).

    john


From dhc@dcrocker.net  Tue Sep  7 09:51:32 2010
Return-Path: <dhc@dcrocker.net>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E0F5C3A6A66 for <apps-discuss@core3.amsl.com>; Tue,  7 Sep 2010 09:51:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.518
X-Spam-Level: 
X-Spam-Status: No, score=-5.518 tagged_above=-999 required=5 tests=[AWL=-0.778, BAYES_20=-0.74, 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 fL+lzPZI08Jy for <apps-discuss@core3.amsl.com>; Tue,  7 Sep 2010 09:51:29 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id C15DD3A6A56 for <discuss@apps.ietf.org>; Tue,  7 Sep 2010 09:51:29 -0700 (PDT)
Received: from [192.168.1.4] (ppp-68-122-73-240.dsl.pltn13.pacbell.net [68.122.73.240]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id o87Gpr8N017889 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <discuss@apps.ietf.org>; Tue, 7 Sep 2010 09:51:58 -0700
Message-ID: <4C866DA9.8080302@dcrocker.net>
Date: Tue, 07 Sep 2010 09:51:53 -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.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: Apps Discuss <discuss@apps.ietf.org>
References: <4C83BE0C.6090802@dcrocker.net> <20100905182354.GB30466@x27.adm.denic.de>
In-Reply-To: <20100905182354.GB30466@x27.adm.denic.de>
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, 07 Sep 2010 09:51:58 -0700 (PDT)
Subject: Re: [apps-discuss] "organization's top level domain"
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Sep 2010 16:51:32 -0000

Folks,

The main challenge in selecting a term is that it both means what we want it to 
mean AND it is likely to get widely used.

"Organizational primary domain" invites an interpretation that it refers to one 
among a set of aliases, rather than the 'base' of an organization's name tree. 
By using the word 'primary', we have to ask what the average person would assume 
is meant by "secondary domain", and I doubt it would be taken to mean "one level 
down the tree".

On further reflection, I'm inclined to suggest:

     "Organization's delegated domain"

Thoughts?

d/


-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From paul.hoffman@vpnc.org  Tue Sep  7 09:57:54 2010
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B89B73A6A80 for <apps-discuss@core3.amsl.com>; Tue,  7 Sep 2010 09:57:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.825
X-Spam-Level: 
X-Spam-Status: No, score=-99.825 tagged_above=-999 required=5 tests=[AWL=-0.379, BAYES_50=0.001, HELO_MISMATCH_COM=0.553, 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 zsSi6-8nrdLg for <apps-discuss@core3.amsl.com>; Tue,  7 Sep 2010 09:57:54 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id EB1E23A6A7E for <discuss@apps.ietf.org>; Tue,  7 Sep 2010 09:57:53 -0700 (PDT)
Received: from [10.20.30.158] (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o87GwK6h079613 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 7 Sep 2010 09:58:21 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p06240850c8ac1fa178a5@[10.20.30.158]>
In-Reply-To: <4C866DA9.8080302@dcrocker.net>
References: <4C83BE0C.6090802@dcrocker.net> <20100905182354.GB30466@x27.adm.denic.de> <4C866DA9.8080302@dcrocker.net>
Date: Tue, 7 Sep 2010 09:58:19 -0700
To: dcrocker@bbiw.net, Apps Discuss <discuss@apps.ietf.org>
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
Subject: Re: [apps-discuss] "organization's top level domain"
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Sep 2010 16:57:54 -0000

At 9:51 AM -0700 9/7/10, Dave CROCKER wrote:
>The main challenge in selecting a term is that it both means what we want it to mean AND it is likely to get widely used.
>
>"Organizational primary domain" invites an interpretation that it refers to one among a set of aliases, rather than the 'base' of an organization's name tree. By using the word 'primary', we have to ask what the average person would assume is meant by "secondary domain", and I doubt it would be taken to mean "one level down the tree".
>
>On further reflection, I'm inclined to suggest:
>
>    "Organization's delegated domain"
>
>Thoughts?

+1

--Paul Hoffman, Director
--VPN Consortium

From dhc@dcrocker.net  Tue Sep  7 10:00:33 2010
Return-Path: <dhc@dcrocker.net>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 16D043A66B4 for <apps-discuss@core3.amsl.com>; Tue,  7 Sep 2010 10:00:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.438
X-Spam-Level: 
X-Spam-Status: No, score=-6.438 tagged_above=-999 required=5 tests=[AWL=0.161,  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 ywHROZHR9TJL for <apps-discuss@core3.amsl.com>; Tue,  7 Sep 2010 10:00:28 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id 6C0C33A67F3 for <discuss@apps.ietf.org>; Tue,  7 Sep 2010 10:00:28 -0700 (PDT)
Received: from [192.168.1.4] (ppp-68-122-73-240.dsl.pltn13.pacbell.net [68.122.73.240]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id o87H0oYn018260 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 7 Sep 2010 10:00:56 -0700
Message-ID: <4C866FC2.1010503@dcrocker.net>
Date: Tue, 07 Sep 2010 10:00:50 -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.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: Peter Koch <pk@denic.de>
References: <4C83BE0C.6090802@dcrocker.net> <20100905182354.GB30466@x27.adm.denic.de>
In-Reply-To: <20100905182354.GB30466@x27.adm.denic.de>
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, 07 Sep 2010 10:00:56 -0700 (PDT)
Cc: Apps Discuss <discuss@apps.ietf.org>
Subject: [apps-discuss] RFC2142 revusuib
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Sep 2010 17:00:33 -0000

On 9/5/2010 11:23 AM, Peter Koch wrote:
> the text in the RFC doesn't meet today's terminology, but it also isn't
> (any longer) a good fit for operational reality. There is no 1:1 mapping

My original query concerned a specific bit of nomenclature, to resolve an 
erratum.  I also think it worthwhile to try to establish common language for a 
construct the is important.

A larger discussion about the document is fine, but is quite independent of the 
original question.  Hence the new Subject.


> between organisation and domain (at whatever level) and the hierarchy
> in the domain name space doesn't necessarily meet or imply organisational
> hierarchy.  Therefore, I think the best way to deal with the erratum is
> to postpone it for an update of the RFC.

My current thinking is that a document revision effort should have two parts. 
One is to define an IANA registry, so that incremental change is possible, going 
forward.  The second is to review the document's existing definitions and modify 
them based on community review.

If there is meaningful community interest, I'd be glad to pursue that.


> That said, there are some recommendations in there that were good ideas at the
> time but are out of sync with today's practice or the IETF's scope of
> influence (see section 3; also mail addresses at "ra.net" are no longer
> deliverable).  I'd suggest to declare this RFC "Historic" and, assuming enough
> interest and momentum, work towards a BCP that deals with those remaining
> mailboxes which are of importance today.


I don't understand the reference to "scope of influence". I would have guessed 
it meant that you think we should not recommend best practice, but the end of 
your paragraph makes clear that you don't mean that.

d?


-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From Claudio.Allocchio@garr.it  Mon Sep  6 07:40:28 2010
Return-Path: <Claudio.Allocchio@garr.it>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7CB643A6943; Mon,  6 Sep 2010 07:40:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.881
X-Spam-Level: *
X-Spam-Status: No, score=1.881 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
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 05BfxM0tLWbe; Mon,  6 Sep 2010 07:40:26 -0700 (PDT)
Received: from cyrus.dir.garr.it (cyrus.dir.garr.it [IPv6:2001:760:0:158::29]) by core3.amsl.com (Postfix) with ESMTP id 6FE223A6915; Mon,  6 Sep 2010 07:40:26 -0700 (PDT)
Received: from mac-allocchio3.elettra.trieste.it (mac-allocchio3.elettra.trieste.it [140.105.2.18]) by cyrus.dir.garr.it (8.14.4/8.14.4) with ESMTP id o86EelG6057347 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 6 Sep 2010 16:40:48 +0200 (CEST)
Date: Mon, 6 Sep 2010 16:40:47 +0200 (CEST)
From: Claudio Allocchio <Claudio.Allocchio@garr.it>
X-X-Sender: claudio@mac-allocchio3.elettra.trieste.it
To: apps-discuss@ietf.org, subir@research.Telcordia.com, gabor.bajko@nokia.com, vijay@wichorus.com, iesg@ietf.org
Message-ID: <Pine.OSX.4.64.1009061616080.2959@mac-allocchio3.elettra.trieste.it>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Mailman-Approved-At: Tue, 07 Sep 2010 10:28:18 -0700
Subject: [apps-discuss] apps-team review of draft-das-mipshop-andsf-dhcp-options
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Sep 2010 14:40:28 -0000

I have been selected as the Applications Area Review Team reviewer for 
this draft (for background on apps-review, please see 
http://www.apps.ietf.org/content/applications-area-review-team).

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

Document: draft-das-mipshop-andsf-dhcp-options
Reviewer: Claudio Allocchio (GARR, Italian Research and Academic Network)
Review Date: 2010-09-06
IETF Last Call Date: 2010-08-09 (?)
IESG Telechat Date: 2010-09-09

Summary: This draft has not any specific Application Area issues (use of 
XML, date/time format, URIs, Internationalization conformance, IDNA, 
etc.), hence fro this point of view it is ready for publication as 
Proposed Standard.

Major Issues: None.

Minor Issues:

- section 2: maybe I'm just overconcerned with clarity, but I would 
rephrase the second senctence and schema repeating "IPv4 address" instead 
of only "IP address(es)"

The Option begins with an option code followed by a length and one
or more IPv4 addresses. The option layout is depicted below:

      0  1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
                                      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                      | Option Code   |    Length     |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                     IPv4 Address                              |
      .                                                               .
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

- Section 3:

same as above: use "IPv6 address(es)" all the time, instead of only "IP 
address(es)".

Nits: None.

I hope this helps!   ;-)

Best Regards!
Claudio

------------------------------------------------------------------------------
Claudio Allocchio             G   A   R   R          Claudio.Allocchio@garr.it
                         Senior Technical Officer
tel: +39 040 3758523      Italian Academic and       G=Claudio; S=Allocchio;
fax: +39 040 3758565        Research Network         P=garr; A=garr; C=it;

            PGP Key: http://www.cert.garr.it/PGP/keys.php3#ca

From ajs@shinkuro.com  Tue Sep  7 11:12:44 2010
Return-Path: <ajs@shinkuro.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 92F0E3A6A8A for <apps-discuss@core3.amsl.com>; Tue,  7 Sep 2010 11:12:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.84
X-Spam-Level: 
X-Spam-Status: No, score=-101.84 tagged_above=-999 required=5 tests=[AWL=0.759, 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 SbpGweg+Ye-b for <apps-discuss@core3.amsl.com>; Tue,  7 Sep 2010 11:12:43 -0700 (PDT)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id 8D19F3A6902 for <apps-discuss@ietf.org>; Tue,  7 Sep 2010 11:12:43 -0700 (PDT)
Received: from crankycanuck.ca (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 BABBA1ECB41D for <apps-discuss@ietf.org>; Tue,  7 Sep 2010 18:13:10 +0000 (UTC)
Date: Tue, 7 Sep 2010 14:13:09 -0400
From: Andrew Sullivan <ajs@shinkuro.com>
To: apps-discuss@ietf.org
Message-ID: <20100907181308.GN489@shinkuro.com>
References: <4C83BE0C.6090802@dcrocker.net> <20100905182354.GB30466@x27.adm.denic.de> <4C866DA9.8080302@dcrocker.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4C866DA9.8080302@dcrocker.net>
User-Agent: Mutt/1.5.18 (2008-05-17)
Subject: Re: [apps-discuss] "organization's top level domain"
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Sep 2010 18:12:44 -0000

On Tue, Sep 07, 2010 at 09:51:53AM -0700, Dave CROCKER wrote:
> On further reflection, I'm inclined to suggest:
>
>     "Organization's delegated domain"

This has the conspicuous advantage that it is technically exactly
correct.  One teeny quibble: the discussion has suggested (at least to
me) that there is one such domain, whereas we know there may be (and
often is) more than one.  Any way to point out that there may well be
more than one, but that each one is effectively separate and managed
independently (modulo aliasing techniques like CNAME, DNAME, and
whatever the wild bunch over in DNSEXT comes up with next)?

A

-- 
Andrew Sullivan
ajs@shinkuro.com
Shinkuro, Inc.

From john-ietf@jck.com  Tue Sep  7 11:29:24 2010
Return-Path: <john-ietf@jck.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9DC183A6893 for <apps-discuss@core3.amsl.com>; Tue,  7 Sep 2010 11:29:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.356
X-Spam-Level: 
X-Spam-Status: No, score=-102.356 tagged_above=-999 required=5 tests=[AWL=0.243, 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 tRkNm-968PDA for <apps-discuss@core3.amsl.com>; Tue,  7 Sep 2010 11:29:23 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 601FE3A682A for <apps-discuss@ietf.org>; Tue,  7 Sep 2010 11:29:23 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1Ot2vW-00092J-WC; Tue, 07 Sep 2010 14:29:51 -0400
Date: Tue, 07 Sep 2010 14:29:50 -0400
From: John C Klensin <john-ietf@jck.com>
To: Andrew Sullivan <ajs@shinkuro.com>, apps-discuss@ietf.org
Message-ID: <9A9E793D54FF76A74CA9E772@[192.168.1.128]>
In-Reply-To: <20100907181308.GN489@shinkuro.com>
References: <4C83BE0C.6090802@dcrocker.net> <20100905182354.GB30466@x27.adm.denic.de> <4C866DA9.8080302@dcrocker.net> <20100907181308.GN489@shinkuro.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
Subject: Re: [apps-discuss] "organization's top level domain"
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Sep 2010 18:29:24 -0000

--On Tuesday, September 07, 2010 2:13 PM -0400 Andrew Sullivan
<ajs@shinkuro.com> wrote:

> On Tue, Sep 07, 2010 at 09:51:53AM -0700, Dave CROCKER wrote:
>> On further reflection, I'm inclined to suggest:
>> 
>>     "Organization's delegated domain"
> 
> This has the conspicuous advantage that it is technically
> exactly correct.  One teeny quibble: the discussion has
> suggested (at least to me) that there is one such domain,
> whereas we know there may be (and often is) more than one.
> Any way to point out that there may well be more than one, but
> that each one is effectively separate and managed
> independently (modulo aliasing techniques like CNAME, DNAME,
> and whatever the wild bunch over in DNSEXT comes up with next)?

As long as you are sure that "delegated" won't run afoul of
assorted "variant" and/or "symmetric" theories.  And I'll let
you explain those to this lucky group.

There is another little trap, which is why I've often used
"enterprise" rather than "organization" and that is having
subsidiary organizations delegated by some primary one.  That
leads one to "primary organization's primary delegated...",
which hurts the head, but nothing is perfect.

    john


From pk@DENIC.DE  Tue Sep  7 11:35:30 2010
Return-Path: <pk@DENIC.DE>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2B8A73A6957 for <apps-discuss@core3.amsl.com>; Tue,  7 Sep 2010 11:35:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.898
X-Spam-Level: 
X-Spam-Status: No, score=-5.898 tagged_above=-999 required=5 tests=[AWL=0.351,  BAYES_00=-2.599, HELO_EQ_DE=0.35, 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 pyFy8JoBjOhw for <apps-discuss@core3.amsl.com>; Tue,  7 Sep 2010 11:35:29 -0700 (PDT)
Received: from office.denic.de (gw-office.denic.de [81.91.160.182]) by core3.amsl.com (Postfix) with ESMTP id D473A3A6950 for <apps-discuss@ietf.org>; Tue,  7 Sep 2010 11:35:28 -0700 (PDT)
Received: from unknown.office.denic.de ([10.122.66.129]) by office.denic.de with esmtp  id 1Ot31Q-0005UT-8M; Tue, 07 Sep 2010 20:35:56 +0200
Received: by unknown.office.denic.de (Postfix, from userid 501) id 144536BE21F; Tue,  7 Sep 2010 20:35:55 +0200 (CEST)
Date: Tue, 7 Sep 2010 20:35:55 +0200
From: Peter Koch <pk@DENIC.DE>
To: apps-discuss@ietf.org
Message-ID: <20100907183555.GJ15670@unknown.office.denic.de>
Mail-Followup-To: apps-discuss@ietf.org
References: <4C83BE0C.6090802@dcrocker.net> <20100905182354.GB30466@x27.adm.denic.de> <4C866DA9.8080302@dcrocker.net> <20100907181308.GN489@shinkuro.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20100907181308.GN489@shinkuro.com>
User-Agent: Mutt/1.4.2.1i
Subject: Re: [apps-discuss] "organization's top level domain"
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Sep 2010 18:35:30 -0000

On Tue, Sep 07, 2010 at 02:13:09PM -0400, Andrew Sullivan wrote:

> >     "Organization's delegated domain"
> 
> This has the conspicuous advantage that it is technically exactly
> correct.

except where it isn't, probably depending on the exact meaning of
"delegated".  There is at least one (larger) TLD where registered
domains may or may not be delegated. DNS data for those not delegated will be
maintained within the TLD zone.  In the DNS, delegation is about creating
zone boundaries, but the presence or absence of those boundaries is
no indication of administrative (in the broader, not technical sense)
boundaries.  

-Peter

From bobwyman@gmail.com  Tue Sep  7 11:39:11 2010
Return-Path: <bobwyman@gmail.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 70A243A6958 for <apps-discuss@core3.amsl.com>; Tue,  7 Sep 2010 11:39:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.292
X-Spam-Level: 
X-Spam-Status: No, score=0.292 tagged_above=-999 required=5 tests=[AWL=2.268,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001]
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 FZBm5q+wMCSA for <apps-discuss@core3.amsl.com>; Tue,  7 Sep 2010 11:39:09 -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 864483A6966 for <apps-discuss@ietf.org>; Tue,  7 Sep 2010 11:37:51 -0700 (PDT)
Received: by bwz9 with SMTP id 9so5575923bwz.31 for <apps-discuss@ietf.org>; Tue, 07 Sep 2010 11:37:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; bh=fny09onufDWQuTjjtKG3V0zEPnPkK2w2z6ae8T81y1M=; b=py5CzEYY32klvJ8lYHDgmZ2MYv4cbMTxk9wU5eAEBOaGU26gbi26sMi6xsGOO/OjSh SBgh769ePZWG0CDclS25PO8eteCHTCJcKRdKD8Sw46S4IaRdZgF2tZyRDmP1/Wy8Pcxa AmYKc6RsbmDpnWs0nPch9+1VBSG7ZJur3IF6I=
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:cc:content-type; b=q8TXQPILnTAfqMFaWRaj0v65nlyV7k2ld4vf0toZef0LaPvdeuRfpALUCXiMidQM2P XGgymgH5HzTb9DqNRn2Usj3Y6AizE4BXOJqYx2xVl61R1Xg51QMgoRTNxQx5NZaV5v7a 4+TVHzMg8M2tDflLd7cB1vEzGX3b4kmA3IAks=
MIME-Version: 1.0
Received: by 10.204.35.5 with SMTP id n5mr770066bkd.155.1283884679154; Tue, 07 Sep 2010 11:37:59 -0700 (PDT)
Sender: bobwyman@gmail.com
Received: by 10.204.18.69 with HTTP; Tue, 7 Sep 2010 11:37:59 -0700 (PDT)
In-Reply-To: <9A9E793D54FF76A74CA9E772@192.168.1.128>
References: <4C83BE0C.6090802@dcrocker.net> <20100905182354.GB30466@x27.adm.denic.de> <4C866DA9.8080302@dcrocker.net> <20100907181308.GN489@shinkuro.com> <9A9E793D54FF76A74CA9E772@192.168.1.128>
Date: Tue, 7 Sep 2010 14:37:59 -0400
X-Google-Sender-Auth: Rk3IbG-iJFZ9v6Xj8DUvCg5cjf8
Message-ID: <AANLkTi=r9hEXzD73vRBPj-hSt0YzYDvpsV1+TbdQXjwK@mail.gmail.com>
From: Bob Wyman <bob@wyman.us>
To: John C Klensin <john-ietf@jck.com>
Content-Type: multipart/alternative; boundary=0003255590ae3bcc7e048fafb2db
Cc: apps-discuss@ietf.org
Subject: Re: [apps-discuss] "organization's top level domain"
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Sep 2010 18:39:12 -0000

--0003255590ae3bcc7e048fafb2db
Content-Type: text/plain; charset=ISO-8859-1

John C Klensin <john-ietf@jck.com> wrote:
> I've often used "enterprise" rather than "organization"

Have you considered the even more generic, while still correct, "entity"?
"Enterprise" too often implies too much about economic intent and
"organization" tends to exclude individuals. Entity encompasses all of these
cases.

bob wyman


On Tue, Sep 7, 2010 at 2:29 PM, John C Klensin <john-ietf@jck.com> wrote:

>
>
> --On Tuesday, September 07, 2010 2:13 PM -0400 Andrew Sullivan
> <ajs@shinkuro.com> wrote:
>
> > On Tue, Sep 07, 2010 at 09:51:53AM -0700, Dave CROCKER wrote:
> >> On further reflection, I'm inclined to suggest:
> >>
> >>     "Organization's delegated domain"
> >
> > This has the conspicuous advantage that it is technically
> > exactly correct.  One teeny quibble: the discussion has
> > suggested (at least to me) that there is one such domain,
> > whereas we know there may be (and often is) more than one.
> > Any way to point out that there may well be more than one, but
> > that each one is effectively separate and managed
> > independently (modulo aliasing techniques like CNAME, DNAME,
> > and whatever the wild bunch over in DNSEXT comes up with next)?
>
> As long as you are sure that "delegated" won't run afoul of
> assorted "variant" and/or "symmetric" theories.  And I'll let
> you explain those to this lucky group.
>
> There is another little trap, which is why I've often used
> "enterprise" rather than "organization" and that is having
> subsidiary organizations delegated by some primary one.  That
> leads one to "primary organization's primary delegated...",
> which hurts the head, but nothing is perfect.
>
>    john
>
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss
>

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

<meta http-equiv=3D"content-type" content=3D"text/html; charset=3Dutf-8">Jo=
hn C Klensin=A0<span dir=3D"ltr">&lt;<a href=3D"mailto:john-ietf@jck.com">j=
ohn-ietf@jck.com</a>&gt;</span>=A0wrote:<br>&gt;=A0<meta http-equiv=3D"cont=
ent-type" content=3D"text/html; charset=3Dutf-8">I&#39;ve often used=A0&quo=
t;enterprise&quot; rather than &quot;organization&quot;<div>
<br></div><div>Have you considered the even more generic, while still corre=
ct, &quot;entity&quot;?</div><div>&quot;Enterprise&quot; too often implies =
too much about economic intent and &quot;organization&quot; tends to exclud=
e individuals. Entity encompasses all of these cases.</div>
<div><br></div><div>bob wyman</div><div><br></div><div><br><div class=3D"gm=
ail_quote">On Tue, Sep 7, 2010 at 2:29 PM, John C Klensin <span dir=3D"ltr"=
>&lt;<a href=3D"mailto:john-ietf@jck.com">john-ietf@jck.com</a>&gt;</span> =
wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;"><br>
<br>
--On Tuesday, September 07, 2010 2:13 PM -0400 Andrew Sullivan<br>
<div class=3D"im">&lt;<a href=3D"mailto:ajs@shinkuro.com">ajs@shinkuro.com<=
/a>&gt; wrote:<br>
<br>
&gt; On Tue, Sep 07, 2010 at 09:51:53AM -0700, Dave CROCKER wrote:<br>
&gt;&gt; On further reflection, I&#39;m inclined to suggest:<br>
&gt;&gt;<br>
&gt;&gt; =A0 =A0 &quot;Organization&#39;s delegated domain&quot;<br>
&gt;<br>
&gt; This has the conspicuous advantage that it is technically<br>
&gt; exactly correct. =A0One teeny quibble: the discussion has<br>
&gt; suggested (at least to me) that there is one such domain,<br>
&gt; whereas we know there may be (and often is) more than one.<br>
&gt; Any way to point out that there may well be more than one, but<br>
&gt; that each one is effectively separate and managed<br>
&gt; independently (modulo aliasing techniques like CNAME, DNAME,<br>
&gt; and whatever the wild bunch over in DNSEXT comes up with next)?<br>
<br>
</div>As long as you are sure that &quot;delegated&quot; won&#39;t run afou=
l of<br>
assorted &quot;variant&quot; and/or &quot;symmetric&quot; theories. =A0And =
I&#39;ll let<br>
you explain those to this lucky group.<br>
<br>
There is another little trap, which is why I&#39;ve often used<br>
&quot;enterprise&quot; rather than &quot;organization&quot; and that is hav=
ing<br>
subsidiary organizations delegated by some primary one. =A0That<br>
leads one to &quot;primary organization&#39;s primary delegated...&quot;,<b=
r>
which hurts the head, but nothing is perfect.<br>
<font color=3D"#888888"><br>
 =A0 =A0john<br>
</font><div><div></div><div class=3D"h5"><br>
_______________________________________________<br>
apps-discuss mailing list<br>
<a href=3D"mailto:apps-discuss@ietf.org">apps-discuss@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/apps-discuss" target=3D"_b=
lank">https://www.ietf.org/mailman/listinfo/apps-discuss</a><br>
</div></div></blockquote></div><br></div>

--0003255590ae3bcc7e048fafb2db--

From ajs@shinkuro.com  Tue Sep  7 11:41:47 2010
Return-Path: <ajs@shinkuro.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 54E053A695A for <apps-discuss@core3.amsl.com>; Tue,  7 Sep 2010 11:41:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.847
X-Spam-Level: 
X-Spam-Status: No, score=-101.847 tagged_above=-999 required=5 tests=[AWL=0.752, 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 VrCktRqYYRNa for <apps-discuss@core3.amsl.com>; Tue,  7 Sep 2010 11:41:46 -0700 (PDT)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id 453D93A6876 for <apps-discuss@ietf.org>; Tue,  7 Sep 2010 11:41:46 -0700 (PDT)
Received: from crankycanuck.ca (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 23F6B1ECB41D for <apps-discuss@ietf.org>; Tue,  7 Sep 2010 18:42:14 +0000 (UTC)
Date: Tue, 7 Sep 2010 14:42:12 -0400
From: Andrew Sullivan <ajs@shinkuro.com>
To: apps-discuss@ietf.org
Message-ID: <20100907184212.GO489@shinkuro.com>
Mail-Followup-To: apps-discuss@ietf.org
References: <4C83BE0C.6090802@dcrocker.net> <20100905182354.GB30466@x27.adm.denic.de> <4C866DA9.8080302@dcrocker.net> <20100907181308.GN489@shinkuro.com> <9A9E793D54FF76A74CA9E772@[192.168.1.128]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <9A9E793D54FF76A74CA9E772@[192.168.1.128]>
User-Agent: Mutt/1.5.18 (2008-05-17)
Subject: Re: [apps-discuss] "organization's top level domain"
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Sep 2010 18:41:47 -0000

On Tue, Sep 07, 2010 at 02:29:50PM -0400, John C Klensin wrote:
> As long as you are sure that "delegated" won't run afoul of
> assorted "variant" and/or "symmetric" theories.  And I'll let
> you explain those to this lucky group.

Oh, I am by no means sure of that.  But since we're still dealing with
the DNS and not some mystery-meat variation in which magic happens and
things that are different delegations are "the same" FSVO, I am
willing to leave those dogs to sleep.

> There is another little trap, which is why I've often used
> "enterprise" rather than "organization" and that is having
> subsidiary organizations delegated by some primary one.  That
> leads one to "primary organization's primary delegated...",
> which hurts the head, but nothing is perfect.

Isn't that a different organization, once you have a new delegation?
After all, delegations are by definition administrative boundaries.

A

-- 
Andrew Sullivan
ajs@shinkuro.com
Shinkuro, Inc.

From ajs@shinkuro.com  Tue Sep  7 11:44:06 2010
Return-Path: <ajs@shinkuro.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7F65D3A6876 for <apps-discuss@core3.amsl.com>; Tue,  7 Sep 2010 11:44:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.855
X-Spam-Level: 
X-Spam-Status: No, score=-101.855 tagged_above=-999 required=5 tests=[AWL=0.744, BAYES_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 G1qUUady9Dk3 for <apps-discuss@core3.amsl.com>; Tue,  7 Sep 2010 11:44:05 -0700 (PDT)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id 94D0B3A681E for <apps-discuss@ietf.org>; Tue,  7 Sep 2010 11:44:05 -0700 (PDT)
Received: from crankycanuck.ca (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 027FF1ECB41D for <apps-discuss@ietf.org>; Tue,  7 Sep 2010 18:44:32 +0000 (UTC)
Date: Tue, 7 Sep 2010 14:44:30 -0400
From: Andrew Sullivan <ajs@shinkuro.com>
To: apps-discuss@ietf.org
Message-ID: <20100907184430.GP489@shinkuro.com>
Mail-Followup-To: apps-discuss@ietf.org
References: <4C83BE0C.6090802@dcrocker.net> <20100905182354.GB30466@x27.adm.denic.de> <4C866DA9.8080302@dcrocker.net> <20100907181308.GN489@shinkuro.com> <20100907183555.GJ15670@unknown.office.denic.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20100907183555.GJ15670@unknown.office.denic.de>
User-Agent: Mutt/1.5.18 (2008-05-17)
Subject: Re: [apps-discuss] "organization's top level domain"
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Sep 2010 18:44:06 -0000

On Tue, Sep 07, 2010 at 08:35:55PM +0200, Peter Koch wrote:
> except where it isn't, probably depending on the exact meaning of
> "delegated".

You mean that undelegated zones still qualify under this term?  Then
yes, you're right, the proposed term is wrong. 

Ugh.

A


-- 
Andrew Sullivan
ajs@shinkuro.com
Shinkuro, Inc.

From dave@cridland.net  Tue Sep  7 12:33:19 2010
Return-Path: <dave@cridland.net>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D28243A6876; Tue,  7 Sep 2010 12:33:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.543
X-Spam-Level: 
X-Spam-Status: No, score=-1.543 tagged_above=-999 required=5 tests=[AWL=-0.803, 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 uznpdiXPKvXK; Tue,  7 Sep 2010 12:33:18 -0700 (PDT)
Received: from peirce.dave.cridland.net (peirce.dave.cridland.net [217.155.137.61]) by core3.amsl.com (Postfix) with ESMTP id A92093A6980; Tue,  7 Sep 2010 12:33:11 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by peirce.dave.cridland.net (Postfix) with ESMTP id 0E1F811680C1; Tue,  7 Sep 2010 20:33:37 +0100 (BST)
X-Virus-Scanned: Debian amavisd-new at peirce.dave.cridland.net
Received: from peirce.dave.cridland.net ([127.0.0.1]) by localhost (peirce.dave.cridland.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 12nD8AaQ3yXx; Tue,  7 Sep 2010 20:33:34 +0100 (BST)
Received: from puncture (unknown [217.155.137.60]) by peirce.dave.cridland.net (Postfix) with ESMTPA id F13EE11680BD; Tue,  7 Sep 2010 20:33:33 +0100 (BST)
MIME-Version: 1.0
Message-Id: <11907.1283888013.974202@puncture>
Date: Tue, 07 Sep 2010 20:33:33 +0100
From: Dave Cridland <dave@cridland.net>
To: General discussion of application-layer protocols <apps-discuss@ietf.org>,  The IESG <iesg@ietf.org>, <abegen@cisco.com>
Content-Type: text/plain; delsp="yes"; charset="iso-8859-1"; format="flowed"
Content-Transfer-Encoding: 8Bit
Subject: [apps-discuss] apps-team review of draft-ietf-fecframe-sdp-elements
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Sep 2010 19:33:20 -0000

Hiya folks,

I have been selected as the Applications Area Review Team reviewer  
for this draft (for background on apps-review, please see  
http://www.apps.ietf.org/content/applications-area-review-team).

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

Document: draft-ietf-fecframe-sdp-elements
Reviewer: Dave Cridland
Review Date: 2010-09-07

Summary: This draft has minor editorial issues, and one potential  
issue. The document could be published as an RFC with the existing  
encoding of repair-window, but some thought should be given to it.

Major Issues: None

Minor Issues:

Section 4.6 describes an SDP attribute "repair-window", which seems  
to have a possibly over-complicated representation. It has two  
different units, one of which is the default. This yields three  
different ways of expressing the same intent:

150
150ms
150000us

It's unclear to me what benefit this brings, and the downside could  
be that implementations only handle a subset of the possibilities,  
resulting in a failure to interoperate.

I would advise serious consideration of restricting this to one unit.  
If microsecond resolutions are required, then obviously this would be  
µs, resulting in the above being written only as:

150000

This is unfortunately not a current option, and if there are existing  
deployments, this may yield further problems.

Nits:

The term "bytes" is sometimes used where I suspect "octets" would be  
more precise.

Security:

I briefly cast my eye over the Security Considerations section -  
please don't grant these comments the same weight as a security  
review.

There is advice that "It is RECOMMENDED [to] follow the security  
considerations of SDP". I would have thought that following those  
recommendations would be a requirement. I'm quite taken with using  
both RECOMMENDED and SHOULD in the same sentence, mind, but I think  
this could be phrased better.

It's also not clear what effect the SDP modification would actually  
have - whether this is a denial of service or if it yields some other  
attack. (My suspicion is that if an attacker is in a position to  
perform this attack, then the attacker can subvert the media streams  
entirely and do something much more interesting).

Dave.
-- 
Dave Cridland - mailto:dave@cridland.net - xmpp:dwd@dave.cridland.net
  - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
  - http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade

From john-ietf@jck.com  Tue Sep  7 18:35:19 2010
Return-Path: <john-ietf@jck.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C088D3A6877 for <apps-discuss@core3.amsl.com>; Tue,  7 Sep 2010 18:35:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.361
X-Spam-Level: 
X-Spam-Status: No, score=-102.361 tagged_above=-999 required=5 tests=[AWL=0.238, 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 hfSONKKhKRWR for <apps-discuss@core3.amsl.com>; Tue,  7 Sep 2010 18:35:18 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id BB9F83A6844 for <apps-discuss@ietf.org>; Tue,  7 Sep 2010 18:35:16 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1Ot9Zg-000OB5-C0; Tue, 07 Sep 2010 21:35:44 -0400
Date: Tue, 07 Sep 2010 21:35:43 -0400
From: John C Klensin <john-ietf@jck.com>
To: Andrew Sullivan <ajs@shinkuro.com>, apps-discuss@ietf.org
Message-ID: <62E755BE0C9FE32A7539F500@PST.JCK.COM>
In-Reply-To: <20100907184430.GP489@shinkuro.com>
References: <4C83BE0C.6090802@dcrocker.net> <20100905182354.GB30466@x27.adm.denic.de> <4C866DA9.8080302@dcrocker.net> <20100907181308.GN489@shinkuro.com> <20100907183555.GJ15670@unknown.office.denic.de> <20100907184430.GP489@shinkuro.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
Subject: Re: [apps-discuss] "organization's top level domain"
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Sep 2010 01:35:20 -0000

--On Tuesday, September 07, 2010 14:44 -0400 Andrew Sullivan
<ajs@shinkuro.com> wrote:

> On Tue, Sep 07, 2010 at 08:35:55PM +0200, Peter Koch wrote:
>> except where it isn't, probably depending on the exact
>> meaning of "delegated".
> 
> You mean that undelegated zones still qualify under this term?
> Then yes, you're right, the proposed term is wrong. 

Sigh.  What I've been after (not necessarily exactly the same
thing Dave has been after) is a way to identify a domain that is
the first (highest-level) one to actually belong to an
organization/ enterprise/ entity, such that the entity can held
responsible for that domain and everything and anything below
it.  The presumption is that the next domain toward the root is
the responsibility of some entity that is in the business (or
service) of allocating names to multiple, mostly unrelated,
organizations/ enterprises/ entities.

In that context at least, "domains" and "subdomains" are defined
by label boundaries, not by delegation records, zone cuts, or
anything else that connects to how particular DNS subtrees are
structured administratively or operationally.  To make things
worse, when an enterprise (organization/ entity) domain exists
in this way, it may be delegated or not but, if it is delegated,
it may be delegated to an admin contact who is not directly
connected with the entity that has actual policy responsibility
for the domain.

It seems to me that we are trying to overlay that idea of policy
responsibility for a domain and its subdomains onto top of the
DNS concepts of delegation and authority wrt zones and zone
administration.  They just aren't going to mesh perfectly, no
matter what we do.  For example...

>> There is another little trap, which is why I've often used
>> "enterprise" rather than "organization" and that is having
>> subsidiary organizations delegated by some primary one.  That
>> leads one to "primary organization's primary delegated...",
>> which hurts the head, but nothing is perfect.
> 
> Isn't that a different organization, once you have a new
> delegation? After all, delegations are by definition
> administrative boundaries.

But that certainly doesn't create a "different organization", at
least as long as it is possible for one organization to "own"
multiple domains in the same or different parts of the DNS tree.

The abstractions also get us.  For example, Bob Wyman wrote:

> John C Klensin <john-ietf@jck.com> wrote:
>> I've often used "enterprise" rather than "organization"
> 
> Have you considered the even more generic, while still
> correct, "entity"? "Enterprise" too often implies too much
> about economic intent and "organization" tends to exclude
> individuals. Entity encompasses all of these cases.

But "entity" is so abstract and general that it can include both
subdivisions of "enterprise" or "organization" and much broader
units such as TLD registries or even governments (note, e.g.,
the terminology actually used in ISO 3166-1).

best,
   john


From fanf2@hermes.cam.ac.uk  Wed Sep  8 03:39:47 2010
Return-Path: <fanf2@hermes.cam.ac.uk>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0D4DF3A683E for <apps-discuss@core3.amsl.com>; Wed,  8 Sep 2010 03:39:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.319
X-Spam-Level: 
X-Spam-Status: No, score=-5.319 tagged_above=-999 required=5 tests=[AWL=-0.116, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, 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 OFhTWB6Er9nu for <apps-discuss@core3.amsl.com>; Wed,  8 Sep 2010 03:39:44 -0700 (PDT)
Received: from ppsw-31.csi.cam.ac.uk (ppsw-31.csi.cam.ac.uk [131.111.8.131]) by core3.amsl.com (Postfix) with ESMTP id D0B253A6817 for <apps-discuss@ietf.org>; Wed,  8 Sep 2010 03:39:30 -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 [87.115.173.110] (port=58566 helo=[192.168.1.8]) by ppsw-31.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.157]:587) with esmtpsa (PLAIN:fanf2) (TLSv1:AES128-SHA:128) id 1OtI4K-0001sW-Ke (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Wed, 08 Sep 2010 11:39:56 +0100
References: <4C83BE0C.6090802@dcrocker.net> <20100905182354.GB30466@x27.adm.denic.de> <4C866DA9.8080302@dcrocker.net> <20100907181308.GN489@shinkuro.com>
In-Reply-To: <20100907181308.GN489@shinkuro.com>
Mime-Version: 1.0 (iPhone Mail 8A400)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <852F873D-44C1-4D9C-AA1C-50FC3473BA00@dotat.at>
X-Mailer: iPhone Mail (8A400)
From: Tony Finch <dot@dotat.at>
Date: Wed, 8 Sep 2010 11:39:14 +0100
To: Andrew Sullivan <ajs@shinkuro.com>
Sender: Tony Finch <fanf2@hermes.cam.ac.uk>
Cc: "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] "organization's top level domain"
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Sep 2010 10:39:47 -0000

On 7 Sep 2010, at 19:13, Andrew Sullivan <ajs@shinkuro.com> wrote:

> On Tue, Sep 07, 2010 at 09:51:53AM -0700, Dave CROCKER wrote:
>> On further reflection, I'm inclined to suggest:
>>=20
>>    "Organization's delegated domain"
>=20
> This has the conspicuous advantage that it is technically exactly
> correct.

Yes, it's pretty good.

However there are situations where an organization has a domain name but it i=
s not delegated to them, e.g. departments or affiliated organizations whose D=
NS is managed by their parent organization but who manage some other service=
s themselves.

So perhaps "organization's principal domain name(s)"?

Tony.=

From paul.hoffman@vpnc.org  Wed Sep  8 06:57:48 2010
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C85FE3A68D2 for <apps-discuss@core3.amsl.com>; Wed,  8 Sep 2010 06:57:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.122
X-Spam-Level: 
X-Spam-Status: No, score=-101.122 tagged_above=-999 required=5 tests=[AWL=0.924, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, 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 Ng9sdWFcCSQy for <apps-discuss@core3.amsl.com>; Wed,  8 Sep 2010 06:57:48 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id F08783A68C0 for <apps-discuss@ietf.org>; Wed,  8 Sep 2010 06:57:47 -0700 (PDT)
Received: from [10.20.30.158] (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o88DwE7N049498 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 8 Sep 2010 06:58:15 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p06240813c8ad4693e1b0@[10.20.30.158]>
In-Reply-To: <20100907184430.GP489@shinkuro.com>
References: <4C83BE0C.6090802@dcrocker.net> <20100905182354.GB30466@x27.adm.denic.de>	<4C866DA9.8080302@dcrocker.net> <20100907181308.GN489@shinkuro.com> <20100907183555.GJ15670@unknown.office.denic.de> <20100907184430.GP489@shinkuro.com>
Date: Wed, 8 Sep 2010 06:58:13 -0700
To: Andrew Sullivan <ajs@shinkuro.com>, apps-discuss@ietf.org
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
Subject: Re: [apps-discuss] "organization's top level domain"
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Sep 2010 13:57:48 -0000

At 2:44 PM -0400 9/7/10, Andrew Sullivan wrote:
>On Tue, Sep 07, 2010 at 08:35:55PM +0200, Peter Koch wrote:
>> except where it isn't, probably depending on the exact meaning of
>> "delegated".
>
>You mean that undelegated zones still qualify under this term?  Then
>yes, you're right, the proposed term is wrong.

I disagree. It is good enough. Peter's case, while real, is an edge case that is probably not even understood by people who think they control names in that zone.

Saying "we can't come up with a good term because someone has a business model that goes against it" is not productive.

--Paul Hoffman, Director
--VPN Consortium

From ajs@shinkuro.com  Wed Sep  8 07:10:48 2010
Return-Path: <ajs@shinkuro.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9C0B03A6869 for <apps-discuss@core3.amsl.com>; Wed,  8 Sep 2010 07:10:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.876
X-Spam-Level: 
X-Spam-Status: No, score=-101.876 tagged_above=-999 required=5 tests=[AWL=0.723, 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 8cBfuXtjlyow for <apps-discuss@core3.amsl.com>; Wed,  8 Sep 2010 07:10:45 -0700 (PDT)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id 1BD333A67F4 for <apps-discuss@ietf.org>; Wed,  8 Sep 2010 07:10:45 -0700 (PDT)
Received: from crankycanuck.ca (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 E494F1ECB41D; Wed,  8 Sep 2010 14:11:11 +0000 (UTC)
Date: Wed, 8 Sep 2010 10:11:10 -0400
From: Andrew Sullivan <ajs@shinkuro.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Message-ID: <20100908141109.GC3852@shinkuro.com>
References: <4C83BE0C.6090802@dcrocker.net> <20100905182354.GB30466@x27.adm.denic.de> <4C866DA9.8080302@dcrocker.net> <20100907181308.GN489@shinkuro.com> <20100907183555.GJ15670@unknown.office.denic.de> <20100907184430.GP489@shinkuro.com> <p06240813c8ad4693e1b0@[10.20.30.158]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <p06240813c8ad4693e1b0@[10.20.30.158]>
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: apps-discuss@ietf.org
Subject: Re: [apps-discuss] "organization's top level domain"
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Sep 2010 14:10:49 -0000

On Wed, Sep 08, 2010 at 06:58:13AM -0700, Paul Hoffman wrote:
> >You mean that undelegated zones still qualify under this term?  Then
> >yes, you're right, the proposed term is wrong.
> 
> I disagree. It is good enough. Peter's case, while real, is an edge case that is probably not even understood by people who think they control names in that zone.
> 

It doesn't matter.  "Delegate" has a technical meaning in the DNS
context.  For a protocol as central to the Internet as DNS is, the
entire area is replete with sloppy terminology and bad definitions;
"delegate" is not one of those, and I am strongly opposed to
formalizing any term that appears to blur that clarity.  If zones that
are not actually delegated across a zone cut are included, then we
can't use the term "delegated".

> Saying "we can't come up with a good term because someone has a business model that goes against it" is not productive.
> 

Using precise terms imprecisely isn't productive, either.

A

-- 
Andrew Sullivan
ajs@shinkuro.com
Shinkuro, Inc.

From abegen@cisco.com  Tue Sep  7 13:08:32 2010
Return-Path: <abegen@cisco.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 57CA93A6AB7; Tue,  7 Sep 2010 13:08:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.459
X-Spam-Level: 
X-Spam-Status: No, score=-10.459 tagged_above=-999 required=5 tests=[AWL=0.140, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 pVYPbbqw7bYb; Tue,  7 Sep 2010 13:08:28 -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 8A1EF3A6AA6; Tue,  7 Sep 2010 13:08:28 -0700 (PDT)
Authentication-Results: sj-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAPc4hkyrR7Hu/2dsb2JhbAChBHGlVIx1jkuFPQSEQ4hT
X-IronPort-AV: E=Sophos;i="4.56,330,1280707200"; d="scan'208";a="277109942"
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-2.cisco.com with ESMTP; 07 Sep 2010 20:08:56 +0000
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id o87K8uOe007117; Tue, 7 Sep 2010 20:08:56 GMT
Received: from xmb-sjc-215.amer.cisco.com ([171.70.151.169]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 7 Sep 2010 13:08:56 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 7 Sep 2010 13:08:56 -0700
Message-ID: <04CAD96D4C5A3D48B1919248A8FE0D540D128DEB@xmb-sjc-215.amer.cisco.com>
In-Reply-To: <11907.1283888013.974202@puncture>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: apps-team review of draft-ietf-fecframe-sdp-elements
Thread-Index: ActOw5b9a5gvJ96zQty/SQ6Q5sf+xgAA/bxQ
References: <11907.1283888013.974202@puncture>
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: "Dave Cridland" <dave@cridland.net>, "General discussion of application-layer protocols" <apps-discuss@ietf.org>, "The IESG" <iesg@ietf.org>
X-OriginalArrivalTime: 07 Sep 2010 20:08:56.0937 (UTC) FILETIME=[80ABF590:01CB4EC8]
X-Mailman-Approved-At: Wed, 08 Sep 2010 16:55:04 -0700
Subject: Re: [apps-discuss] apps-team review of draft-ietf-fecframe-sdp-elements
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Sep 2010 20:08:32 -0000

Hi Dave,

I am off to PTO till the weekend (about to leave). But, here are my =
quick comments:

> -----Original Message-----
> From: Dave Cridland [mailto:dave@cridland.net]
> Sent: Tuesday, September 07, 2010 10:34 PM
> To: General discussion of application-layer protocols; The IESG; Ali =
C. Begen (abegen)
> Subject: apps-team review of draft-ietf-fecframe-sdp-elements
>=20
> Hiya folks,
>=20
> I have been selected as the Applications Area Review Team reviewer
> for this draft (for background on apps-review, please see
> http://www.apps.ietf.org/content/applications-area-review-team).
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive. Please wait for direction from your document
> shepherd or AD before posting a new version of the draft.
>=20
> Document: draft-ietf-fecframe-sdp-elements
> Reviewer: Dave Cridland
> Review Date: 2010-09-07
>=20
> Summary: This draft has minor editorial issues, and one potential
> issue. The document could be published as an RFC with the existing
> encoding of repair-window, but some thought should be given to it.
>=20
> Major Issues: None
>=20
> Minor Issues:
>=20
> Section 4.6 describes an SDP attribute "repair-window", which seems
> to have a possibly over-complicated representation. It has two
> different units, one of which is the default. This yields three
> different ways of expressing the same intent:
>=20
> 150
> 150ms
> 150000us

Correct.
=20
> It's unclear to me what benefit this brings, and the downside could
> be that implementations only handle a subset of the possibilities,
> resulting in a failure to interoperate.
>=20
> I would advise serious consideration of restricting this to one unit.
> If microsecond resolutions are required, then obviously this would be
> =B5s, resulting in the above being written only as:

Personally and as the author, I was pretty much always fine with the ms. =
I don't think we will see any need for 'us' in the foreseeable future. =
But, some asked for it and defining it as an alternative unit was the =
simple solution.=20
=20
> 150000

This may address your concern but for the current implementations and =
applications, it might be more confusing.
=20
> This is unfortunately not a current option, and if there are existing
> deployments, this may yield further problems.

Right.

However, I am open to suggestions. If majority thinks we should change =
it, I can do a quick revision.
=20
> Nits:
>=20
> The term "bytes" is sometimes used where I suspect "octets" would be
> more precise.

OK, will do one more pass in the next revision.
=20
> Security:
>=20
> I briefly cast my eye over the Security Considerations section -
> please don't grant these comments the same weight as a security
> review.
>=20
> There is advice that "It is RECOMMENDED [to] follow the security
> considerations of SDP". I would have thought that following those
> recommendations would be a requirement. I'm quite taken with using
> both RECOMMENDED and SHOULD in the same sentence, mind, but I think
> this could be phrased better.

Will look into this.
=20
> It's also not clear what effect the SDP modification would actually
> have - whether this is a denial of service or if it yields some other
> attack. (My suspicion is that if an attacker is in a position to
> perform this attack, then the attacker can subvert the media streams
> entirely and do something much more interesting).

Yes, he can certainly do more interesting and harmful stuff. But, doing =
harm without being detected would be worse and SDP modification is one =
way of doing it.
=20
Thanks again for the review. I will address these comments in the next =
revision (I will be back in the weekend).

Cheers, acbegen

> Dave.
> --
> Dave Cridland - mailto:dave@cridland.net - xmpp:dwd@dave.cridland.net
>   - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
>   - http://dave.cridland.net/
> Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade

From dhc@dcrocker.net  Thu Sep  9 09:44:26 2010
Return-Path: <dhc@dcrocker.net>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6F92C3A6919 for <apps-discuss@core3.amsl.com>; Thu,  9 Sep 2010 09:44: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=[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 JePi+mMaoeSI for <apps-discuss@core3.amsl.com>; Thu,  9 Sep 2010 09:44:25 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id 040F83A67D6 for <apps-discuss@ietf.org>; Thu,  9 Sep 2010 09:44:25 -0700 (PDT)
Received: from [192.168.1.14] (ppp-68-120-198-81.dsl.pltn13.pacbell.net [68.120.198.81]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id o89GilR5003995 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for <apps-discuss@ietf.org>; Thu, 9 Sep 2010 09:44:52 -0700
Message-ID: <4C890EFD.9040407@dcrocker.net>
Date: Thu, 09 Sep 2010 09:44:45 -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.9) Gecko/20100825 Thunderbird/3.1.3
MIME-Version: 1.0
To: "apps-discuss@ietf.org" <apps-discuss@ietf.org>
References: <4C83BE0C.6090802@dcrocker.net>	<20100905182354.GB30466@x27.adm.denic.de>	<4C866DA9.8080302@dcrocker.net> <20100907181308.GN489@shinkuro.com> <852F873D-44C1-4D9C-AA1C-50FC3473BA00@dotat.at>
In-Reply-To: <852F873D-44C1-4D9C-AA1C-50FC3473BA00@dotat.at>
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, 09 Sep 2010 09:44:52 -0700 (PDT)
Subject: Re: [apps-discuss] "organization's top level domain"
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Sep 2010 16:44:26 -0000

On 9/8/2010 3:39 AM, Tony Finch wrote:
> On 7 Sep 2010, at 19:13, Andrew Sullivan<ajs@shinkuro.com>  wrote:
>> On Tue, Sep 07, 2010 at 09:51:53AM -0700, Dave CROCKER wrote:
>>> "Organization's delegated domain"
...
> However there are situations where an organization has a domain name but it
> is not delegated to them, e.g. departments or affiliated organizations whose
> DNS is managed by their parent organization but who manage some other
> services themselves.
>
> So perhaps "organization's principal domain name(s)"?


On reviewing the thread, and noting the possible mismatch between the precise
technical meaning of 'delegate' versus the desire to note an organizational
boundary, I was gravitating toward's "organization's registered domain".
Sub-domains are registered, too, of course but I think the term is nonetheless
pretty clear.

However, 'registered' is another term of art and its use here therefore offers
some plausible chance of misunderstanding and/or mismatch.

I think Tony's suggestion is superior.  It has the multiple benefits of using a
term that is not already taken for DNS use and of having the right focus, IMO.

As for organization versus enterprise, at best the difference is likely to be
too subtle most people and at worst it will not work quite properly. Enterprise
is sometimes use to refer to geography (campus).  That's obscure, but I'd
suggest against inviting it.  It also tends to imply commercial enterprise,
whereas "organization" is fully neutral about business model.

So I vote for "organization's principal domain(s)".

I'd like to get +1/-1 responses from the rest of you, please...

d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From ajs@shinkuro.com  Thu Sep  9 09:52:25 2010
Return-Path: <ajs@shinkuro.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B8D7F3A6A7B for <apps-discuss@core3.amsl.com>; Thu,  9 Sep 2010 09:52:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.956
X-Spam-Level: 
X-Spam-Status: No, score=-101.956 tagged_above=-999 required=5 tests=[AWL=0.643, 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 A2MO922VeRvh for <apps-discuss@core3.amsl.com>; Thu,  9 Sep 2010 09:52:17 -0700 (PDT)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id CE0583A68E7 for <apps-discuss@ietf.org>; Thu,  9 Sep 2010 09:52:16 -0700 (PDT)
Received: from crankycanuck.ca (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 CDFB51ECB41D for <apps-discuss@ietf.org>; Thu,  9 Sep 2010 16:52:43 +0000 (UTC)
Date: Thu, 9 Sep 2010 12:52:42 -0400
From: Andrew Sullivan <ajs@shinkuro.com>
To: apps-discuss@ietf.org
Message-ID: <20100909165241.GF7373@shinkuro.com>
References: <4C83BE0C.6090802@dcrocker.net> <20100905182354.GB30466@x27.adm.denic.de> <4C866DA9.8080302@dcrocker.net> <20100907181308.GN489@shinkuro.com> <852F873D-44C1-4D9C-AA1C-50FC3473BA00@dotat.at> <4C890EFD.9040407@dcrocker.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4C890EFD.9040407@dcrocker.net>
User-Agent: Mutt/1.5.18 (2008-05-17)
Subject: Re: [apps-discuss] "organization's top level domain"
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Sep 2010 16:52:25 -0000

On Thu, Sep 09, 2010 at 09:44:45AM -0700, Dave CROCKER wrote:
>
> I think Tony's suggestion is superior.

I agree.  Use that.


-- 
Andrew Sullivan
ajs@shinkuro.com
Shinkuro, Inc.

From tony@att.com  Thu Sep  9 09:53:38 2010
Return-Path: <tony@att.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5B7EC3A692A for <apps-discuss@core3.amsl.com>; Thu,  9 Sep 2010 09:53:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.117
X-Spam-Level: 
X-Spam-Status: No, score=-106.117 tagged_above=-999 required=5 tests=[AWL=0.482, 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 zQKl183WoCQP for <apps-discuss@core3.amsl.com>; Thu,  9 Sep 2010 09:53:33 -0700 (PDT)
Received: from mail167.messagelabs.com (mail167.messagelabs.com [216.82.253.179]) by core3.amsl.com (Postfix) with ESMTP id ECB9F3A6816 for <apps-discuss@ietf.org>; Thu,  9 Sep 2010 09:53:32 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: tony@att.com
X-Msg-Ref: server-13.tower-167.messagelabs.com!1284051238!31158348!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [144.160.20.145]
Received: (qmail 4495 invoked from network); 9 Sep 2010 16:53:59 -0000
Received: from sbcsmtp6.sbc.com (HELO mlpd192.enaf.sfdc.sbc.com) (144.160.20.145) by server-13.tower-167.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 9 Sep 2010 16:53: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 o89GsELn013172 for <apps-discuss@ietf.org>; Thu, 9 Sep 2010 12:54:15 -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 o89GsBhB013127 for <apps-discuss@ietf.org>; Thu, 9 Sep 2010 12:54:11 -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 o89GrrwL014441 for <apps-discuss@ietf.org>; Thu, 9 Sep 2010 12:53:54 -0400
Received: from mailgw1.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 o89GrqXV014399 for <apps-discuss@ietf.org>; Thu, 9 Sep 2010 12:53:52 -0400
Received: from [135.91.110.95] (dn135-91-110-95.dhcpn.ugn.att.com[135.91.110.95]) by maillennium.att.com (mailgw1) with ESMTP id <20100909165351gw100627pqe> (Authid: tony); Thu, 9 Sep 2010 16:53:52 +0000
X-Originating-IP: [135.91.110.95]
Message-ID: <4C89111F.2000108@att.com>
Date: Thu, 09 Sep 2010 12:53:51 -0400
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
To: dcrocker@bbiw.net
References: <4C83BE0C.6090802@dcrocker.net>	<20100905182354.GB30466@x27.adm.denic.de>	<4C866DA9.8080302@dcrocker.net>	<20100907181308.GN489@shinkuro.com>	<852F873D-44C1-4D9C-AA1C-50FC3473BA00@dotat.at> <4C890EFD.9040407@dcrocker.net>
In-Reply-To: <4C890EFD.9040407@dcrocker.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] "organization's top level domain"
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Sep 2010 16:53:38 -0000

+1

On 9/9/2010 12:44 PM, Dave CROCKER wrote:
>
> On 9/8/2010 3:39 AM, Tony Finch wrote:
>> On 7 Sep 2010, at 19:13, Andrew Sullivan<ajs@shinkuro.com>  wrote:
>>> On Tue, Sep 07, 2010 at 09:51:53AM -0700, Dave CROCKER wrote:
>>>> "Organization's delegated domain"
> ...
>> However there are situations where an organization has a domain name 
>> but it
>> is not delegated to them, e.g. departments or affiliated 
>> organizations whose
>> DNS is managed by their parent organization but who manage some other
>> services themselves.
>>
>> So perhaps "organization's principal domain name(s)"?
>
>
> On reviewing the thread, and noting the possible mismatch between the 
> precise
> technical meaning of 'delegate' versus the desire to note an 
> organizational
> boundary, I was gravitating toward's "organization's registered domain".
> Sub-domains are registered, too, of course but I think the term is 
> nonetheless
> pretty clear.
>
> However, 'registered' is another term of art and its use here 
> therefore offers
> some plausible chance of misunderstanding and/or mismatch.
>
> I think Tony's suggestion is superior.  It has the multiple benefits 
> of using a
> term that is not already taken for DNS use and of having the right 
> focus, IMO.
>
> As for organization versus enterprise, at best the difference is 
> likely to be
> too subtle most people and at worst it will not work quite properly. 
> Enterprise
> is sometimes use to refer to geography (campus).  That's obscure, but I'd
> suggest against inviting it.  It also tends to imply commercial 
> enterprise,
> whereas "organization" is fully neutral about business model.
>
> So I vote for "organization's principal domain(s)".
>
> I'd like to get +1/-1 responses from the rest of you, please...
>
> d/
>

From paul.hoffman@vpnc.org  Thu Sep  9 09:53:47 2010
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D15BC3A6A98 for <apps-discuss@core3.amsl.com>; Thu,  9 Sep 2010 09:53:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.161
X-Spam-Level: 
X-Spam-Status: No, score=-101.161 tagged_above=-999 required=5 tests=[AWL=0.885, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, 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 sHMmmcR2TBXh for <apps-discuss@core3.amsl.com>; Thu,  9 Sep 2010 09:53:46 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id D134F3A6A83 for <apps-discuss@ietf.org>; Thu,  9 Sep 2010 09:53:45 -0700 (PDT)
Received: from [10.20.30.158] (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o89Gs55U038648 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Sep 2010 09:54:07 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p0624085bc8aec16bf112@[10.20.30.158]>
In-Reply-To: <4C890EFD.9040407@dcrocker.net>
References: <4C83BE0C.6090802@dcrocker.net> <20100905182354.GB30466@x27.adm.denic.de>	<4C866DA9.8080302@dcrocker.net> <20100907181308.GN489@shinkuro.com> <852F873D-44C1-4D9C-AA1C-50FC3473BA00@dotat.at> <4C890EFD.9040407@dcrocker.net>
Date: Thu, 9 Sep 2010 09:54:04 -0700
To: dcrocker@bbiw.net, "apps-discuss@ietf.org" <apps-discuss@ietf.org>
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
Subject: Re: [apps-discuss] "organization's top level domain"
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Sep 2010 16:53:47 -0000

At 9:44 AM -0700 9/9/10, Dave CROCKER wrote:
>On 9/8/2010 3:39 AM, Tony Finch wrote:
>>On 7 Sep 2010, at 19:13, Andrew Sullivan<ajs@shinkuro.com>  wrote:
>>>On Tue, Sep 07, 2010 at 09:51:53AM -0700, Dave CROCKER wrote:
>>>>"Organization's delegated domain"
>...
>>However there are situations where an organization has a domain name but it
>>is not delegated to them, e.g. departments or affiliated organizations whose
>>DNS is managed by their parent organization but who manage some other
>>services themselves.
>>
>>So perhaps "organization's principal domain name(s)"?
>
>
>On reviewing the thread, and noting the possible mismatch between the precise
>technical meaning of 'delegate' versus the desire to note an organizational
>boundary, I was gravitating toward's "organization's registered domain".
>Sub-domains are registered, too, of course but I think the term is nonetheless
>pretty clear.
>
>However, 'registered' is another term of art and its use here therefore offers
>some plausible chance of misunderstanding and/or mismatch.
>
>I think Tony's suggestion is superior.  It has the multiple benefits of using a
>term that is not already taken for DNS use and of having the right focus, IMO.
>
>As for organization versus enterprise, at best the difference is likely to be
>too subtle most people and at worst it will not work quite properly. Enterprise
>is sometimes use to refer to geography (campus).  That's obscure, but I'd
>suggest against inviting it.  It also tends to imply commercial enterprise,
>whereas "organization" is fully neutral about business model.
>
>So I vote for "organization's principal domain(s)".
>
>I'd like to get +1/-1 responses from the rest of you, please...

You're not going to like this, but -1 for a sad reason: the principal domain name for Example Corp. is www.example.com, not example.com.

--Paul Hoffman, Director
--VPN Consortium

From msk@cloudmark.com  Thu Sep  9 10:03:55 2010
Return-Path: <msk@cloudmark.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2C3F83A68D6 for <apps-discuss@core3.amsl.com>; Thu,  9 Sep 2010 10:03:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.37
X-Spam-Level: 
X-Spam-Status: No, score=-103.37 tagged_above=-999 required=5 tests=[AWL=-0.771, 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 6T9f6TkkZi6o for <apps-discuss@core3.amsl.com>; Thu,  9 Sep 2010 10:03:54 -0700 (PDT)
Received: from ht1-outbound.cloudmark.com (ht1-outbound.cloudmark.com [72.5.239.35]) by core3.amsl.com (Postfix) with ESMTP id 5C2D63A68A0 for <apps-discuss@ietf.org>; Thu,  9 Sep 2010 10:03:54 -0700 (PDT)
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by malice.corp.cloudmark.com ([172.22.10.71]) with mapi; Thu, 9 Sep 2010 10:04:21 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: Tony Hansen <tony@att.com>, "dcrocker@bbiw.net" <dcrocker@bbiw.net>
Date: Thu, 9 Sep 2010 10:04:21 -0700
Thread-Topic: [apps-discuss] "organization's top level domain"
Thread-Index: ActQP59nbu1X26iXTEeJBFirnrXbAgAAV5oQ
Message-ID: <BB012BD379D7B046ABE1472D8093C61C01FA2104FB@EXCH-C2.corp.cloudmark.com>
References: <4C83BE0C.6090802@dcrocker.net> <20100905182354.GB30466@x27.adm.denic.de>	<4C866DA9.8080302@dcrocker.net> <20100907181308.GN489@shinkuro.com> <852F873D-44C1-4D9C-AA1C-50FC3473BA00@dotat.at> <4C890EFD.9040407@dcrocker.net> <4C89111F.2000108@att.com>
In-Reply-To: <4C89111F.2000108@att.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: "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] "organization's top level domain"
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Sep 2010 17:03:55 -0000

> -----Original Message-----
> From: apps-discuss-bounces@ietf.org [mailto:apps-discuss-
> bounces@ietf.org] On Behalf Of Tony Hansen
> Sent: Thursday, September 09, 2010 9:54 AM
> To: dcrocker@bbiw.net
> Cc: apps-discuss@ietf.org
> Subject: Re: [apps-discuss] "organization's top level domain"
>=20
> > So I vote for "organization's principal domain(s)".
> >
> > I'd like to get +1/-1 responses from the rest of you, please...
>
> +1

Ditto.

From ajs@shinkuro.com  Thu Sep  9 10:17:12 2010
Return-Path: <ajs@shinkuro.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4A0353A6897 for <apps-discuss@core3.amsl.com>; Thu,  9 Sep 2010 10:17:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.961
X-Spam-Level: 
X-Spam-Status: No, score=-101.961 tagged_above=-999 required=5 tests=[AWL=0.638, 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 kyysPnBG--Eo for <apps-discuss@core3.amsl.com>; Thu,  9 Sep 2010 10:17:11 -0700 (PDT)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id 0FD613A6870 for <apps-discuss@ietf.org>; Thu,  9 Sep 2010 10:17:11 -0700 (PDT)
Received: from crankycanuck.ca (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 633F51ECB41D for <apps-discuss@ietf.org>; Thu,  9 Sep 2010 17:17:38 +0000 (UTC)
Date: Thu, 9 Sep 2010 13:17:36 -0400
From: Andrew Sullivan <ajs@shinkuro.com>
To: apps-discuss@ietf.org
Message-ID: <20100909171736.GH7373@shinkuro.com>
References: <4C83BE0C.6090802@dcrocker.net> <20100905182354.GB30466@x27.adm.denic.de> <4C866DA9.8080302@dcrocker.net> <20100907181308.GN489@shinkuro.com> <852F873D-44C1-4D9C-AA1C-50FC3473BA00@dotat.at> <4C890EFD.9040407@dcrocker.net> <p0624085bc8aec16bf112@[10.20.30.158]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <p0624085bc8aec16bf112@[10.20.30.158]>
User-Agent: Mutt/1.5.18 (2008-05-17)
Subject: Re: [apps-discuss] "organization's top level domain"
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Sep 2010 17:17:12 -0000

On Thu, Sep 09, 2010 at 09:54:04AM -0700, Paul Hoffman wrote:
> You're not going to like this, but -1 for a sad reason: the principal domain name for Example Corp. is www.example.com, not example.com.
> 

Really?

We need to work out exactly what we mean by "domain name", then.

A

-- 
Andrew Sullivan
ajs@shinkuro.com
Shinkuro, Inc.

From fanf2@hermes.cam.ac.uk  Thu Sep  9 10:36:35 2010
Return-Path: <fanf2@hermes.cam.ac.uk>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7A6933A677E for <apps-discuss@core3.amsl.com>; Thu,  9 Sep 2010 10:36:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.687
X-Spam-Level: 
X-Spam-Status: No, score=-5.687 tagged_above=-999 required=5 tests=[AWL=0.912,  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 F-IVhvLS8KCG for <apps-discuss@core3.amsl.com>; Thu,  9 Sep 2010 10:36:33 -0700 (PDT)
Received: from ppsw-33.csi.cam.ac.uk (ppsw-33.csi.cam.ac.uk [131.111.8.133]) by core3.amsl.com (Postfix) with ESMTP id 352773A68A0 for <apps-discuss@ietf.org>; Thu,  9 Sep 2010 10:36:33 -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]:37111) by ppsw-33.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.159]:25) with esmtpa (EXTERNAL:fanf2) id 1Otl3R-0007dR-iQ (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Thu, 09 Sep 2010 18:36:57 +0100
Received: from fanf2 (helo=localhost) by hermes-1.csi.cam.ac.uk (hermes.cam.ac.uk) with local-esmtp id 1Otl3R-0007Ng-OJ (Exim 4.67) (return-path <fanf2@hermes.cam.ac.uk>); Thu, 09 Sep 2010 18:36:57 +0100
Date: Thu, 9 Sep 2010 18:36:57 +0100
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-1.csi.cam.ac.uk
To: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <p0624085bc8aec16bf112@[10.20.30.158]>
Message-ID: <alpine.LSU.2.00.1009091831150.31615@hermes-1.csi.cam.ac.uk>
References: <4C83BE0C.6090802@dcrocker.net> <20100905182354.GB30466@x27.adm.denic.de> <4C866DA9.8080302@dcrocker.net> <20100907181308.GN489@shinkuro.com> <852F873D-44C1-4D9C-AA1C-50FC3473BA00@dotat.at> <4C890EFD.9040407@dcrocker.net> <p0624085bc8aec16bf112@[10.20.30.158]>
User-Agent: Alpine 2.00 (LSU 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: Tony Finch <fanf2@hermes.cam.ac.uk>
Cc: dcrocker@bbiw.net, "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] "organization's top level domain"
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Sep 2010 17:36:36 -0000

On Thu, 9 Sep 2010, Paul Hoffman wrote:
>
> >So I vote for "organization's principal domain(s)".
>
> You're not going to like this, but -1 for a sad reason: the principal
> domain name for Example Corp. is www.example.com, not example.com.

Spoilsport :-) I did consider this problem, but I think it is dealt
with by the context. Here's the edited RFC 2142 section 2:

   For well known names that are not related to specific protocols, only
   the organization's principal domain(s) is/are required to be valid.
   For example, if an Internet service provider's domain name is
   COMPANY.COM, then the <ABUSE@COMPANY.COM> address must be valid and
   supported, even though the customers whose activity generates
   complaints use hosts with more specific domain names like
   SHELL1.COMPANY.COM.  Note, however, that it is valid and encouraged
   to support mailbox names for sub-domains, as appropriate.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
HUMBER THAMES DOVER WIGHT PORTLAND: NORTH BACKING WEST OR NORTHWEST, 5 TO 7,
DECREASING 4 OR 5, OCCASIONALLY 6 LATER IN HUMBER AND THAMES. MODERATE OR
ROUGH. RAIN THEN FAIR. GOOD.

From dcrocker@bbiw.net  Thu Sep  9 10:40:41 2010
Return-Path: <dcrocker@bbiw.net>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 469DD3A68E9 for <apps-discuss@core3.amsl.com>; Thu,  9 Sep 2010 10:40:41 -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 E43+YvHb5Yz6 for <apps-discuss@core3.amsl.com>; Thu,  9 Sep 2010 10:40:33 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id 29E963A6AAD for <apps-discuss@ietf.org>; Thu,  9 Sep 2010 10:40:25 -0700 (PDT)
Received: from [26.195.47.226] (m3f0536d0.tmodns.net [208.54.5.63]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id o89HeVuB007150 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Sep 2010 10:40:39 -0700
X-User-Agent: K-9 Mail for Android
References: <4C83BE0C.6090802@dcrocker.net> <20100905182354.GB30466@x27.adm.denic.de> <4C866DA9.8080302@dcrocker.net> <20100907181308.GN489@shinkuro.com> <852F873D-44C1-4D9C-AA1C-50FC3473BA00@dotat.at> <4C890EFD.9040407@dcrocker.net> <p0624085bc8aec16bf112@[10.20.30.158]> <alpine.LSU.2.00.1009091831150.31615@hermes-1.csi.cam.ac.uk>
In-Reply-To: <alpine.LSU.2.00.1009091831150.31615@hermes-1.csi.cam.ac.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
From: Dave Crocker <dcrocker@bbiw.net>
Date: Thu, 09 Sep 2010 10:37:49 -0700
To: Tony Finch <dot@dotat.at>, Paul Hoffman <paul.hoffman@vpnc.org>
Message-ID: <6684db27-7589-4c97-a016-70da923f3fde@email.android.com>
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Thu, 09 Sep 2010 10:40:40 -0700 (PDT)
Cc: "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] "organization's top level domain"
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Sep 2010 17:40:41 -0000

Yeah. I do not see this as negating the definition, even though it makes for a confusing... example.

"Tony Finch" <dot@dotat.at> wrote:

>On Thu, 9 Sep 2010, Paul Hoffman wrote:
>>
>> >So I vote for "organization's principal domain(s)".
>>
>> You're not going to like this, but -1 for a sad reason: the principal
>> domain name for Example Corp. is www.example.com, not example.com.
>
>Spoilsport :-) I did consider this problem, but I think it is dealt
>with by the context. Here's the edited RFC 2142 section 2:
>
>   For well known names that are not related to specific protocols, only
>   the organization's principal domain(s) is/are required to be valid.
>   For example, if an Internet service provider's domain name is
>   COMPANY.COM, then the <ABUSE@COMPANY.COM> address must be valid and
>   supported, even though the customers whose activity generates
>   complaints use hosts with more specific domain names like
>   SHELL1.COMPANY.COM.  Note, however, that it is valid and encouraged
>   to support mailbox names for sub-domains, as appropriate.
>
>Tony.
>-- 
>f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
>HUMBER THAMES DOVER WIGHT PORTLAND: NORTH BACKING WEST OR NORTHWEST, 5 TO 7,
>DECREASING 4 OR 5, OCCASIONALLY 6 LATER IN HUMBER AND THAMES. MODERATE OR
>ROUGH. RAIN THEN FAIR. GOOD.



d/

-- 
Dave Crocker
bbiw.net

(via mobile)

From paul.hoffman@vpnc.org  Thu Sep  9 11:10:17 2010
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D27F13A696E for <apps-discuss@core3.amsl.com>; Thu,  9 Sep 2010 11:10:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.167
X-Spam-Level: 
X-Spam-Status: No, score=-101.167 tagged_above=-999 required=5 tests=[AWL=0.879, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, 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 ELLi6KvPJ2kH for <apps-discuss@core3.amsl.com>; Thu,  9 Sep 2010 11:10:10 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 6C98C3A6904 for <apps-discuss@ietf.org>; Thu,  9 Sep 2010 11:10:09 -0700 (PDT)
Received: from [10.20.30.158] (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o89IAODD043043 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Sep 2010 11:10:25 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p0624085fc8aed3732ae9@[10.20.30.158]>
In-Reply-To: <6684db27-7589-4c97-a016-70da923f3fde@email.android.com>
References: <4C83BE0C.6090802@dcrocker.net> <20100905182354.GB30466@x27.adm.denic.de> <4C866DA9.8080302@dcrocker.net> <20100907181308.GN489@shinkuro.com> <852F873D-44C1-4D9C-AA1C-50FC3473BA00@dotat.at> <4C890EFD.9040407@dcrocker.net> <p0624085bc8aec16bf112@[10.20.30.158]> <alpine.LSU.2.00.1009091831150.31615@hermes-1.csi.cam.ac.uk> <6684db27-7589-4c97-a016-70da923f3fde@email.android.com>
Date: Thu, 9 Sep 2010 11:10:23 -0700
To: Dave Crocker <dcrocker@bbiw.net>, Tony Finch <dot@dotat.at>
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
Cc: "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] "organization's top level domain"
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Sep 2010 18:10:19 -0000

So, let me amend my "-1" to "-1 unless there is an example to make it clear we don't mean www.example.com".

--Paul Hoffman, Director
--VPN Consortium

From dcrocker@bbiw.net  Thu Sep  9 11:19:58 2010
Return-Path: <dcrocker@bbiw.net>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 923253A6850 for <apps-discuss@core3.amsl.com>; Thu,  9 Sep 2010 11:19:57 -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 umLloG6KCtIC for <apps-discuss@core3.amsl.com>; Thu,  9 Sep 2010 11:19:54 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id 1E4F43A67F3 for <apps-discuss@ietf.org>; Thu,  9 Sep 2010 11:19:53 -0700 (PDT)
Received: from [26.195.47.226] (m3f0536d0.tmodns.net [208.54.5.63]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id o89IIs0J009083 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Sep 2010 11:19:18 -0700
X-User-Agent: K-9 Mail for Android
References: <4C83BE0C.6090802@dcrocker.net> <20100905182354.GB30466@x27.adm.denic.de> <4C866DA9.8080302@dcrocker.net> <20100907181308.GN489@shinkuro.com> <852F873D-44C1-4D9C-AA1C-50FC3473BA00@dotat.at> <4C890EFD.9040407@dcrocker.net> <p0624085bc8aec16bf112@[10.20.30.158]> <alpine.LSU.2.00.1009091831150.31615@hermes-1.csi.cam.ac.uk> <6684db27-7589-4c97-a016-70da923f3fde@email.android.com> <p0624085fc8aed3732ae9@[10.20.30.158]>
In-Reply-To: <p0624085fc8aed3732ae9@[10.20.30.158]>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
From: Dave Crocker <dcrocker@bbiw.net>
Date: Thu, 09 Sep 2010 11:16:14 -0700
To: Paul Hoffman <paul.hoffman@vpnc.org>, Tony Finch <dot@dotat.at>
Message-ID: <950cb363-5e2a-45c7-b48c-72fef9c0f903@email.android.com>
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Thu, 09 Sep 2010 11:20:18 -0700 (PDT)
Cc: "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] "organization's top level domain"
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Sep 2010 18:19:58 -0000

My point was that I do not understand applying "principal doman" and coming up with your example, unless the requirement is to cover every possible misinterpretation.

"Paul Hoffman" <paul.hoffman@vpnc.org> wrote:

>So, let me amend my "-1" to "-1 unless there is an example to make it clear we don't mean www.example.com".
>
>--Paul Hoffman, Director
>--VPN Consortium



d/

-- 
Dave Crocker
bbiw.net

(via mobile)

From vkg@bell-labs.com  Thu Sep  9 14:44:30 2010
Return-Path: <vkg@bell-labs.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 780CC3A680F; Thu,  9 Sep 2010 14:44:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.449
X-Spam-Level: 
X-Spam-Status: No, score=-102.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rK4xzNNg6OBd; Thu,  9 Sep 2010 14:44:12 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by core3.amsl.com (Postfix) with ESMTP id 8C3E53A681A; Thu,  9 Sep 2010 14:44:10 -0700 (PDT)
Received: from umail.lucent.com (h135-3-40-63.lucent.com [135.3.40.63]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id o89LiAgT023509 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Sep 2010 16:44:11 -0500 (CDT)
Received: from shoonya.ih.lucent.com (Knoppix-135185238233.ih.lucent.com [135.185.238.233]) by umail.lucent.com (8.13.8/TPES) with ESMTP id o89LiAFD009212; Thu, 9 Sep 2010 16:44:10 -0500 (CDT)
Message-ID: <4C89558D.4000401@bell-labs.com>
Date: Thu, 09 Sep 2010 16:45:49 -0500
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.11) Gecko/20100720 Fedora/3.0.6-1.fc12 Thunderbird/3.0.6
MIME-Version: 1.0
To: draft-ietf-geopriv-arch@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
Cc: rbarnes@bbn.com, acooper@cdt.org, IESG IESG <iesg@ietf.org>, "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: [apps-discuss] Apps-team review of draft-ietf-geopriv-arch-02
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Sep 2010 21:44:30 -0000

I have been selected as the Applications Area Review Team reviewer for 
this draft (for background on apps-review, please see 
http://www.apps.ietf.org/content/applications-area-review-team).

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

Document: draft-ietf-geopriv-arch-02
Reviewer: Vijay K. Gurbani
Review Date: Sept-9-2010
IETF Last Call Date: Unknown
IESG Telechat Date: Sept-9-2010

Summary: This draft is ready for publication as a BCP.

Major issues: None.
Minor issues: 2
Nits: 2

I realize that this review is a day late, my apologies.  However,
none of the review comments below are blocking so attending to
them should be low impact.  The document is very well written.

Minor issues:
-------------
1) In S2.2 you state that a LO can contain geodetic or civic
  location data.  Common sense argues that they should be the
  same in the sense that they point to the same physical
  location.  However, is there a requirement to that effect in
  the document (if there is, please disregard.  But I do not
  recall reading such a requirement)?  What if they are different?

2) In Figure 3, there is a vertical line from LG to Device.
  What information is sent on that interface?  It is clear that
  the vertical line from the Device to LG is sending some manner
  of positioning data that the device wants to transmit.  But
  I am not sure what information the vertical line from LG to Device
  carries.

  There is some text later on --- on the top of page 15 --- that
  says "The LG provides assistance data to the Device".  If so,
  then a label containing this information should be placed
  in Figure 3.

Nits:
------
1) S2.2, "Device" definition: Do you mean "The physical device ..."
  when you wrote "The technical device ..."?

2)  S3.2.2, opening sentence.  "Some performing ..." What is the
  object there?  Some what?

Thanks,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
Email: vkg@{alcatel-lucent.com,bell-labs.com,acm.org}
Web:   http://ect.bell-labs.com/who/vkg/

From john-ietf@jck.com  Thu Sep  9 20:20:06 2010
Return-Path: <john-ietf@jck.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A9B323A69F2 for <apps-discuss@core3.amsl.com>; Thu,  9 Sep 2010 20:20:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.367
X-Spam-Level: 
X-Spam-Status: No, score=-102.367 tagged_above=-999 required=5 tests=[AWL=0.232, 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 okCd6uzUBwjj for <apps-discuss@core3.amsl.com>; Thu,  9 Sep 2010 20:20:02 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 79D4C3A694F for <apps-discuss@ietf.org>; Thu,  9 Sep 2010 20:20:02 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1OtuA8-0007T0-To; Thu, 09 Sep 2010 23:20:29 -0400
Date: Thu, 09 Sep 2010 23:20:28 -0400
From: John C Klensin <john-ietf@jck.com>
To: Andrew Sullivan <ajs@shinkuro.com>, apps-discuss@ietf.org
Message-ID: <50C55FBBE3915A7A9B252D61@PST.JCK.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
Subject: Re: [apps-discuss] "organization's top level domain"
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Sep 2010 03:20:06 -0000

--On Thursday, September 09, 2010 13:17 -0400 Andrew Sullivan
<ajs@shinkuro.com> wrote:

> On Thu, Sep 09, 2010 at 09:54:04AM -0700, Paul Hoffman wrote:
>> You're not going to like this, but -1 for a sad reason: the
>> principal domain name for Example Corp. is www.example.com,
>> not example.com.
>> 
> 
> Really?
> 
> We need to work out exactly what we mean by "domain name",
> then.

Andrew, I'm ok with ""organization's principal domain(s)",
subject to two qualifications:

	(1) Some example or explanation (along the line's of
	Paul's comments) appears.   And
	
	(2) You (or someone else) floats this by the
	DNSEXT/DNSOPS community and make sure that it doesn't
	either surprise or horrify them.  I appreciate your
	contributions, Peter's, and others to this conversation,
	but the about the last thing we need in the DNS
	terminology space is yet another term that is used
	differently in different communities.
	
	
As far as "exactly what we mean by 'domain name'" is concerned
and as you know, that is _not_ worked out and is a good example
of why we keep having these discussions.   I have seen that
term, sometimes used just interchangeably with "domain", widely
used to describe:
	
	* A label
	
	* An FQDN but not some appreciated name
	
	* An FQDN or an abbreviated name
	
	* The portion of an FQDN when the first (leftmost) label
	(and associated label-separating period when relevant)
	is removed.

In addition, it is unclear from some writing whether a "domain
name" must be in dot-separated-label form or whether it can also
refer to the internal, length-value form.

Unfortunately, part of the current discussion on the IETF list
about the terminology used in
draft-saintandre-tls-server-id-check and RFC 4985 strongly
illustrates the point.

There is reason to despair of getting the derived terms right if
the basic ones don't have well-defined definitions.

      john




From lear@cisco.com  Mon Sep 13 02:40:55 2010
Return-Path: <lear@cisco.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9A44C3A6950 for <apps-discuss@core3.amsl.com>; Mon, 13 Sep 2010 02:40:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.998
X-Spam-Level: 
X-Spam-Status: No, score=-107.998 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001, 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 SVrkAn7Sn9Dg for <apps-discuss@core3.amsl.com>; Mon, 13 Sep 2010 02:40:53 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 2A6A63A67EC for <apps-discuss@ietf.org>; Mon, 13 Sep 2010 02:40:53 -0700 (PDT)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAAOPjUxAZnwM/2dsb2JhbACDGp4rcaM5iXyRBYJwgVx0BIon
X-IronPort-AV: E=Sophos;i="4.56,358,1280707200";  d="scan'208,217";a="158682368"
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-2.cisco.com with ESMTP; 13 Sep 2010 09:41:19 +0000
Received: from dhcp-wdata-vlan18-22-251.cisco.com (dhcp-wdata-vlan18-22-251.cisco.com [144.254.22.251]) by rtp-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o8D9fHJP018401; Mon, 13 Sep 2010 09:41:18 GMT
Message-ID: <4C8DF1CC.2010306@cisco.com>
Date: Mon, 13 Sep 2010 11:41:32 +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.9) Gecko/20100825 Lightning/1.0b2 Thunderbird/3.1.3
MIME-Version: 1.0
To: "apps-discuss@ietf.org" <apps-discuss@ietf.org>
X-Enigmail-Version: 1.1.1
Content-Type: multipart/alternative; boundary="------------000309060906020709010203"
Cc: draft-ietf-grow-mrt@tools.ietf.org, grow-chairs@tools.ietf.org
Subject: [apps-discuss] Apps Area Review of draft-grow-mrt-13
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Sep 2010 09:40:55 -0000

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

 I have been selected as the Applications Area Review Team reviewer for
this draft (for background on apps-review, please see
http://www.apps.ietf.org/content/applications-area-review-team).

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

Document: draft-ietf-grow-mrt-13
Reviewer: Eliot Lear
Review Date: 13 September 2010

Summary:

This draft is not yet ready for publication, but will require at least a
review of the issues mentioned below.

Major Issues:

This specification suffers from two complicating effects:

    * The fact that it already deployed, and hence is attempting to
      document existing practice; and
    * there is substantial "feature creep" in an attempt to continue to
      use the same collector, while extending capabilities.

Consideration should be given to breaking this effort into two: an
informational document that explains what is going on today, and a new
clean specification for standardization.

This specification could perhaps benefit from review of those who
developed IPFIX and PSAMP.  In particular, consistent terminology would
be nice.

Specific issues:

   1. Section 3.  There is no versioning information in the packet
      header.  This means that format upgrades will require external
      information to identify their changes.
   2. Section 3. There are several 32-bit timestamp values, which will
      mean that a wrap will occur in 2038.  For most *protocols* this is
      not a problem because one can manage with wrap conditions. 
      However, this is a data export format meant for researchers. 
      Researchers tend to want to do longitudinal studies, and as such,
      it may prove difficult to use conventional wrapping mechanisms.  
      (The 32bit value also varies from the POSIX time_t definition; a
      nit to be sure, but an annoying one).
   3. Sections 5.2 and 5.3.  There are  two table dump mechanisms
      (TABLE_DUMP and TABLE_DUMP_V2) defined.  This  complicates
      implementations without any justification.  Very limited guidance
      is given as to when one is needed versus the other.  The authors
      are advised to strongly consider deprecating TABLE_DUMP in favor
      of TABLE_DUMP_V2, or in the alternative, providing much clearer
      guidance as to when one should be used by an exporter.  This
      problem replays itself throughout the document in other
      circumstances (c.f.., BGP4MP_MESSAGE & BGP4MP_MESSAGE_AS4).
   4. In Section 5.4.1 & 5.4.2 it appears that IANA-specified values are
      listed, and are as such limited.  This seems unnecessarily
      restrictive, and would force updates of this document when work is
      done on BGP.  That might prove necessary anyway becasue there may
      be insufficient length information to ignore a single table entry.
   5. The TABLE_DUMP_V2 subtypes are not sufficiently specified.  A good
      example of how to specify something sufficiently is the MRT
      header, where all fields are defined and explained.  For instance,
      in the case of TABLE_DUMP*, is a single entry encoded with format
      specified in Figures 3-5?  the use of records versus messages
      isn't clear.  In part this is due to inconsistent or poorly
      defined use of terminology (record versus message) A diagram or
      example should be included in the text that says:

>    The MRT records which follow the PEER_INDEX_TABLE MRT record contain
>    the RIB entries and include a header which specifies a sequence
>    number, NLRI, and a count of the number of RIB entries which follow.

   6. There is not a single example in the document.  This further
      hinders implementation of an already unclear specification.


Minor issues:

   7. Section 4.  There seems to be a desired to deprecate START and
      I_AM_DEAD from the outset.  While I can easily envision uses for
      this information, and for archival purposes, it seems useful to
      indicate start and end collection times (e.g., it may be useful to
      know when someone thought they were collecting routing updates but
      had in fact none), perhaps a bit more discussion and guidance
      should be given to implementors.
   8. The document really should have a glossary of terms.


Nits:

   9. NLRI is not defined.


Other (not within Apps charter):

  10. Section 8: Security Considerations do not describe data privacy
      concerns (consider the case where information being exported might
      indicate connectivity of specific individuals or systems, as could
      be possible with IGP information).  A fuller review is recommended.


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body text="#000000" bgcolor="#ffffff">
    I have been selected as the Applications Area Review Team reviewer
    for this draft (for background on apps-review, please see
    <a class="moz-txt-link-freetext" href="http://www.apps.ietf.org/content/applications-area-review-team">http://www.apps.ietf.org/content/applications-area-review-team</a>).<br>
    <br>
    Please resolve these comments along with any other Last Call
    comments you may receive. Please wait for direction from your
    document shepherd or AD before posting a new version of the draft.<br>
    <br>
    Document: draft-ietf-grow-mrt-13<br>
    Reviewer: Eliot Lear<br>
    Review Date: 13 September 2010<br>
    <br>
    Summary:<br>
    <br>
    This draft is not yet ready for publication, but will require at
    least a review of the issues mentioned below.<br>
    <br>
    Major Issues:<br>
    <br>
    This specification suffers from two complicating effects:<br>
    <ul>
      <li>The fact that it already deployed, and hence is attempting to
        document existing practice; and<br>
      </li>
      <li>there is substantial "feature creep" in an attempt to continue
        to use the same collector, while extending capabilities.</li>
    </ul>
    Consideration should be given to breaking this effort into two: an
    informational document that explains what is going on today, and a
    new clean specification for standardization.<br>
    <br>
    This specification could perhaps benefit from review of those who
    developed IPFIX and PSAMP.  In particular, consistent terminology
    would be nice.<br>
    <br>
    Specific issues:<br>
    <br>
    <ol>
      <li>Section 3.  There is no versioning information in the packet
        header.  This means that format upgrades will require external
        information to identify their changes.</li>
      <li>Section 3. There are several 32-bit timestamp values, which
        will mean that a wrap will occur in 2038.  For most <b>protocols</b>
        this is not a problem because one can manage with wrap
        conditions.  However, this is a data export format meant for
        researchers.  Researchers tend to want to do longitudinal
        studies, and as such, it may prove difficult to use conventional
        wrapping mechanisms.   (The 32bit value also varies from the
        POSIX time_t definition; a nit to be sure, but an annoying one).</li>
      <li>Sections 5.2 and 5.3.  There are  two table dump mechanisms
        (TABLE_DUMP and TABLE_DUMP_V2) defined.  This  complicates
        implementations without any justification.  Very limited
        guidance is given as to when one is needed versus the other. 
        The authors are advised to strongly consider deprecating
        TABLE_DUMP in favor of TABLE_DUMP_V2, or in the alternative,
        providing much clearer guidance as to when one should be used by
        an exporter.  This problem replays itself throughout the
        document in other circumstances (c.f.., BGP4MP_MESSAGE &amp;
        BGP4MP_MESSAGE_AS4).</li>
      <li>In Section 5.4.1 &amp; 5.4.2 it appears that IANA-specified
        values are listed, and are as such limited.  This seems
        unnecessarily restrictive, and would force updates of this
        document when work is done on BGP.  That might prove necessary
        anyway becasue there may be insufficient length information to
        ignore a single table entry.</li>
      <li>The TABLE_DUMP_V2 subtypes are not sufficiently specified.  A
        good example of how to specify something sufficiently is the MRT
        header, where all fields are defined and explained.  For
        instance, in the case of TABLE_DUMP*, is a single entry encoded
        with format specified in Figures 3-5?  the use of records versus
        messages isn't clear.  In part this is due to inconsistent or
        poorly defined use of terminology (record versus message) A
        diagram or example should be included in the text that says:</li>
    </ol>
    <blockquote type="cite">
      <pre class="newpage">   The MRT records which follow the PEER_INDEX_TABLE MRT record contain
   the RIB entries and include a header which specifies a sequence
   number, NLRI, and a count of the number of RIB entries which follow.
</pre>
    </blockquote>
    <ol start="6">
      <li>There is not a single example in the document.  This further
        hinders implementation of an already unclear specification.<br>
      </li>
    </ol>
    <br>
    Minor issues:<br>
    <br>
    <ol start="7">
      <li>Section 4.  There seems to be a desired to deprecate START and
        I_AM_DEAD from the outset.  While I can easily envision uses for
        this information, and for archival purposes, it seems useful to
        indicate start and end collection times (e.g., it may be useful
        to know when someone thought they were collecting routing
        updates but had in fact none), perhaps a bit more discussion and
        guidance should be given to implementors.</li>
      <li>The document really should have a glossary of terms.</li>
    </ol>
    <br>
    Nits:<br>
    <ol start="9">
      <li>NLRI is not defined.</li>
    </ol>
    <br>
    Other (not within Apps charter):<br>
    <ol start="10">
      <li>Section 8: Security Considerations do not describe data
        privacy concerns (consider the case where information being
        exported might indicate connectivity of specific individuals or
        systems, as could be possible with IGP information).  A fuller
        review is recommended.<br>
      </li>
    </ol>
  </body>
</html>

--------------000309060906020709010203--

From alexey.melnikov@isode.com  Wed Sep 15 04:41:10 2010
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CC3933A6953 for <apps-discuss@core3.amsl.com>; Wed, 15 Sep 2010 04:41:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.401
X-Spam-Level: 
X-Spam-Status: No, score=-102.401 tagged_above=-999 required=5 tests=[AWL=0.198, 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 ut+NeoFIgWgt for <apps-discuss@core3.amsl.com>; Wed, 15 Sep 2010 04:41:09 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id 2DBCA3A6830 for <Apps-Discuss@ietf.org>; Wed, 15 Sep 2010 04:41:06 -0700 (PDT)
Received: from [172.16.2.125] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <TJCw6gBIEMc8@rufus.isode.com>; Wed, 15 Sep 2010 12:41:31 +0100
Message-ID: <4C90B0E4.5080502@isode.com>
Date: Wed, 15 Sep 2010 12:41:24 +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: Apps-Discuss@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [apps-discuss] Moving "mailserver" URI scheme from "Provisional" to "Historic"
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Sep 2010 11:41:11 -0000

RFC 1738, Section 4 says:

   mailserver       Access to data available from mail servers.


That is all it says. I don't believe this URI scheme is well defined and 
I also don't believe that it was ever deployed (corrections to the last 
statement are welcomed).

Any objections of declaring this Historic?


From alexey.melnikov@isode.com  Wed Sep 15 08:22:46 2010
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4D0C93A6995 for <apps-discuss@core3.amsl.com>; Wed, 15 Sep 2010 08:22:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.404
X-Spam-Level: 
X-Spam-Status: No, score=-102.404 tagged_above=-999 required=5 tests=[AWL=0.195, 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 SARIRkq08hgT for <apps-discuss@core3.amsl.com>; Wed, 15 Sep 2010 08:22:45 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id 118E83A696B for <Apps-Discuss@ietf.org>; Wed, 15 Sep 2010 08:22:45 -0700 (PDT)
Received: from [172.16.2.125] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <TJDk3QBIEFak@rufus.isode.com>; Wed, 15 Sep 2010 16:23:09 +0100
Message-ID: <4C90E4CA.2070201@isode.com>
Date: Wed, 15 Sep 2010 16:22:50 +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: Bjoern Hoehrmann <derhoermi@gmx.net>
References: <4C90B0E4.5080502@isode.com> <nfh196hdj8q6a9u7icil6segc7qmnmc24p@hive.bjoern.hoehrmann.de>
In-Reply-To: <nfh196hdj8q6a9u7icil6segc7qmnmc24p@hive.bjoern.hoehrmann.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Apps-Discuss@ietf.org
Subject: Re: [apps-discuss] Moving "mailserver" URI scheme from "Provisional" to "Historic"
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Sep 2010 15:22:46 -0000

Bjoern Hoehrmann wrote:

>* Alexey Melnikov wrote:  
>
>>RFC 1738, Section 4 says:
>>
>>  mailserver       Access to data available from mail servers.
>>
>>That is all it says. I don't believe this URI scheme is well defined and 
>>I also don't believe that it was ever deployed (corrections to the last 
>>statement are welcomed).
>>
>>Any objections of declaring this Historic?
>>    
>>
>I note that http://ftp.ics.uci.edu/pub/ietf/uri/historical.html sort of
>did that already. (And I am intrigued by "An SGML-based URC Service".)
>
I suppose I need to double check with Paul. I didn't know he tried to 
standardize it.

>(Wouldn't uri-review@ietf.org or uri@w3.org be a better place to ask?)
>
Ok, Sent to the former.
But I think discussing this topic here is also appropriate.

>  
>

From paul.hoffman@vpnc.org  Wed Sep 15 08:44:11 2010
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 561943A69A5 for <apps-discuss@core3.amsl.com>; Wed, 15 Sep 2010 08:44:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.238
X-Spam-Level: 
X-Spam-Status: No, score=-101.238 tagged_above=-999 required=5 tests=[AWL=0.808, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, 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 9whWlc5JMD3i for <apps-discuss@core3.amsl.com>; Wed, 15 Sep 2010 08:44:09 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 2382D3A68FE for <Apps-Discuss@ietf.org>; Wed, 15 Sep 2010 08:44:08 -0700 (PDT)
Received: from [10.20.30.158] (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o8FFiUO2057102 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 15 Sep 2010 08:44:31 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p062408d9c8b69a457d5a@[10.20.30.158]>
In-Reply-To: <4C90E4CA.2070201@isode.com>
References: <4C90B0E4.5080502@isode.com> <nfh196hdj8q6a9u7icil6segc7qmnmc24p@hive.bjoern.hoehrmann.de> <4C90E4CA.2070201@isode.com>
Date: Wed, 15 Sep 2010 08:44:28 -0700
To: Alexey Melnikov <alexey.melnikov@isode.com>, Bjoern Hoehrmann <derhoermi@gmx.net>
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
Cc: Apps-Discuss@ietf.org
Subject: Re: [apps-discuss] Moving "mailserver" URI scheme from "Provisional" to "Historic"
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Sep 2010 15:44:12 -0000

At 4:22 PM +0100 9/15/10, Alexey Melnikov wrote:
>Bjoern Hoehrmann wrote:
>
>>* Alexey Melnikov wrote: 
>>>RFC 1738, Section 4 says:
>>>
>>> mailserver       Access to data available from mail servers.
>>>
>>>That is all it says. I don't believe this URI scheme is well defined and I also don't believe that it was ever deployed (corrections to the last statement are welcomed).
>>>
>>>Any objections of declaring this Historic?
>>>  
>>>
>>I note that http://ftp.ics.uci.edu/pub/ietf/uri/historical.html sort of
>>did that already. (And I am intrigued by "An SGML-based URC Service".)
>>
>I suppose I need to double check with Paul. I didn't know he tried to standardize it.
>
>>(Wouldn't uri-review@ietf.org or uri@w3.org be a better place to ask?)
>>
>Ok, Sent to the former.
>But I think discussing this topic here is also appropriate.

Nuke it. No one could come up with examples of it being used, much less interoperably.

--Paul Hoffman, Director
--VPN Consortium

From derhoermi@gmx.net  Wed Sep 15 06:16:41 2010
Return-Path: <derhoermi@gmx.net>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E62F43A6BE0 for <apps-discuss@core3.amsl.com>; Wed, 15 Sep 2010 06:16:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.905
X-Spam-Level: 
X-Spam-Status: No, score=-2.905 tagged_above=-999 required=5 tests=[AWL=-0.306, 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 JFwW4sCuTFNY for <apps-discuss@core3.amsl.com>; Wed, 15 Sep 2010 06:16:32 -0700 (PDT)
Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.23]) by core3.amsl.com (Postfix) with SMTP id D43023A6BEF for <Apps-Discuss@ietf.org>; Wed, 15 Sep 2010 06:16:29 -0700 (PDT)
Received: (qmail invoked by alias); 15 Sep 2010 13:16:53 -0000
Received: from dslb-094-222-148-042.pools.arcor-ip.net (EHLO hive) [94.222.148.42] by mail.gmx.net (mp037) with SMTP; 15 Sep 2010 15:16:53 +0200
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX19oHKsrqLdo6OPnUg31vClnOvYkoNYce4Cgj6HYT8 04a8tgcxpfuYjH
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Alexey Melnikov <alexey.melnikov@isode.com>
Date: Wed, 15 Sep 2010 15:16:55 +0200
Message-ID: <nfh196hdj8q6a9u7icil6segc7qmnmc24p@hive.bjoern.hoehrmann.de>
References: <4C90B0E4.5080502@isode.com>
In-Reply-To: <4C90B0E4.5080502@isode.com>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Y-GMX-Trusted: 0
X-Mailman-Approved-At: Wed, 15 Sep 2010 08:53:59 -0700
Cc: Apps-Discuss@ietf.org
Subject: Re: [apps-discuss] Moving "mailserver" URI scheme from "Provisional" to "Historic"
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Sep 2010 13:16:41 -0000

* Alexey Melnikov wrote:
>RFC 1738, Section 4 says:
>
>   mailserver       Access to data available from mail servers.
>
>That is all it says. I don't believe this URI scheme is well defined and 
>I also don't believe that it was ever deployed (corrections to the last 
>statement are welcomed).
>
>Any objections of declaring this Historic?

I note that http://ftp.ics.uci.edu/pub/ietf/uri/historical.html sort of
did that already. (And I am intrigued by "An SGML-based URC Service".)

(Wouldn't uri-review@ietf.org or uri@w3.org be a better place to ask?)
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 

From ted.ietf@gmail.com  Wed Sep 15 14:54:05 2010
Return-Path: <ted.ietf@gmail.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7DDA83A6A11; Wed, 15 Sep 2010 14:54:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.701
X-Spam-Level: 
X-Spam-Status: No, score=-1.701 tagged_above=-999 required=5 tests=[AWL=0.898,  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 kEPw65gh-V6C; Wed, 15 Sep 2010 14:54:02 -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 3198E3A6999; Wed, 15 Sep 2010 14:53:59 -0700 (PDT)
Received: by qyk9 with SMTP id 9so642351qyk.10 for <multiple recipients>; Wed, 15 Sep 2010 14:54:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=YtJii37tI9nAe12CA4Wz0u2v+2DezE0WgneyvPXrHQU=; b=NjLlqIDgOqn4SFiE7LcWENUToho/xVTUYRLmcO1pxNubdewGRnw4J3eF/prsAe2en1 upIVvYh0O8R8UOL3G6ZY5r27gz7Li9penE62KdcVRWZr/iQ+ZUNE2XEu93nmrJLFQ1qu 4N09aNnInIEGIoxrEgDr1EXDfEEmmDz37dMAw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=pUzXP2Dpm505k3WZlWpUwj8mhxo7HvhKSqV0UwTLPPnnn/INjm6DdfjVKyVYcMSLPS RdszZU/JxH11nPx9RXGTtQIHlGW8z/R2B9tdoRbkrDaJRr5gGsVzXIfvMuuPB7Q3RyZq q5WMjgFD1Bqwjo2UHKJEo9E1ktUVeJiLg2ZfM=
MIME-Version: 1.0
Received: by 10.224.2.85 with SMTP id 21mr1578138qai.74.1284587664363; Wed, 15 Sep 2010 14:54:24 -0700 (PDT)
Received: by 10.229.249.208 with HTTP; Wed, 15 Sep 2010 14:54:24 -0700 (PDT)
Date: Wed, 15 Sep 2010 14:54:24 -0700
Message-ID: <AANLkTinAd5ZEbiaXjZqKKzHDbwMSCAUZQmz3boG9aMVc@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
To: IESG <iesg@ietf.org>, Apps Discuss <discuss@ietf.org>,  nikos.mavrogiannopoulos@esat.kuleuven.be, dkg@fifthhorseman.net
Content-Type: text/plain; charset=ISO-8859-1
Subject: [apps-discuss] [APPS-REVIEW]Review of draft-mavrogiannopoulos-rfc5081bis
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Sep 2010 21:54:05 -0000

I have been selected as the Applications Area Review Team reviewer for
this draft (for background on apps-review, please see
http://www.apps.ietf.org/content/applications-area-review-team).

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

Document: draft-mavrogiannopoulos-rfc5081bis
Reviewer: Ted Hardie
Review Date: September 15th, 2010
On agenda of 2010-09-23 IESG telechat

Summary: This draft is almost ready for publication, but there remain
a few issues which need clarification in the text.

Major Issues:

The introduction to the document says:

"The proposed extensions are backward compatible with the current TLS
   specification, so that existing client and server implementations
   that make use of X.509 certificates are not affected."

but the Appendix, which describes the changes from RFC 5081,  notes that
there is a major and incompatible change:


   This document incorporates a major and incompatible change in the
   "Server Certificate" and "Client Certificate" TLS messages.  This
   change requires the subkey IDs used for TLS authentication to marked
   explicitely in the handshake procedure.  This was decided in order to
   place no limitation on the OpenPGP certificates' contents that can be
   used with with this protocol.

   [RFC5081] required that an OpenPGP key or subkey was marked with the
   authentication flag and thus would have failed if this flag was not
   set, or this flag was set in more than one subkeys.  The protocol in
   this memo has no such limitation.

Section 3 indicates that the presence of the "cert_type" extension signals
the ability to handle the new handshake procedure; it also, unfortunately,
contains some language which appears contradictory.  In section 3.2,
it says:

   If the server receives a client hello that contains the "cert_type"
   extension and chooses a cipher suite that requires a certificate,
   then two outcomes are possible.  The server MUST either select a
   certificate type from the certificate_types field in the extended
   client hello or terminate the session with a fatal alert of type
   "unsupported_certificate".

It goes on to say, however:

  It is perfectly legal for a server to ignore this message.  In that
   case the normal TLS handshake should be used and, other certificate
   types than the default MUST NOT be used.

The combination of these issues leaves potential confusion about how compatible
this mechanism is with previously defined behavior and how mandatory support
is.  Reading through it, the intent appears to be:

Use the "cert_type" extension mechanism to signal support for a
non-compatible handshake mechanism.
   If the client and server support the "cert_type" extension, the
spec requires that servers either select
    a certificate type from the certificate_types field or fail.
Servers remain free not to support the extension at all.

Some language clean-up to make this clear seems to me required.  I
would personally
probably integrate the appendix material into the introduction.  I
would also suggest
clarifying in Section 3 which statements apply to the negotiation after it has
been established that "cert_type" is supported by both parties.


Minor Issues:

The IANA section should probably note that the pointer for the "cert_type"
TLS extension should be updated to this document.


Nits:

From stpeter@stpeter.im  Wed Sep 15 19:13:24 2010
Return-Path: <stpeter@stpeter.im>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 62C4D3A6AF4 for <apps-discuss@core3.amsl.com>; Wed, 15 Sep 2010 19:13:24 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jJplc8wTBK+h for <apps-discuss@core3.amsl.com>; Wed, 15 Sep 2010 19:13:21 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id A11153A6AF0 for <discuss@apps.ietf.org>; Wed, 15 Sep 2010 19:13:21 -0700 (PDT)
Received: from squire.local (dsl-228-11.dynamic-dsl.frii.net [216.17.228.11]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id A4184400EE; Wed, 15 Sep 2010 20:18:04 -0600 (MDT)
Message-ID: <4C917D51.8050500@stpeter.im>
Date: Wed, 15 Sep 2010 20:13:37 -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.1.12) Gecko/20100824 Thunderbird/3.0.7
MIME-Version: 1.0
To: dcrocker@bbiw.net
References: <4C83BE0C.6090802@dcrocker.net>
In-Reply-To: <4C83BE0C.6090802@dcrocker.net>
X-Enigmail-Version: 1.0.1
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Apps Discuss <discuss@apps.ietf.org>
Subject: Re: [apps-discuss] "organization's top level domain"
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Sep 2010 02:13:24 -0000

On 9/5/10 9:58 AM, Dave CROCKER wrote:
> Folks,
> 
> Howdy.
> 
> I'm looking for a nomenclature suggestion...
> 
> RFC 2142 user the phrase "organization's top level domain".  This refers
> to the string that is delegated to the organization and provides the
> root of any sub-tree to the DNS that they create.  Around the world and
> around the DNS, this 'root' will have two or more fields, such as
> bbiw.net or ucl.ac.uk.
> 
> An erratum has been filed on the phrase.  I take it as being a result of
> "top level domain" becoming entrenched to mean only the right-most field
> of a domain name. The stuff that is delegated from the root of the DNS.

Dave, I was just now processing errata and came across the erratum you
referenced in this thread:

http://www.rfc-editor.org/errata_search.php?eid=1764

To close the loop, I'm going to set this erratum to "hold for document
update" with the consensus terminology (i.e., "organization's principal
domain name").

Peter

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



From dhc@dcrocker.net  Wed Sep 15 22:21:59 2010
Return-Path: <dhc@dcrocker.net>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E69A13A6AF9 for <apps-discuss@core3.amsl.com>; Wed, 15 Sep 2010 22:21:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.552
X-Spam-Level: 
X-Spam-Status: No, score=-6.552 tagged_above=-999 required=5 tests=[AWL=0.047,  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 0qKjR4nXJfQd for <apps-discuss@core3.amsl.com>; Wed, 15 Sep 2010 22:21:58 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id 30F5F3A6AEE for <discuss@apps.ietf.org>; Wed, 15 Sep 2010 22:21:58 -0700 (PDT)
Received: from [192.168.1.4] (ppp-68-120-198-81.dsl.pltn13.pacbell.net [68.120.198.81]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id o8G5MHj8016473 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Wed, 15 Sep 2010 22:22:23 -0700
Message-ID: <4C91A986.2090209@dcrocker.net>
Date: Wed, 15 Sep 2010 22:22:14 -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.9) Gecko/20100825 Thunderbird/3.1.3
MIME-Version: 1.0
To: Peter Saint-Andre <stpeter@stpeter.im>
References: <4C83BE0C.6090802@dcrocker.net> <4C917D51.8050500@stpeter.im>
In-Reply-To: <4C917D51.8050500@stpeter.im>
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, 15 Sep 2010 22:22:23 -0700 (PDT)
Cc: Apps Discuss <discuss@apps.ietf.org>
Subject: Re: [apps-discuss] "organization's top level domain"
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Sep 2010 05:22:00 -0000

WFM.  tnx.

d/

On 9/15/2010 7:13 PM, Peter Saint-Andre wrote:
> To close the loop, I'm going to set this erratum to "hold for document
> update" with the consensus terminology (i.e., "organization's principal
> domain name").

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From duerst@it.aoyama.ac.jp  Wed Sep 15 22:35:27 2010
Return-Path: <duerst@it.aoyama.ac.jp>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 10DC23A688F for <apps-discuss@core3.amsl.com>; Wed, 15 Sep 2010 22:35:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.866
X-Spam-Level: 
X-Spam-Status: No, score=-99.866 tagged_above=-999 required=5 tests=[AWL=-0.076, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3dx865yUqJ-c for <apps-discuss@core3.amsl.com>; Wed, 15 Sep 2010 22:35:25 -0700 (PDT)
Received: from scintmta01.scbb.aoyama.ac.jp (scintmta01.scbb.aoyama.ac.jp [133.2.253.33]) by core3.amsl.com (Postfix) with ESMTP id 957513A68AF for <Apps-Discuss@ietf.org>; Wed, 15 Sep 2010 22:35:02 -0700 (PDT)
Received: from scmse02.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta01.scbb.aoyama.ac.jp (secret/secret) with SMTP id o8G5ZM3g023647 for <Apps-Discuss@ietf.org>; Thu, 16 Sep 2010 14:35:22 +0900
Received: from (unknown [133.2.206.133]) by scmse02.scbb.aoyama.ac.jp with smtp id 31b2_5a28_334fddd0_c154_11df_aa5a_001d096c5782; Thu, 16 Sep 2010 14:35:22 +0900
Received: from [IPv6:::1] ([133.2.210.1]:39440) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S1448CE2> for <Apps-Discuss@ietf.org> from <duerst@it.aoyama.ac.jp>; Thu, 16 Sep 2010 14:35:22 +0900
Message-ID: <4C91AC93.60902@it.aoyama.ac.jp>
Date: Thu, 16 Sep 2010 14:35:15 +0900
From: =?ISO-8859-1?Q?=22Martin_J=2E_D=FCrst=22?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>
References: <4C90B0E4.5080502@isode.com>	<nfh196hdj8q6a9u7icil6segc7qmnmc24p@hive.bjoern.hoehrmann.de>	<4C90E4CA.2070201@isode.com> <p062408d9c8b69a457d5a@[10.20.30.158]>
In-Reply-To: <p062408d9c8b69a457d5a@[10.20.30.158]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: "uri-review@ietf.org" <uri-review@ietf.org>, Bjoern Hoehrmann <derhoermi@gmx.net>, Apps-Discuss@ietf.org
Subject: Re: [apps-discuss] Moving "mailserver" URI scheme from "Provisional" to "Historic"
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Sep 2010 05:35:27 -0000

On 2010/09/16 0:44, Paul Hoffman wrote:
> At 4:22 PM +0100 9/15/10, Alexey Melnikov wrote:
>> Bjoern Hoehrmann wrote:
>>
>>> * Alexey Melnikov wrote:
>>>> RFC 1738, Section 4 says:
>>>>
>>>> mailserver       Access to data available from mail servers.

>>>> Any objections of declaring this Historic?

>>> I note that http://ftp.ics.uci.edu/pub/ietf/uri/historical.html sort of
>>> did that already. (And I am intrigued by "An SGML-based URC Service".)
>>>
>> I suppose I need to double check with Paul. I didn't know he tried to standardize it.

> Nuke it. No one could come up with examples of it being used, much less interoperably.

Yes. It proposed to add subject and body to the functionality of a 
mailto: URI, but this is now possible with mailto: URIs (see 
http://tools.ietf.org/html/rfc2368 and 
https://datatracker.ietf.org/doc/draft-duerst-mailto-bis/), so it's also 
clearly technically obsolete.

Regards,    Martin.

-- 
#-# Martin J. Dürst, Professor, Aoyama Gakuin University
#-# http://www.sw.it.aoyama.ac.jp   mailto:duerst@it.aoyama.ac.jp

From nikos.mavrogiannopoulos@esat.kuleuven.be  Thu Sep 16 01:51:10 2010
Return-Path: <nikos.mavrogiannopoulos@esat.kuleuven.be>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1D97B3A6900; Thu, 16 Sep 2010 01:51:10 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BFPvtirKcWv3; Thu, 16 Sep 2010 01:51:08 -0700 (PDT)
Received: from cavuit02.kulnet.kuleuven.be (cavuit02.kulnet.kuleuven.be [134.58.240.44]) by core3.amsl.com (Postfix) with ESMTP id 54E5E3A6820; Thu, 16 Sep 2010 01:51:08 -0700 (PDT)
Received: from smtps01.kuleuven.be (smtpshost01.kulnet.kuleuven.be [134.58.240.74]) by cavuit02.kulnet.kuleuven.be (Postfix) with ESMTP id 6ED5351C004; Thu, 16 Sep 2010 10:51:26 +0200 (CEST)
Received: from hydrogen.esat.kuleuven.be (hydrogen.esat.kuleuven.be [134.58.56.153]) by smtps01.kuleuven.be (Postfix) with ESMTP id 46AFD31E707; Thu, 16 Sep 2010 10:51:26 +0200 (CEST)
Received: from localhost (webmail2.cc.kuleuven.be [134.58.242.4]) by hydrogen.esat.kuleuven.be (Postfix) with ESMTP id 57AC348002; Thu, 16 Sep 2010 10:51:26 +0200 (CEST)
Received: from 78-23-65-223.access.telenet.be (78-23-65-223.access.telenet.be [78.23.65.223]) by webmail2.kuleuven.be (IMP) with HTTP  for <nikos@mailserv.esat.kuleuven.be>; Thu, 16 Sep 2010 10:51:26 +0200
Message-ID: <1284627086.4c91da8ec0004@webmail2.kuleuven.be>
Date: Thu, 16 Sep 2010 10:51:26 +0200
X-Kuleuven: This mail passed the K.U.Leuven mailcluster
From: nikos <Nikos.Mavrogiannopoulos@esat.kuleuven.be>
To: Ted Hardie <ted.ietf@gmail.com>
References: <AANLkTinAd5ZEbiaXjZqKKzHDbwMSCAUZQmz3boG9aMVc@mail.gmail.com>
In-Reply-To: <AANLkTinAd5ZEbiaXjZqKKzHDbwMSCAUZQmz3boG9aMVc@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: Internet Messaging Program (IMP) 3.2-cvs
X-Originating-IP: 78.23.65.223
X-KULeuven-Information: Katholieke Universiteit Leuven
X-KULeuven-Scanned: Found to be clean
X-KULeuven-Envelope-From: nikos.mavrogiannopoulos@esat.kuleuven.be
X-Mailman-Approved-At: Thu, 16 Sep 2010 08:09:42 -0700
Cc: dkg@fifthhorseman.net, nikos.mavrogiannopoulos@esat.kuleuven.be, IESG <iesg@ietf.org>, Apps Discuss <discuss@ietf.org>
Subject: Re: [apps-discuss] [APPS-REVIEW]Review of draft-mavrogiannopoulos-rfc5081bis
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: nikos.mavrogiannopoulos@esat.kuleuven.be
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Sep 2010 09:14:02 -0000

Quoting Ted Hardie <ted.ietf@gmail.com>:

> I have been selected as the Applications Area Review Team reviewer
> for
> this draft (for background on apps-review, please see
> http://www.apps.ietf.org/content/applications-area-review-team).
> Please resolve these comments along with any other Last Call
> comments
> you may receive. Please wait for direction from your document
> shepherd
> or AD before posting a new version of the draft.
> Document: draft-mavrogiannopoulos-rfc5081bis
> Reviewer: Ted Hardie
> Review Date: September 15th, 2010
> On agenda of 2010-09-23 IESG telechat

Hello,
 Thank you for the comments. I have some clarifications for the text and 
some proposed changes, inline.

> The introduction to the document says:
> 
> "The proposed extensions are backward compatible with the current
> TLS
>    specification, so that existing client and server implementations
>    that make use of X.509 certificates are not affected."
> 
> but the Appendix, which describes the changes from RFC 5081,  notes
> that
> there is a major and incompatible change:
> 
>    This document incorporates a major and incompatible change in the
>    "Server Certificate" and "Client Certificate" TLS messages.  This
>    change requires the subkey IDs used for TLS authentication to
> marked
>    explicitely in the handshake procedure.  This was decided in order
> to
>    place no limitation on the OpenPGP certificates' contents that can
> be
>    used with with this protocol.
> 
>    [RFC5081] required that an OpenPGP key or subkey was marked with
> the
>    authentication flag and thus would have failed if this flag was
> not
>    set, or this flag was set in more than one subkeys.  The protocol
> in
>    this memo has no such limitation.

Please note that those two paragraphs refer to different documents.
The phrase "The proposed extensions are backward compatible with the 
current TLS specification" (RFC5246) and the appendix refers to 
experimental RFC5081 from which there are incompatible changes. If it is 
ok with you after this clarification, I'll leave this text as is.

 
> Section 3 indicates that the presence of the "cert_type" extension
> signals
> the ability to handle the new handshake procedure; it also,
> unfortunately,
> contains some language which appears contradictory.  In section 3.2,
> it says:
> 
>    If the server receives a client hello that contains the
> "cert_type"
>    extension and chooses a cipher suite that requires a certificate,
>    then two outcomes are possible.  The server MUST either select a
>    certificate type from the certificate_types field in the extended
>    client hello or terminate the session with a fatal alert of type
>    "unsupported_certificate".
> 
> It goes on to say, however:
> 
>   It is perfectly legal for a server to ignore this message.  In
> that
>    case the normal TLS handshake should be used and, other
> certificate
>    types than the default MUST NOT be used.

You are right here also on the intention of the text. Would removing the 
paragraph:
   "It is perfectly legal for a server to ignore this message.  In that
   case the normal TLS handshake should be used and, other certificate
   types than the default MUST NOT be used."
make the text more clear for you?

This paragraph was intended as a clarification on the last sentence of 
the previous paragraph:
"Servers that only support X.509 certificates MAY omit including the
"cert_type" extension in the extended server hello."
but might be misunderstood, thus removing it should resolve that issue.

> Some language clean-up to make this clear seems to me required.  I
> would personally
> probably integrate the appendix material into the introduction.  I
> would also suggest
> clarifying in Section 3 which statements apply to the negotiation
> after it has
> been established that "cert_type" is supported by both parties.

The text has been based on RFC2246-RFC5246 structure of describing the 
handshake procedure and it lists the handshake messages that change for 
this method. I believe all statements in section 3 apply to the 
handshake procedure. If something is not clear please let me know.

> Minor Issues:
> The IANA section should probably note that the pointer for the
> "cert_type"
> TLS extension should be updated to this document.

Would this change
"This document uses a registry and the "cert_type" extension originally 
defined inRFC5081. Existing IANA references should be updated to
point to this document."
be ok with you?


best regards,
Nikos


From ted.ietf@gmail.com  Thu Sep 16 09:41:06 2010
Return-Path: <ted.ietf@gmail.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 628A63A69CE; Thu, 16 Sep 2010 09:41:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.746
X-Spam-Level: 
X-Spam-Status: No, score=-1.746 tagged_above=-999 required=5 tests=[AWL=0.853,  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 oPdu6x8L4vj9; Thu, 16 Sep 2010 09:41:02 -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 323663A69E1; Thu, 16 Sep 2010 09:40:43 -0700 (PDT)
Received: by qyk9 with SMTP id 9so1438522qyk.10 for <multiple recipients>; Thu, 16 Sep 2010 09:41:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=5pIablQ+NdQ/QTMD6SO56G+6bfYgzquJGDlMzPqJlaE=; b=Ryj5hh0BaWwLvv0r4TgE6FLdI9zc9z4voiSiqJa7/z5tLbdWBtFa0uJ5hfS4xdArAr GMfLM8T/vkeRqir3NdS6Lxki56ER78vdeeziHX/fy6ZhnZT+WdCMgu+sDXiGrvspqFHw yJeylB4QGS3Dij+8V9zLaw/N2thnm0OdEL25M=
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=AKNe4CZDb+eGnxfFH9vBYops9GqkSwRkqRAeaYMPG5gC/qBFHSdmiWKsVKQkWy1t/5 PB0MgUQlpoGQMd9F3Xatsme0jh9B5qdReP8tGJHvy663ti1ZqedyebEvwGEu3tEkccku nprzgEFEOTq44EoUbrYUif/sHhaxptOdZ1AX4=
MIME-Version: 1.0
Received: by 10.224.34.212 with SMTP id m20mr2256753qad.397.1284655265113; Thu, 16 Sep 2010 09:41:05 -0700 (PDT)
Received: by 10.229.249.208 with HTTP; Thu, 16 Sep 2010 09:41:05 -0700 (PDT)
In-Reply-To: <1284627086.4c91da8ec0004@webmail2.kuleuven.be>
References: <AANLkTinAd5ZEbiaXjZqKKzHDbwMSCAUZQmz3boG9aMVc@mail.gmail.com> <1284627086.4c91da8ec0004@webmail2.kuleuven.be>
Date: Thu, 16 Sep 2010 09:41:05 -0700
Message-ID: <AANLkTimY-Zc-W41G6ZDER+GiKsniqeE0B4pK0MSo-K3U@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
To: nikos.mavrogiannopoulos@esat.kuleuven.be
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: dkg@fifthhorseman.net, IESG <iesg@ietf.org>, Apps Discuss <discuss@ietf.org>
Subject: Re: [apps-discuss] [APPS-REVIEW]Review of draft-mavrogiannopoulos-rfc5081bis
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Sep 2010 16:41:06 -0000

Hi Nikos,

Thanks for the quick reply, some comments in-line.

On Thu, Sep 16, 2010 at 1:51 AM, nikos
<Nikos.Mavrogiannopoulos@esat.kuleuven.be> wrote:
> Quoting Ted Hardie <ted.ietf@gmail.com>:
>
>> I have been selected as the Applications Area Review Team reviewer
>> for
>> this draft (for background on apps-review, please see
>> http://www.apps.ietf.org/content/applications-area-review-team).
>> Please resolve these comments along with any other Last Call
>> comments
>> you may receive. Please wait for direction from your document
>> shepherd
>> or AD before posting a new version of the draft.
>> Document: draft-mavrogiannopoulos-rfc5081bis
>> Reviewer: Ted Hardie
>> Review Date: September 15th, 2010
>> On agenda of 2010-09-23 IESG telechat
>
> Hello,
> =A0Thank you for the comments. I have some clarifications for the text an=
d
> some proposed changes, inline.
>
>> The introduction to the document says:
>>
>> "The proposed extensions are backward compatible with the current
>> TLS
>> =A0 =A0specification, so that existing client and server implementations
>> =A0 =A0that make use of X.509 certificates are not affected."
>>
>> but the Appendix, which describes the changes from RFC 5081, =A0notes
>> that
>> there is a major and incompatible change:
>>
>> =A0 =A0This document incorporates a major and incompatible change in the
>> =A0 =A0"Server Certificate" and "Client Certificate" TLS messages. =A0Th=
is
>> =A0 =A0change requires the subkey IDs used for TLS authentication to
>> marked
>> =A0 =A0explicitely in the handshake procedure. =A0This was decided in or=
der
>> to
>> =A0 =A0place no limitation on the OpenPGP certificates' contents that ca=
n
>> be
>> =A0 =A0used with with this protocol.
>>
>> =A0 =A0[RFC5081] required that an OpenPGP key or subkey was marked with
>> the
>> =A0 =A0authentication flag and thus would have failed if this flag was
>> not
>> =A0 =A0set, or this flag was set in more than one subkeys. =A0The protoc=
ol
>> in
>> =A0 =A0this memo has no such limitation.
>
> Please note that those two paragraphs refer to different documents.
> The phrase "The proposed extensions are backward compatible with the
> current TLS specification" (RFC5246) and the appendix refers to
> experimental RFC5081 from which there are incompatible changes. If it is
> ok with you after this clarification, I'll leave this text as is.
>

The final decision is, of course, up to the iesg.  My personal take is that
"backwards compatible" is liable to cause confusion in this context.  It us=
es
the current extensions mechanism and thus has the current framework's
ability to detect when an extension is not supported.  But the current text
seems to be trying a bit too hard to say "Don't worry, X509 users, this won=
't
hurt a bit."  May I suggest:

"The proposed extensions are signaled within the current extensions
framework[TLS],
so that existing client and server implementations that support only
X.509 certificates
and do not support this extension will not be affected."

I'd also suggest adding an explicit citation to the Appendix, noting
that it is not
backwards compatible with 5081, but it is a standard extension to  TLS
as set out
in RFC 5246.

are backward compatible with the current
>> TLS
>>    specification, so that existing client and server implementations
>>    that make use of X.509 certificates are not affected."


>
>> Section 3 indicates that the presence of the "cert_type" extension
>> signals
>> the ability to handle the new handshake procedure; it also,
>> unfortunately,
>> contains some language which appears contradictory. =A0In section 3.2,
>> it says:
>>
>> =A0 =A0If the server receives a client hello that contains the
>> "cert_type"
>> =A0 =A0extension and chooses a cipher suite that requires a certificate,
>> =A0 =A0then two outcomes are possible. =A0The server MUST either select =
a
>> =A0 =A0certificate type from the certificate_types field in the extended
>> =A0 =A0client hello or terminate the session with a fatal alert of type
>> =A0 =A0"unsupported_certificate".
>>
>> It goes on to say, however:
>>
>> =A0 It is perfectly legal for a server to ignore this message. =A0In
>> that
>> =A0 =A0case the normal TLS handshake should be used and, other
>> certificate
>> =A0 =A0types than the default MUST NOT be used.
>
> You are right here also on the intention of the text. Would removing the
> paragraph:
> =A0 "It is perfectly legal for a server to ignore this message. =A0In tha=
t
> =A0 case the normal TLS handshake should be used and, other certificate
> =A0 types than the default MUST NOT be used."
> make the text more clear for you?
>

Yes, I think that would remove the ambiguity, as it leaves the
standard extension
processing understood.


> This paragraph was intended as a clarification on the last sentence of
> the previous paragraph:
> "Servers that only support X.509 certificates MAY omit including the
> "cert_type" extension in the extended server hello."
> but might be misunderstood, thus removing it should resolve that issue.
>
>> Some language clean-up to make this clear seems to me required. =A0I
>> would personally
>> probably integrate the appendix material into the introduction. =A0I
>> would also suggest
>> clarifying in Section 3 which statements apply to the negotiation
>> after it has
>> been established that "cert_type" is supported by both parties.
>
> The text has been based on RFC2246-RFC5246 structure of describing the
> handshake procedure and it lists the handshake messages that change for
> this method. I believe all statements in section 3 apply to the
> handshake procedure. If something is not clear please let me know.
>
>> Minor Issues:
>> The IANA section should probably note that the pointer for the
>> "cert_type"
>> TLS extension should be updated to this document.
>
> Would this change
> "This document uses a registry and the "cert_type" extension originally
> defined inRFC5081. Existing IANA references should be updated to
> point to this document."
> be ok with you?
>

Yes, that sounds fine.

Thanks again for your response,

Ted


>
> best regards,
> Nikos
>
>

From alexey.melnikov@isode.com  Fri Sep 17 02:42:50 2010
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 57AD43A6C0A for <apps-discuss@core3.amsl.com>; Fri, 17 Sep 2010 02:42:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.447
X-Spam-Level: 
X-Spam-Status: No, score=-102.447 tagged_above=-999 required=5 tests=[AWL=0.152, 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 Nfi5JWxQiisU for <apps-discuss@core3.amsl.com>; Fri, 17 Sep 2010 02:42:49 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id AEF683A6C04 for <Apps-Discuss@ietf.org>; Fri, 17 Sep 2010 02:42:48 -0700 (PDT)
Received: from [192.168.1.124] ((unknown) [62.3.217.253])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <TJM4MABIEBEe@rufus.isode.com>; Fri, 17 Sep 2010 10:43:12 +0100
X-SMTP-Protocol-Errors: NORDNS
Message-ID: <4C933818.4000102@isode.com>
Date: Fri, 17 Sep 2010 10:42:48 +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: Apps-Discuss@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [apps-discuss] Apps Area WG (APPSAWG)
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Sep 2010 09:42:50 -0000

Greetings,

Peter and I talked about this again and we would like to followup on the 
discussion in Maastricht about creating an Application Area working 
group for helping with important documents which don't fit in other 
existing working groups.

Peter and I received some (private) positive feedback before the
Maastricht IETF. The discussion during the Apps Area meeting was a bit
controversial.

We've heard people saying that this is solving a wrong problem. We've
heard comments like "you guys are overworked, but the new WG is not the 
fix for that". We've heard people voicing their concern about possible 
abuse of the WG. We've heard people saying that this is a good 
experiment to try and the community wouldn't know for sure if this is a 
good idea or not until we try.

I probably didn't sound very convincing during the Apps Area meeting,
but I got impression that during one-on-one followup discussions with
people who objected (or raised concerns), I was able to change their
opinion. In particular I showed multiple examples of documents that 
would have benefited from being a product of such working group.

So having heard all arguments and after thinking more about this, Peter 
and I are still thinking that forming such WG is a good idea. We are 
also thinking that based on raised concern it would be a good idea to 
put a specific restriction on how long this WG would exist, before it 
gets closed, or has to be rechartered.

Thanks,
Peter and Alexey, as Apps ADs.

P.S. I am likely to add the proposed WG Charter (largely unchanged from 
what I've sent out before Maastricht, but I will repost) to IESG agenda 
for September 23rd. *If* IESG is happy with initial review, this will go 
out for external review. I am then going on holidays for 3 weeks. This 
will give people enough extra time to comment/nit pick on the Charter.

If this WG is going to be created, I would personally prefer to create 
it before Beijing. I don't expect that it will actually need a meeting 
in Beijing.


From mnot@mnot.net  Fri Sep 17 05:51:03 2010
Return-Path: <mnot@mnot.net>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1AE433A684D for <apps-discuss@core3.amsl.com>; Fri, 17 Sep 2010 05:51:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.965
X-Spam-Level: 
X-Spam-Status: No, score=-104.965 tagged_above=-999 required=5 tests=[AWL=-2.366, 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 7LTXCU876OQ7 for <apps-discuss@core3.amsl.com>; Fri, 17 Sep 2010 05:50:58 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by core3.amsl.com (Postfix) with ESMTP id C54D13A6948 for <Apps-Discuss@ietf.org>; Fri, 17 Sep 2010 05:50:57 -0700 (PDT)
Received: from chancetrain-lm.mnot.net (unknown [118.209.78.64]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id A7A8B22E247; Fri, 17 Sep 2010 08:51:15 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <4C933818.4000102@isode.com>
Date: Fri, 17 Sep 2010 22:51:12 +1000
Content-Transfer-Encoding: quoted-printable
Message-Id: <F180D643-7BB4-4787-B646-C1BCF5835603@mnot.net>
References: <4C933818.4000102@isode.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
X-Mailer: Apple Mail (2.1081)
Cc: Apps-Discuss@ietf.org
Subject: Re: [apps-discuss] Apps Area WG (APPSAWG)
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Sep 2010 12:51:03 -0000

Alexey,

Has any consideration been giving to streaming different areas of =
general interest into separate WGs? E.g., Mail-related work has little =
to do with Web stuff (although there are common roots).=20

Some of my discomfort with it would be removed if it were more of a =
"hey, let's work on THIS general problem area" than a kitchen-sink =
approach.

Just a thought,


On 17/09/2010, at 7:42 PM, Alexey Melnikov wrote:

> Greetings,
>=20
> Peter and I talked about this again and we would like to followup on =
the discussion in Maastricht about creating an Application Area working =
group for helping with important documents which don't fit in other =
existing working groups.
>=20
> Peter and I received some (private) positive feedback before the
> Maastricht IETF. The discussion during the Apps Area meeting was a bit
> controversial.
>=20
> We've heard people saying that this is solving a wrong problem. We've
> heard comments like "you guys are overworked, but the new WG is not =
the fix for that". We've heard people voicing their concern about =
possible abuse of the WG. We've heard people saying that this is a good =
experiment to try and the community wouldn't know for sure if this is a =
good idea or not until we try.
>=20
> I probably didn't sound very convincing during the Apps Area meeting,
> but I got impression that during one-on-one followup discussions with
> people who objected (or raised concerns), I was able to change their
> opinion. In particular I showed multiple examples of documents that =
would have benefited from being a product of such working group.
>=20
> So having heard all arguments and after thinking more about this, =
Peter and I are still thinking that forming such WG is a good idea. We =
are also thinking that based on raised concern it would be a good idea =
to put a specific restriction on how long this WG would exist, before it =
gets closed, or has to be rechartered.
>=20
> Thanks,
> Peter and Alexey, as Apps ADs.
>=20
> P.S. I am likely to add the proposed WG Charter (largely unchanged =
from what I've sent out before Maastricht, but I will repost) to IESG =
agenda for September 23rd. *If* IESG is happy with initial review, this =
will go out for external review. I am then going on holidays for 3 =
weeks. This will give people enough extra time to comment/nit pick on =
the Charter.
>=20
> If this WG is going to be created, I would personally prefer to create =
it before Beijing. I don't expect that it will actually need a meeting =
in Beijing.
>=20
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss


--
Mark Nottingham     http://www.mnot.net/


From alexey.melnikov@isode.com  Fri Sep 17 06:11:02 2010
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 03DD43A6957 for <apps-discuss@core3.amsl.com>; Fri, 17 Sep 2010 06:11:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.451
X-Spam-Level: 
X-Spam-Status: No, score=-102.451 tagged_above=-999 required=5 tests=[AWL=0.148, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1jw0jQMkOEaY for <apps-discuss@core3.amsl.com>; Fri, 17 Sep 2010 06:10:53 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id 58C8C3A694D for <Apps-Discuss@ietf.org>; Fri, 17 Sep 2010 06:10:52 -0700 (PDT)
Received: from [172.16.2.111] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <TJNo9ABIECnm@rufus.isode.com>; Fri, 17 Sep 2010 14:11:16 +0100
Message-ID: <4C9368D2.4060204@isode.com>
Date: Fri, 17 Sep 2010 14:10:42 +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: Mark Nottingham <mnot@mnot.net>
References: <4C933818.4000102@isode.com> <F180D643-7BB4-4787-B646-C1BCF5835603@mnot.net>
In-Reply-To: <F180D643-7BB4-4787-B646-C1BCF5835603@mnot.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Apps-Discuss@ietf.org
Subject: Re: [apps-discuss] Apps Area WG (APPSAWG)
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Sep 2010 13:11:02 -0000

Mark Nottingham wrote:

>Alexey,
>  
>
Mark,

>Has any consideration been giving to streaming different areas of general interest into separate WGs? E.g., Mail-related work has little to do with Web stuff (although there are common roots). 
>  
>
Of course. This is not supposed to replace forwarding documents to 
existing WGs or creation of new ones.

>Some of my discomfort with it would be removed if it were more of a "hey, let's work on THIS general problem area" than a kitchen-sink approach.
>
>Just a thought,
>
>
>On 17/09/2010, at 7:42 PM, Alexey Melnikov wrote:
>  
>
>>Greetings,
>>
>>Peter and I talked about this again and we would like to followup on the discussion in Maastricht about creating an Application Area working group for helping with important documents which don't fit in other existing working groups.
>>
>>Peter and I received some (private) positive feedback before the
>>Maastricht IETF. The discussion during the Apps Area meeting was a bit
>>controversial.
>>
>>We've heard people saying that this is solving a wrong problem. We've
>>heard comments like "you guys are overworked, but the new WG is not the fix for that". We've heard people voicing their concern about possible abuse of the WG. We've heard people saying that this is a good experiment to try and the community wouldn't know for sure if this is a good idea or not until we try.
>>
>>I probably didn't sound very convincing during the Apps Area meeting,
>>but I got impression that during one-on-one followup discussions with
>>people who objected (or raised concerns), I was able to change their
>>opinion. In particular I showed multiple examples of documents that would have benefited from being a product of such working group.
>>
>>So having heard all arguments and after thinking more about this, Peter and I are still thinking that forming such WG is a good idea. We are also thinking that based on raised concern it would be a good idea to put a specific restriction on how long this WG would exist, before it gets closed, or has to be rechartered.
>>
>>Thanks,
>>Peter and Alexey, as Apps ADs.
>>
>>P.S. I am likely to add the proposed WG Charter (largely unchanged from what I've sent out before Maastricht, but I will repost) to IESG agenda for September 23rd. *If* IESG is happy with initial review, this will go out for external review. I am then going on holidays for 3 weeks. This will give people enough extra time to comment/nit pick on the Charter.
>>
>>If this WG is going to be created, I would personally prefer to create it before Beijing. I don't expect that it will actually need a meeting in Beijing.
>>    
>>


From Claudio.Allocchio@garr.it  Fri Sep 17 06:12:29 2010
Return-Path: <Claudio.Allocchio@garr.it>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 057AA3A6955 for <apps-discuss@core3.amsl.com>; Fri, 17 Sep 2010 06:12:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.359
X-Spam-Level: 
X-Spam-Status: No, score=-0.359 tagged_above=-999 required=5 tests=[AWL=2.240,  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 aURvNki7SPb7 for <apps-discuss@core3.amsl.com>; Fri, 17 Sep 2010 06:12:25 -0700 (PDT)
Received: from cyrus.dir.garr.it (cyrus.dir.garr.it [IPv6:2001:760:0:158::29]) by core3.amsl.com (Postfix) with ESMTP id 5645D3A688C for <Apps-Discuss@ietf.org>; Fri, 17 Sep 2010 06:12:25 -0700 (PDT)
Received: from mac-allocchio3.garrtest.units.it (mac-allocchio3.garrtest.units.it [140.105.201.3]) (authenticated bits=0) by cyrus.dir.garr.it (8.14.4/8.14.4) with ESMTP id o8HDCiEx017032 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 17 Sep 2010 15:12:45 +0200 (CEST)
X-DomainKeys: Sendmail DomainKeys Filter v1.0.2 cyrus.dir.garr.it o8HDCiEx017032
DomainKey-Signature: a=rsa-sha1; s=mail; d=garr.it; c=simple; q=dns; b=OlT5BGsFE38eYpej30iYTh5UUJlZg4pH3gFwg/9FUL8igGL4b1c34sLbxW6rQtb6g Vs+nZ3ggcz3kQu9imMz5u36bZ6x59sF+s4peRU/0R0T8//Odg30sf9YXaTezF9LcMoT A2Qp6zOT/5Hua10E/xAnW7UKX4lK0ZQbUN9g7Gc=
Date: Fri, 17 Sep 2010 15:12:45 +0200 (CEST)
From: Claudio Allocchio <Claudio.Allocchio@garr.it>
X-X-Sender: claudio@mac-allocchio3.garrtest.units.it
To: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <F180D643-7BB4-4787-B646-C1BCF5835603@mnot.net>
Message-ID: <Pine.OSX.4.64.1009171509050.12455@mac-allocchio3.garrtest.units.it>
References: <4C933818.4000102@isode.com> <F180D643-7BB4-4787-B646-C1BCF5835603@mnot.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: Apps-Discuss@ietf.org
Subject: Re: [apps-discuss] Apps Area WG (APPSAWG)
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Sep 2010 13:12:29 -0000

On Fri, 17 Sep 2010, Mark Nottingham wrote:

> Alexey,
>
> Has any consideration been giving to streaming different areas of 
> general interest into separate WGs? E.g., Mail-related work has little 
> to do with Web stuff (although there are common roots).

true... hence my further question: how do you think to structure the 
potential membership of this WG? just include anybody wiling to contribute 
(as usual), asking at least a few "more experts" in each area (taken from 
the Apps-review team?) to join... ?

an "open discussion" in a WG has always made better a draft, and this is 
missing for individual submissions, true... but we need a WG which is 
capable of giving positive inputs. But in general I agree that the WS 
idea is good.


  > On 17/09/2010, at 7:42 PM, Alexey 
Melnikov wrote: >
>> Greetings,
>>
>> Peter and I talked about this again and we would like to followup on the discussion in Maastricht about creating an Application Area working group for helping with important documents which don't fit in other existing working groups.
>>
>> Peter and I received some (private) positive feedback before the
>> Maastricht IETF. The discussion during the Apps Area meeting was a bit
>> controversial.
>>
>> We've heard people saying that this is solving a wrong problem. We've
>> heard comments like "you guys are overworked, but the new WG is not the fix for that". We've heard people voicing their concern about possible abuse of the WG. We've heard people saying that this is a good experiment to try and the community wouldn't know for sure if this is a good idea or not until we try.
>>
>> I probably didn't sound very convincing during the Apps Area meeting,
>> but I got impression that during one-on-one followup discussions with
>> people who objected (or raised concerns), I was able to change their
>> opinion. In particular I showed multiple examples of documents that would have benefited from being a product of such working group.
>>
>> So having heard all arguments and after thinking more about this, Peter and I are still thinking that forming such WG is a good idea. We are also thinking that based on raised concern it would be a good idea to put a specific restriction on how long this WG would exist, before it gets closed, or has to be rechartered.
>>
>> Thanks,
>> Peter and Alexey, as Apps ADs.
>>
>> P.S. I am likely to add the proposed WG Charter (largely unchanged from what I've sent out before Maastricht, but I will repost) to IESG agenda for September 23rd. *If* IESG is happy with initial review, this will go out for external review. I am then going on holidays for 3 weeks. This will give people enough extra time to comment/nit pick on the Charter.
>>
>> If this WG is going to be created, I would personally prefer to create it before Beijing. I don't expect that it will actually need a meeting in Beijing.
>>
>> _______________________________________________
>> apps-discuss mailing list
>> apps-discuss@ietf.org
>> https://www.ietf.org/mailman/listinfo/apps-discuss
>
>
> --
> Mark Nottingham     http://www.mnot.net/
>
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss
>

------------------------------------------------------------------------------
Claudio Allocchio             G   A   R   R          Claudio.Allocchio@garr.it
                         Senior Technical Officer
tel: +39 040 3758523      Italian Academic and       G=Claudio; S=Allocchio;
fax: +39 040 3758565        Research Network         P=garr; A=garr; C=it;

            PGP Key: http://www.cert.garr.it/PGP/keys.php3#ca

From alexey.melnikov@isode.com  Fri Sep 17 06:15:52 2010
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6F4943A69A9 for <apps-discuss@core3.amsl.com>; Fri, 17 Sep 2010 06:15:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.452
X-Spam-Level: 
X-Spam-Status: No, score=-102.452 tagged_above=-999 required=5 tests=[AWL=0.147, 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 YUsQgjWigxo1 for <apps-discuss@core3.amsl.com>; Fri, 17 Sep 2010 06:15:47 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id A6FA63A69AC for <Apps-Discuss@ietf.org>; Fri, 17 Sep 2010 06:15:47 -0700 (PDT)
Received: from [172.16.2.111] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <TJNqGwBIEJQt@rufus.isode.com>; Fri, 17 Sep 2010 14:16:11 +0100
Message-ID: <4C9369F9.4030007@isode.com>
Date: Fri, 17 Sep 2010 14:15:37 +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: Mark Nottingham <mnot@mnot.net>
References: <4C933818.4000102@isode.com> <F180D643-7BB4-4787-B646-C1BCF5835603@mnot.net> <4C9368D2.4060204@isode.com>
In-Reply-To: <4C9368D2.4060204@isode.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Apps-Discuss@ietf.org
Subject: Re: [apps-discuss] Apps Area WG (APPSAWG)
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Sep 2010 13:15:52 -0000

Alexey Melnikov wrote:

> Mark Nottingham wrote:
>
>> Alexey,
>
> Mark,
>
>> Has any consideration been giving to streaming different areas of 
>> general interest into separate WGs? E.g., Mail-related work has 
>> little to do with Web stuff (although there are common roots).  
>
> Of course. This is not supposed to replace forwarding documents to 
> existing WGs or creation of new ones.

I will add some text to the proposed Charter to clarify that.

>> Some of my discomfort with it would be removed if it were more of a 
>> "hey, let's work on THIS general problem area" than a kitchen-sink 
>> approach.
>>
>> Just a thought, 
>


From barryleiba.mailing.lists@gmail.com  Fri Sep 17 10:31:54 2010
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 799093A68A4 for <apps-discuss@core3.amsl.com>; Fri, 17 Sep 2010 10:31:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.849
X-Spam-Level: 
X-Spam-Status: No, score=-2.849 tagged_above=-999 required=5 tests=[AWL=-0.250, 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 FbHOpvtYxj+R for <apps-discuss@core3.amsl.com>; Fri, 17 Sep 2010 10:31:51 -0700 (PDT)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by core3.amsl.com (Postfix) with ESMTP id CB4FB3A6845 for <Apps-Discuss@ietf.org>; Fri, 17 Sep 2010 10:31:50 -0700 (PDT)
Received: by gwb20 with SMTP id 20so1114959gwb.31 for <Apps-Discuss@ietf.org>; Fri, 17 Sep 2010 10:32:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:reply-to :in-reply-to:references:date:message-id:subject:from:to:cc :content-type; bh=WaLjAM/3GOs2tOJVLck5QGdF9ciMMpnjUcRAuCqOM0Q=; b=mNG672T+J6Yv4Wj7B/37FLfXqC4ii264v15sttAikNPlek5vFvkBqpCEwL55QuToMS yl7HJoY05PjstlXvp703IO2fwriZUpTzaRWidFnnh9WTsdyrKzyHbIj6Ngl6o9zipLNh vdxSbQOqtlY94cQq/VI7hgzIbMk6ZH24/mp6U=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; b=pMc2qso5im6lhMhPuUjzFpl7ligi5m0UT50swotzeXGegQRpcw0bShft++NIr0E5cK m40+7yM2bLDhNGu2hqazhL2CsacZTOJaWn1DATveUVdfIHl6/1WS6o7oqV0eDSafLfgC C8dj+u6RsQ7hbBDMlQ9rAjuzzrRwZgtVbjsyU=
MIME-Version: 1.0
Received: by 10.100.252.18 with SMTP id z18mr5931400anh.83.1284744735463; Fri, 17 Sep 2010 10:32:15 -0700 (PDT)
Received: by 10.42.5.15 with HTTP; Fri, 17 Sep 2010 10:32:15 -0700 (PDT)
In-Reply-To: <4C933818.4000102@isode.com>
References: <4C933818.4000102@isode.com>
Date: Fri, 17 Sep 2010 13:32:15 -0400
Message-ID: <AANLkTimkcNbb2nbOT=k33Pf5dviNRjZ1x0=7BWC2mo+h@mail.gmail.com>
From: Barry Leiba <barryleiba.mailing.lists@gmail.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Apps-Discuss@ietf.org
Subject: Re: [apps-discuss] Apps Area WG (APPSAWG)
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: barryleiba@computer.org
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Sep 2010 17:31:54 -0000

> P.S. I am likely to add the proposed WG Charter (largely unchanged from what
> I've sent out before Maastricht, but I will repost) to IESG agenda for
> September 23rd.

That doesn't give us much time to review it... can you repost it here
right away?

> If this WG is going to be created, I would personally prefer to create it
> before Beijing. I don't expect that it will actually need a meeting in
> Beijing.

On the contrary, I would expect it to meet at every IETF meeting,
*replacing* (or joining) the current apparea general session.  As time
goes on, we can see how much time the combined functions of this WG
and the apparea session need, and decide whether we should split
anything out.  But keeping that 2.5-hour monday morning session as the
only app-area plenary will help avoid the increased schedule conflicts
that some (including I) worry about.

Barry

From stpeter@stpeter.im  Fri Sep 17 10:41:51 2010
Return-Path: <stpeter@stpeter.im>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6D37E3A681A for <apps-discuss@core3.amsl.com>; Fri, 17 Sep 2010 10:41:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.518
X-Spam-Level: 
X-Spam-Status: No, score=-102.518 tagged_above=-999 required=5 tests=[AWL=0.081, 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 UHxd3SpX1Kfu for <apps-discuss@core3.amsl.com>; Fri, 17 Sep 2010 10:41:49 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id 5836F3A6803 for <apps-discuss@ietf.org>; Fri, 17 Sep 2010 10:41:49 -0700 (PDT)
Received: from dhcp-64-101-72-245.cisco.com (dhcp-64-101-72-245.cisco.com [64.101.72.245]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 58DA340077 for <apps-discuss@ietf.org>; Fri, 17 Sep 2010 11:46:41 -0600 (MDT)
Message-ID: <4C93A875.1010002@stpeter.im>
Date: Fri, 17 Sep 2010 11:42:13 -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.1.12) Gecko/20100824 Thunderbird/3.0.7
MIME-Version: 1.0
To: apps-discuss@ietf.org
References: <4C933818.4000102@isode.com> <AANLkTimkcNbb2nbOT=k33Pf5dviNRjZ1x0=7BWC2mo+h@mail.gmail.com>
In-Reply-To: <AANLkTimkcNbb2nbOT=k33Pf5dviNRjZ1x0=7BWC2mo+h@mail.gmail.com>
X-Enigmail-Version: 1.0.1
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [apps-discuss] Apps Area WG (APPSAWG)
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Sep 2010 17:41:51 -0000

On 9/17/10 11:32 AM, Barry Leiba wrote:

>> If this WG is going to be created, I would personally prefer to create it
>> before Beijing. I don't expect that it will actually need a meeting in
>> Beijing.
> 
> On the contrary, I would expect it to meet at every IETF meeting,
> *replacing* (or joining) the current apparea general session.  As time
> goes on, we can see how much time the combined functions of this WG
> and the apparea session need, and decide whether we should split
> anything out.  But keeping that 2.5-hour monday morning session as the
> only app-area plenary will help avoid the increased schedule conflicts
> that some (including I) worry about.

That seems like the right approach to me.

Peter

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



From alexey.melnikov@isode.com  Fri Sep 17 12:19:14 2010
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A1ED93A68B9 for <apps-discuss@core3.amsl.com>; Fri, 17 Sep 2010 12:19:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.46
X-Spam-Level: 
X-Spam-Status: No, score=-102.46 tagged_above=-999 required=5 tests=[AWL=0.139, 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 PHdbzsoybMjh for <apps-discuss@core3.amsl.com>; Fri, 17 Sep 2010 12:18:42 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id 378CF3A690E for <Apps-Discuss@ietf.org>; Fri, 17 Sep 2010 12:18:42 -0700 (PDT)
Received: from [172.16.2.111] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <TJO=KgBIECM-@rufus.isode.com>; Fri, 17 Sep 2010 20:19:06 +0100
Message-ID: <4C93BEF3.7010105@isode.com>
Date: Fri, 17 Sep 2010 20:18:11 +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: barryleiba@computer.org
References: <4C933818.4000102@isode.com> <AANLkTimkcNbb2nbOT=k33Pf5dviNRjZ1x0=7BWC2mo+h@mail.gmail.com>
In-Reply-To: <AANLkTimkcNbb2nbOT=k33Pf5dviNRjZ1x0=7BWC2mo+h@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Apps-Discuss@ietf.org
Subject: Re: [apps-discuss] Apps Area WG (APPSAWG)
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Sep 2010 19:19:15 -0000

Barry Leiba wrote:

>>P.S. I am likely to add the proposed WG Charter (largely unchanged from what
>>I've sent out before Maastricht, but I will repost) to IESG agenda for
>>September 23rd.
>>    
>>
>That doesn't give us much time to review it...
>
As I said in my earlier message, people will have about 4 weeks to 
review this while I am on holidays.

>can you repost it here
>right away?
>  
>
Ok, here is the latest proposal:

-----------------
Applications Area Working Group (APPSAWG)

The Applications Area sometimes receives proposals for the development
of specifications dealing with application-related topics that are not
in scope for an existing working group and do not justify the formation
of a new working group.

The Applications Area Working Group (APPSAWG) can serve as a forum for such
work in the IETF.  The APPSAWG accepts work items in accordance with the
consensus of the Working Group and the best judgment of the Applications 
Area
Directors, who are responsible for updating the working group milestones
as needed.  The working group meets if there are active proposals that
require intensive discussion.

Work items that are appropriate for the APPSAWG mostly fall under the
following topics:

(A) Well-defined security issues that are relevant to multiple
application technologies (e.g., draft-saintandre-tls-server-id-check).

(B) Small-scale additions to the protocol stack for HTTP and other
application technologies, mostly related to service discovery and
meta-data (e.g., RFC 5785, draft-nottingham-http-link-header, and
draft-hammer-hostmeta).

(C) Selected other work items addressing topics that historically fall
within the Applications Area, such as calendaring, date and time
formats, HTTP, internationalization, language tags, MIME, URIs and XML.

When considering whether to accept a proposed work item, the APPSAWG and
the Applications Area Directors shall take into account the following
factors, among others:

(1) Whether the WG has consensus on the suitability, importance, and
projected quality of the proposed work item.

(2) Whether there is core team of WG participants with sufficient energy
and expertise to advance the proposed work item according to the proposed
schedule.

(3) Whether there are enough WG participants who are willing to review
the work produced by the document authors or editors.

(4) Whether the Area Directors judge that wider input is needed before
accepting the proposed work item (e.g., from the IESG, IAB, or another
standards development organization).

(5) There is no existing related Working Group that is willing to recharter
to take on this work, and the document doesn't justify the formation
of a new working group.
-----------------

>>If this WG is going to be created, I would personally prefer to create it
>>before Beijing. I don't expect that it will actually need a meeting in
>>Beijing.
>>    
>>
>
>On the contrary, I would expect it to meet at every IETF meeting,
>*replacing* (or joining) the current apparea general session.
>
I think this is an implementation detail.
For now I don't know if the WG-to-be will have any documents with 
milestones before Beijing, but of course this can change.

But anyway, yes, this is fine with me as well.

>As time
>goes on, we can see how much time the combined functions of this WG
>and the apparea session need, and decide whether we should split
>anything out.  But keeping that 2.5-hour monday morning session as the
>only app-area plenary will help avoid the increased schedule conflicts
>that some (including I) worry about.
>


From nikos.mavrogiannopoulos@esat.kuleuven.be  Thu Sep 16 10:56:02 2010
Return-Path: <nikos.mavrogiannopoulos@esat.kuleuven.be>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4A4BB3A69DD; Thu, 16 Sep 2010 10:56:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.46
X-Spam-Level: 
X-Spam-Status: No, score=-2.46 tagged_above=-999 required=5 tests=[AWL=0.139,  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 XZqgOAg9rKqR; Thu, 16 Sep 2010 10:56:00 -0700 (PDT)
Received: from cavuit01.kulnet.kuleuven.be (cavuit01.kulnet.kuleuven.be [134.58.240.43]) by core3.amsl.com (Postfix) with ESMTP id 719D33A69F1; Thu, 16 Sep 2010 10:55:47 -0700 (PDT)
Received: from smtps02.kuleuven.be (smtpshost02.kulnet.kuleuven.be [134.58.240.75]) by cavuit01.kulnet.kuleuven.be (Postfix) with ESMTP id 3B6867B804A; Thu, 16 Sep 2010 19:56:05 +0200 (CEST)
Received: from hydrogen.esat.kuleuven.be (hydrogen.esat.kuleuven.be [134.58.56.153]) by smtps02.kuleuven.be (Postfix) with ESMTP id 07AA9F3863; Thu, 16 Sep 2010 19:56:05 +0200 (CEST)
Received: from localhost (webmail2.cc.kuleuven.be [134.58.242.4]) by hydrogen.esat.kuleuven.be (Postfix) with ESMTP id 2D8CE48002; Thu, 16 Sep 2010 19:56:05 +0200 (CEST)
Received: from 78-23-65-223.access.telenet.be (78-23-65-223.access.telenet.be [78.23.65.223]) by webmail2.kuleuven.be (IMP) with HTTP  for <nikos@mailserv.esat.kuleuven.be>; Thu, 16 Sep 2010 19:56:05 +0200
Message-ID: <1284659765.4c925a3595194@webmail2.kuleuven.be>
Date: Thu, 16 Sep 2010 19:56:05 +0200
X-Kuleuven: This mail passed the K.U.Leuven mailcluster
From: nikos <Nikos.Mavrogiannopoulos@esat.kuleuven.be>
To: Ted Hardie <ted.ietf@gmail.com>
References: <AANLkTinAd5ZEbiaXjZqKKzHDbwMSCAUZQmz3boG9aMVc@mail.gmail.com> <1284627086.4c91da8ec0004@webmail2.kuleuven.be> <AANLkTimY-Zc-W41G6ZDER+GiKsniqeE0B4pK0MSo-K3U@mail.gmail.com>
In-Reply-To: <AANLkTimY-Zc-W41G6ZDER+GiKsniqeE0B4pK0MSo-K3U@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: Internet Messaging Program (IMP) 3.2-cvs
X-Originating-IP: 78.23.65.223
X-KULeuven-Information: Katholieke Universiteit Leuven
X-KULeuven-Scanned: Found to be clean
X-KULeuven-Envelope-From: nikos.mavrogiannopoulos@esat.kuleuven.be
X-Mailman-Approved-At: Fri, 17 Sep 2010 15:08:20 -0700
Cc: dkg@fifthhorseman.net, IESG <iesg@ietf.org>, Apps Discuss <discuss@ietf.org>
Subject: Re: [apps-discuss] [APPS-REVIEW]Review of draft-mavrogiannopoulos-rfc5081bis
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: nikos.mavrogiannopoulos@esat.kuleuven.be
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Sep 2010 17:56:02 -0000

Hello,

 (comments inline)

Quoting Ted Hardie <ted.ietf@gmail.com>:
> > Please note that those two paragraphs refer to different
> documents.
> > The phrase "The proposed extensions are backward compatible with
> the
> > current TLS specification" (RFC5246) and the appendix refers to
> > experimental RFC5081 from which there are incompatible changes. If
> it is
> > ok with you after this clarification, I'll leave this text as is.
> >
> 
> The final decision is, of course, up to the iesg.  My personal take
> is that
> "backwards compatible" is liable to cause confusion in this context. 
> It uses
> the current extensions mechanism and thus has the current
> framework's
> ability to detect when an extension is not supported.  But the
> current text
> seems to be trying a bit too hard to say "Don't worry, X509 users,
> this won't
> hurt a bit."  

I think that the introduction serves its purpose, but I can see that the 
appendix could be misleading if read out of context. I've updated the 
appendix to make clear that the incompatibility is with RFC5081 and not 
with other documents:
   "This document incorporates a major change in the "Server 
Certificate"
   and "Client Certificate" TLS messages, that will make implementations
   following this protocol incompatible with ones following [RFC5081].
   This change requires the subkey IDs used for TLS authentication to
   marked explicitely in the handshake procedure.  This was decided in
   order to place no limitation on the OpenPGP certificates' contents
   that can be used with with this protocol."

I've uploaded a -07 version with the fixes discussed.


Thank you and best regards,
Nikos


From sm@resistor.net  Sun Sep 19 09:51:39 2010
Return-Path: <sm@resistor.net>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1A8C93A63D3 for <apps-discuss@core3.amsl.com>; Sun, 19 Sep 2010 09:51:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.769
X-Spam-Level: 
X-Spam-Status: No, score=-101.769 tagged_above=-999 required=5 tests=[AWL=-1.029, BAYES_20=-0.74, 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 ER8+0ht9yg46 for <apps-discuss@core3.amsl.com>; Sun, 19 Sep 2010 09:51:36 -0700 (PDT)
Received: from ns1.qubic.net (ns1.qubic.net [208.69.177.116]) by core3.amsl.com (Postfix) with ESMTP id 76A073A672F for <Apps-Discuss@ietf.org>; Sun, 19 Sep 2010 09:51:36 -0700 (PDT)
Received: from SUBMAN.resistor.net ([10.0.0.1]) (authenticated bits=0) by ns1.qubic.net (8.14.5.Alpha0/8.14.5.Alpha0) with ESMTP id o8JGpmUe006533 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <Apps-Discuss@ietf.org>; Sun, 19 Sep 2010 09:51:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1284915119; x=1285001519; bh=cmo3zUVORmwd3kY2GPgwNko4iAgEnakk7lfBq9DUYYU=; h=Message-Id:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=nZHFBr1vXc2RIL7363vi7ihS2lhQP37xy6lrSjj1ENPjqVKMGZk3pjdkBrVqQGGJp M/8v7/D/TTDWenzXHwJbVWBeJjhf3zRthYQgpUdCHfFbRHg3cv/oYHEQXMq+CG3ShW W+/y3u/eqhQ/uGhdjRAqICINeM1ng/mMdG8GsP0M=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1284915119; x=1285001519; bh=cmo3zUVORmwd3kY2GPgwNko4iAgEnakk7lfBq9DUYYU=; h=Message-Id:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=G2cpSMAUhOfM++aRTTxi5RBVUjMsaSw6KCU4V2rsLwQb0VgBhUC2+4WyYiD/8PhU+ VLN+AWUTU++sBncynOJGmV1/iLs3YujSAJrpWRJ/DiibhYeJWQ5OuEWAqjvYpbsC/6 +ZcXpA4ezHtHmFUtgckw49ups418+S6VGcWUFZqI=
DomainKey-Signature: a=rsa-sha1; s=mail; d=resistor.net; c=simple; q=dns; b=kOwjFke7ZQ43NDQXoZqHea+wfKDY+aSEYG7Y0SjVJpYapIWrFON8gviqC2AhP0zjz dbNL2fbsTjojNLsjfEUA4PJwoTvReYEnLcbrbKCmSEDl3qANiIs/IatUFusqA3AKaSM Fe/tSFLLy7VTL4U/1EuEx61wyLnAG/Si0ymwn1I=
Message-Id: <6.2.5.6.2.20100919093131.08d2ae30@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 19 Sep 2010 09:51:37 -0700
To: Apps-Discuss@ietf.org
From: SM <sm@resistor.net>
In-Reply-To: <4C93BEF3.7010105@isode.com>
References: <4C933818.4000102@isode.com> <AANLkTimkcNbb2nbOT=k33Pf5dviNRjZ1x0=7BWC2mo+h@mail.gmail.com> <4C93BEF3.7010105@isode.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: Re: [apps-discuss] Apps Area WG (APPSAWG)
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 19 Sep 2010 16:51:39 -0000

At 12:18 17-09-10, Alexey Melnikov wrote:
>Ok, here is the latest proposal:
>
>-----------------
>Applications Area Working Group (APPSAWG)
>
>The Applications Area sometimes receives proposals for the development
>of specifications dealing with application-related topics that are not
>in scope for an existing working group and do not justify the formation
>of a new working group.

Is it the Application Area or the Area Directors that receives the 
proposals (see Individual submissions)?

>The Applications Area Working Group (APPSAWG) can serve as a forum for such
>work in the IETF.  The APPSAWG accepts work items in accordance with the
>consensus of the Working Group and the best judgment of the Applications Area
>Directors, who are responsible for updating the working group milestones
>as needed.  The working group meets if there are active proposals that
>require intensive discussion.

If this is to be a working group, I would prefer if the acceptance 
does not require both consensus and the best judgement of the 
Application Area Directors.  The way around that would be for the 
Application Area Director to determine whether the working group 
should consider the draft.  The consensus is then gauged after that.

Regards,
-sm 


From alexey.melnikov@isode.com  Mon Sep 20 04:48:08 2010
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 09C633A6936 for <apps-discuss@core3.amsl.com>; Mon, 20 Sep 2010 04:48:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xWjsHJqKJkE9 for <apps-discuss@core3.amsl.com>; Mon, 20 Sep 2010 04:48:05 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id 685B03A689D for <Apps-Discuss@ietf.org>; Mon, 20 Sep 2010 04:48:05 -0700 (PDT)
Received: from [192.168.1.124] ((unknown) [62.3.217.253])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <TJdKDABIEAG3@rufus.isode.com>; Mon, 20 Sep 2010 12:48:28 +0100
X-SMTP-Protocol-Errors: NORDNS
Message-ID: <4C9749EE.8050907@isode.com>
Date: Mon, 20 Sep 2010 12:47:58 +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: Apps-Discuss@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [apps-discuss] Request for reviews of draft-holsten-about-uri-scheme-04.txt
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Sep 2010 11:48:08 -0000

Hi,
IESG has received a request to consider publication of
draft-holsten-about-uri-scheme-04.txt as an RFC. I would like to solicit
reviews of this document.

Thank you,
Alexey

-- 
IETF Application Area Director, <http://www.ietf.org/iesg/members.html>
Internet Messaging Team Lead, <http://www.isode.com>
JID: same as my email address


From alexey.melnikov@isode.com  Mon Sep 20 10:00:43 2010
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7265A3A6B45 for <apps-discuss@core3.amsl.com>; Mon, 20 Sep 2010 10:00:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 28UO+9QP0x-D for <apps-discuss@core3.amsl.com>; Mon, 20 Sep 2010 10:00:42 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id DC6D53A6AAC for <Apps-Discuss@ietf.org>; Mon, 20 Sep 2010 09:55:26 -0700 (PDT)
Received: from [172.16.2.193] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <TJeSFQBIEIb3@rufus.isode.com>; Mon, 20 Sep 2010 17:55:49 +0100
Message-ID: <4C9791E6.1000701@isode.com>
Date: Mon, 20 Sep 2010 17:55:02 +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: SM <sm@resistor.net>
References: <4C933818.4000102@isode.com> <AANLkTimkcNbb2nbOT=k33Pf5dviNRjZ1x0=7BWC2mo+h@mail.gmail.com> <4C93BEF3.7010105@isode.com> <6.2.5.6.2.20100919093131.08d2ae30@resistor.net>
In-Reply-To: <6.2.5.6.2.20100919093131.08d2ae30@resistor.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Apps-Discuss@ietf.org
Subject: Re: [apps-discuss] Apps Area WG (APPSAWG)
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Sep 2010 17:00:43 -0000

SM wrote:

> At 12:18 17-09-10, Alexey Melnikov wrote:
>
>> Ok, here is the latest proposal:
>>
>> -----------------
>> Applications Area Working Group (APPSAWG)
>>
>> The Applications Area sometimes receives proposals for the development
>> of specifications dealing with application-related topics that are not
>> in scope for an existing working group and do not justify the formation
>> of a new working group.
>
> Is it the Application Area or the Area Directors that receives the 
> proposals (see Individual submissions)?

Area Directors. If you think the distinction is important in the 
Charter, I can change that.

>> The Applications Area Working Group (APPSAWG) can serve as a forum 
>> for such
>> work in the IETF.  The APPSAWG accepts work items in accordance with the
>> consensus of the Working Group and the best judgment of the 
>> Applications Area
>> Directors, who are responsible for updating the working group milestones
>> as needed.  The working group meets if there are active proposals that
>> require intensive discussion.
>
> If this is to be a working group, I would prefer if the acceptance 
> does not require both consensus and the best judgement of the 
> Application Area Directors.  The way around that would be for the 
> Application Area Director to determine whether the working group 
> should consider the draft.  The consensus is then gauged after that.

Fine with me.

Part of the reasons for the text is to allow ideas for new documents to 
work on to be initiated from the WG, not just from ADs themselves.


From tony@att.com  Mon Sep 20 13:46:54 2010
Return-Path: <tony@att.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 13A7F3A689C for <apps-discuss@core3.amsl.com>; Mon, 20 Sep 2010 13:46:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.336
X-Spam-Level: 
X-Spam-Status: No, score=-106.336 tagged_above=-999 required=5 tests=[AWL=0.263, 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 cYEkk0FdGN+K for <apps-discuss@core3.amsl.com>; Mon, 20 Sep 2010 13:46:52 -0700 (PDT)
Received: from mail161.messagelabs.com (mail161.messagelabs.com [216.82.253.115]) by core3.amsl.com (Postfix) with ESMTP id CF1D53A6956 for <apps-discuss@ietf.org>; Mon, 20 Sep 2010 13:46:52 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: tony@att.com
X-Msg-Ref: server-11.tower-161.messagelabs.com!1285015635!10449692!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [144.160.20.146]
Received: (qmail 30731 invoked from network); 20 Sep 2010 20:47:15 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpd194.enaf.sfdc.sbc.com) (144.160.20.146) by server-11.tower-161.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 20 Sep 2010 20:47:15 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd194.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id o8KKkgKw022898 for <apps-discuss@ietf.org>; Mon, 20 Sep 2010 16:46:42 -0400
Received: from klpd017.kcdc.att.com (klpd017.kcdc.att.com [135.188.40.86]) by mlpd194.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id o8KKkaXA022771 for <apps-discuss@ietf.org>; Mon, 20 Sep 2010 16:46:36 -0400
Received: from kcdc.att.com (localhost.localdomain [127.0.0.1]) by klpd017.kcdc.att.com (8.14.4/8.14.4) with ESMTP id o8KKl8LA028435 for <apps-discuss@ietf.org>; Mon, 20 Sep 2010 15:47:08 -0500
Received: from mailgw1.maillennium.att.com (mailgw1.maillennium.att.com [135.25.114.99]) by klpd017.kcdc.att.com (8.14.4/8.14.4) with ESMTP id o8KKl2IR028307 for <apps-discuss@ietf.org>; Mon, 20 Sep 2010 15:47:02 -0500
Received: from [135.70.137.225] (vpn-135-70-137-225.vpn.mwst.att.com[135.70.137.225]) by maillennium.att.com (mailgw1) with ESMTP id <20100920204702gw100ei16te> (Authid: tony); Mon, 20 Sep 2010 20:47:02 +0000
X-Originating-IP: [135.70.137.225]
Message-ID: <4C97C844.5010809@att.com>
Date: Mon, 20 Sep 2010 16:47:00 -0400
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
To: apps-discuss@ietf.org
References: <4C933818.4000102@isode.com>	<AANLkTimkcNbb2nbOT=k33Pf5dviNRjZ1x0=7BWC2mo+h@mail.gmail.com> <4C93A875.1010002@stpeter.im>
In-Reply-To: <4C93A875.1010002@stpeter.im>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [apps-discuss] Apps Area WG (APPSAWG)
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Sep 2010 20:46:54 -0000

I'm probably stating the obvious, but the Appsarea meeting typically 
doesn't use the full 2.5 hour slot it's normally allocated, so the 
APPSAWG could easily join in the fun within the same time slot. I also 
think it's already the proper mix of people.

     Tony Hansen
     tony@att.com

On 9/17/2010 1:42 PM, Peter Saint-Andre wrote:
> On 9/17/10 11:32 AM, Barry Leiba wrote:
>
>    
>>> If this WG is going to be created, I would personally prefer to create it
>>> before Beijing. I don't expect that it will actually need a meeting in
>>> Beijing.
>>>        
>> On the contrary, I would expect it to meet at every IETF meeting,
>> *replacing* (or joining) the current apparea general session.  As time
>> goes on, we can see how much time the combined functions of this WG
>> and the apparea session need, and decide whether we should split
>> anything out.  But keeping that 2.5-hour monday morning session as the
>> only app-area plenary will help avoid the increased schedule conflicts
>> that some (including I) worry about.
>>      
> That seems like the right approach to me.
>
> Peter
>
>    

From sm@resistor.net  Mon Sep 20 16:33:40 2010
Return-Path: <sm@resistor.net>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 59FA13A67FC for <apps-discuss@core3.amsl.com>; Mon, 20 Sep 2010 16:33:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.659
X-Spam-Level: 
X-Spam-Status: No, score=-102.659 tagged_above=-999 required=5 tests=[AWL=-0.060, 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 REOE34LPi35j for <apps-discuss@core3.amsl.com>; Mon, 20 Sep 2010 16:33:37 -0700 (PDT)
Received: from ns1.qubic.net (ns1.qubic.net [208.69.177.116]) by core3.amsl.com (Postfix) with ESMTP id 70DCB3A67D1 for <Apps-Discuss@ietf.org>; Mon, 20 Sep 2010 16:33:37 -0700 (PDT)
Received: from SUBMAN.resistor.net ([10.0.0.1]) (authenticated bits=0) by ns1.qubic.net (8.14.5.Alpha0/8.14.5.Alpha0) with ESMTP id o8KNXTQf003938 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 20 Sep 2010 16:33:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1285025639; x=1285112039; bh=ZFEahJpakMhywPAEH1FZjDUEBLhE7SVhZFscPUcX7Dk=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=Jwc1Q7vEGVi62Fsz7PsIDNK+UTuqDKiPoEn6EOc5QTql8iXmL4z5FJOBNOenAF8kf vadARbPk0n+XxUSteFDpID8GtYKfOc1Qza7ztlxs63YrWUacTxpNxMLockiMmGo4HA 5XHDD87avdGT+JDYh5gKsnXYHhOsS2LP0T9l/2mI=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1285025639; x=1285112039; bh=ZFEahJpakMhywPAEH1FZjDUEBLhE7SVhZFscPUcX7Dk=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=q6BKh+C6HOkhh0XhSVezpLMANZG7RJoHq+Y6RKunR/EHovRXFTDDjateXHCeXDvGA dBxUNnusT4HchckIHj92pNORJSuAwwTmjTjFFNq9f21zaya6MpTMS0WUEJsO7fBiSV Cf7HEq4ZyBv/OfvGEFZm3TEk9b1F1sA0YGJGwXtg=
DomainKey-Signature: a=rsa-sha1; s=mail; d=resistor.net; c=simple; q=dns; b=v2VdkAjFlBuKnrBH7jq+PU/d/4tOOuOkSOYBWmf+mUaiMLVBnlpWNbWNjg3Qi87ks v9ejEO//B5fVmCldijEQDjZovyAnItXpLh8J2pV1U3DMSyWl5+GwFaVu3wbzNWB3fh1 eXHqvL121bnbjbbexIPzfQYQPd/07rTebAFbqQ0=
Message-Id: <6.2.5.6.2.20100920142444.0898c520@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 20 Sep 2010 16:33:02 -0700
To: Alexey Melnikov <alexey.melnikov@isode.com>
From: SM <sm@resistor.net>
In-Reply-To: <4C9791E6.1000701@isode.com>
References: <4C933818.4000102@isode.com> <AANLkTimkcNbb2nbOT=k33Pf5dviNRjZ1x0=7BWC2mo+h@mail.gmail.com> <4C93BEF3.7010105@isode.com> <6.2.5.6.2.20100919093131.08d2ae30@resistor.net> <4C9791E6.1000701@isode.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: Apps-Discuss@ietf.org
Subject: Re: [apps-discuss] Apps Area WG (APPSAWG)
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Sep 2010 23:33:40 -0000

Hi Alexey,
At 09:55 20-09-10, Alexey Melnikov wrote:
>Area Directors. If you think the distinction is important in the 
>Charter, I can change that.

It's more of a nit.  I am fine with either.

>Fine with me.
>
>Part of the reasons for the text is to allow ideas for new documents 
>to work on to be initiated from the WG, not just from ADs themselves.

It may seem far-fetched but it would be better to avoid situations 
where the consensus of the working group is at odds with best 
judgment of the Applications Area Directors.  There are two options:

  1. The Application Area Director determines whether the work should 
be submitted to the working group for consideration.

  2. The author of the draft asks the working group to consider 
taking on the work.

As this is to be a working group, the second option may be 
easier.  In practice, the  Applications Area Directors should be able 
to influence the outcome.  I am fine with the first option too.

Regards,
-sm 


From paul.hoffman@vpnc.org  Mon Sep 20 16:40:19 2010
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 41EBA3A67B6 for <apps-discuss@core3.amsl.com>; Mon, 20 Sep 2010 16:40:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.296
X-Spam-Level: 
X-Spam-Status: No, score=-101.296 tagged_above=-999 required=5 tests=[AWL=0.750, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, 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 47MU0c9uB8SM for <apps-discuss@core3.amsl.com>; Mon, 20 Sep 2010 16:40:17 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id C2E153A67D1 for <Apps-Discuss@ietf.org>; Mon, 20 Sep 2010 16:40:16 -0700 (PDT)
Received: from [10.20.30.158] (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o8KNecNP097621 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 20 Sep 2010 16:40:39 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p0624085fc8bda0ca7381@[10.20.30.158]>
In-Reply-To: <6.2.5.6.2.20100920142444.0898c520@resistor.net>
References: <4C933818.4000102@isode.com> <AANLkTimkcNbb2nbOT=k33Pf5dviNRjZ1x0=7BWC2mo+h@mail.gmail.com> <4C93BEF3.7010105@isode.com> <6.2.5.6.2.20100919093131.08d2ae30@resistor.net> <4C9791E6.1000701@isode.com> <6.2.5.6.2.20100920142444.0898c520@resistor.net>
Date: Mon, 20 Sep 2010 16:40:37 -0700
To: SM <sm@resistor.net>, Alexey Melnikov <alexey.melnikov@isode.com>
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
Cc: Apps-Discuss@ietf.org
Subject: Re: [apps-discuss] Apps Area WG (APPSAWG)
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Sep 2010 23:40:19 -0000

At 4:33 PM -0700 9/20/10, SM wrote:
>Hi Alexey,
>At 09:55 20-09-10, Alexey Melnikov wrote:
>>Area Directors. If you think the distinction is important in the Charter, I can change that.
>
>It's more of a nit.  I am fine with either.
>
>>Fine with me.
>>
>>Part of the reasons for the text is to allow ideas for new documents to work on to be initiated from the WG, not just from ADs themselves.
>
>It may seem far-fetched but it would be better to avoid situations where the consensus of the working group is at odds with best judgment of the Applications Area Directors.  There are two options:
>
> 1. The Application Area Director determines whether the work should be submitted to the working group for consideration.
>
> 2. The author of the draft asks the working group to consider taking on the work.
>
>As this is to be a working group, the second option may be easier.  In practice, the  Applications Area Directors should be able to influence the outcome.  I am fine with the first option too.

The ADs always have the final say (and often the initial say) in the work taken up by any WG, not just an area-wide WG. Different ADs act on this in different ways in different situations. It might be better not to instatiate this interaction in the WG charter, just as it is not included in (any?) other WG charters.

--Paul Hoffman, Director
--VPN Consortium

From fluffy@cisco.com  Tue Sep 21 12:16:27 2010
Return-Path: <fluffy@cisco.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1572528C0F6 for <apps-discuss@core3.amsl.com>; Tue, 21 Sep 2010 12:16:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.498
X-Spam-Level: 
X-Spam-Status: No, score=-110.498 tagged_above=-999 required=5 tests=[AWL=0.101, 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 4tlPO8Zh54Dd for <apps-discuss@core3.amsl.com>; Tue, 21 Sep 2010 12:16:25 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id 45AB528C0F5 for <Apps-Discuss@ietf.org>; Tue, 21 Sep 2010 12:16:25 -0700 (PDT)
Authentication-Results: sj-iport-5.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAMahmEyrR7Hu/2dsb2JhbACUNo10cagpnEOFQQSEToVqgn4
X-IronPort-AV: E=Sophos;i="4.56,401,1280707200"; d="scan'208";a="258558503"
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-5.cisco.com with ESMTP; 21 Sep 2010 19:16:09 +0000
Received: from [192.168.4.177] (rcdn-fluffy-8711.cisco.com [10.99.9.18]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id o8LJG9qo016905 for <Apps-Discuss@ietf.org>; Tue, 21 Sep 2010 19:16:09 GMT
From: Cullen Jennings <fluffy@cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Impp: xmpp:cullenfluffyjennings@jabber.org
Date: Tue, 21 Sep 2010 13:16:08 -0600
Message-Id: <D26D434D-93D6-4108-AA48-D8DA8286786C@cisco.com>
To: Apps-Discuss@ietf.org
Mime-Version: 1.0 (Apple Message framework v1081)
X-Mailer: Apple Mail (2.1081)
Subject: [apps-discuss] Draft on representing values of sensors in JSON (draft-jennings-senml)
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Sep 2010 19:16:27 -0000

I'd love to get some feedback on 

http://www.ietf.org/id/draft-jennings-senml-03.txt

Abstract

   This specification defines media types for representing simple sensor
   measurements in JSON.  A simple sensor, such as a temperature sensor,
   could use this media type in protocols such as HTTP to transport the
   values of a sensor.

From Martin.Thomson@andrew.com  Tue Sep 21 16:33:55 2010
Return-Path: <Martin.Thomson@andrew.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0CC2D3A67C2 for <apps-discuss@core3.amsl.com>; Tue, 21 Sep 2010 16:33:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.581
X-Spam-Level: 
X-Spam-Status: No, score=-2.581 tagged_above=-999 required=5 tests=[AWL=-0.582, BAYES_00=-2.599, J_CHICKENPOX_44=0.6]
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 tgbX7E-8kERZ for <apps-discuss@core3.amsl.com>; Tue, 21 Sep 2010 16:33:51 -0700 (PDT)
Received: from csmailgw1.commscope.com (csmailgw1.commscope.com [198.135.207.244]) by core3.amsl.com (Postfix) with ESMTP id BACC83A686B for <Apps-Discuss@ietf.org>; Tue, 21 Sep 2010 16:33:48 -0700 (PDT)
Received: from [10.86.20.103] ([10.86.20.103]:55221 "EHLO ACDCE7HC2.commscope.com") by csmailgw1.commscope.com with ESMTP id S33519058Ab0IUXeO (ORCPT <rfc822;Apps-Discuss@ietf.org>); Tue, 21 Sep 2010 18:34:14 -0500
Received: from SISPE7HC2.commscope.com (10.97.4.13) by ACDCE7HC2.commscope.com (10.86.20.103) with Microsoft SMTP Server (TLS) id 8.1.436.0; Tue, 21 Sep 2010 18:34:13 -0500
Received: from SISPE7MB1.commscope.com ([fe80::9d82:a492:85e3:a293]) by SISPE7HC2.commscope.com ([fe80::58c3:2447:f977:57c3%10]) with mapi; Wed, 22 Sep 2010 07:34:11 +0800
From: "Thomson, Martin" <Martin.Thomson@andrew.com>
To: Cullen Jennings <fluffy@cisco.com>, "Apps-Discuss@ietf.org" <Apps-Discuss@ietf.org>
Date: Wed, 22 Sep 2010 07:34:09 +0800
Thread-Topic: [apps-discuss] Draft on representing values of sensors in JSON (draft-jennings-senml)
Thread-Index: ActZwZJAlkXnGJ3cT2Swf6lEA0DpKwAHBEdQ
Message-ID: <8B0A9FCBB9832F43971E38010638454F03F1490AE0@SISPE7MB1.commscope.com>
References: <D26D434D-93D6-4108-AA48-D8DA8286786C@cisco.com>
In-Reply-To: <D26D434D-93D6-4108-AA48-D8DA8286786C@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="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-BCN: Meridius 1000 Version 3.4 on csmailgw1.commscope.com
X-BCN-Sender: Martin.Thomson@andrew.com
Subject: Re: [apps-discuss] Draft on representing values of sensors in JSON	(draft-jennings-senml)
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Sep 2010 23:33:55 -0000

PiBJJ2QgbG92ZSB0byBnZXQgc29tZSBmZWVkYmFjayBvbg0KPiANCj4gaHR0cDovL3d3dy5pZXRm
Lm9yZy9pZC9kcmFmdC1qZW5uaW5ncy1zZW5tbC0wMy50eHQNCg0KSGkgQ3VsbGVuLA0KDQpUaGUg
VW5pZmllZCBDb2RlIGZvciBVbml0cyBvZiBNZWFzdXJlIG1pZ2h0IGJlIG9mIGludGVyZXN0IHRv
IHlvdS4gIFRoaXMgaXMgYmFzZWQgb24gSVNPIDI1OTkgYW5kIEFOU0EgWDMuNTAuICBJdCBtaWdo
dCBzYXZlIHlvdSB0aGUgbmVlZCBmb3IgYSBuZXcgcmVnaXN0cnkuDQoNCiAgaHR0cDovL3VuaXRz
b2ZtZWFzdXJlLm9yZy8NCg0KSSBoYXZlIG15IG93biByZXNlcnZhdGlvbnMgYWJvdXQgdGhlIGdy
YW1tYXIgKHRvbyBtYW55IHNwZWNpYWwgY2FzZXMpLCBidXQgaXQgc2VlbXMgYSBzaGFtZSB0byB3
YXN0ZSBhbGwgdGhlIGdvb2QgZWZmb3J0Lg0KDQoNCllvdSBhbHNvIGhhdmUgYSBUT0RPIG9uIGFj
Y3VyYWN5L2NvbmZpZGVuY2UuICBBZGRpdGlvbmFsIG9wdGlvbmFsIGF0dHJpYnV0ZXMgc2VlbSBh
cHByb3ByaWF0ZTogaW4gbWV0cm9sb2d5LCBpdCdzIGNvbW1vbnBsYWNlIHRvIGRlc2NyaWJlIGEg
Y29uZmlkZW5jZSBpbnRlcnZhbC4NCg0KTWVhc3VyZW1lbnQgcXVhbGl0eSBhdHRyaWJ1dGVzIGNh
biBiZSBhZGRlZDoNCg0KICB1bmM6IHRoZSB1bmNlcnRhaW50eSBpbiB0aGUgbWVhc3VyZW1lbnQs
IHRoYXQgdXNlcyB0aGUgc2FtZSB1bml0cyBhcyB0aGUgYmFzZTsgaWYgYWJzZW50LCB0aGUgdmFs
dWUgaXMgdW5rbm93biAoaS5lLiwgZG9uJ3QgYXNzdW1lIHRoYXQgdGhpcyBpcyB6ZXJvKQ0KICBj
OiB0aGUgY29uZmlkZW5jZSBvZiB0aGUgbWVhc3VyZW1lbnQsIGFzIGEgcGVyY2VudGFnZTsgaWYg
YWJzZW50LCB5b3UgY2FuIHBpY2sgYSBkZWZhdWx0IHZhbHVlDQoNCkFuIGFsdGVybmF0aXZlIGlz
IHRvIHJlcG9ydCBSTVMgZXJyb3IsIHdoaWNoIGlzIGEgY29tbW9uIG1lYXN1cmUgb2YgcXVhbGl0
eSB3aGVyZSB0aGVyZSBhcmUgbXVsdGlwbGUgc2FtcGxlcyB0YWtlbiwgYnV0IG9ubHkgYSBtZWFu
IHZhbHVlIHJlcG9ydGVkOg0KDQogIHJtczogdGhlIFJNUyBlcnJvciBpbiB0aGUgbWVhc3VyZW1l
bnRzOyBpZiBhYnNlbnQ6IHVua25vd24NCiAgbnVtOiB0aGUgbnVtYmVyIG9mIHNhbXBsZXMgdGFr
ZW47IGlmIGFic2VudDogYXNzdW1lIGVpdGhlciBhIHZlcnkgbGFyZ2UgbnVtYmVyIHN1Y2ggdGhh
dCBSTVMgPX4gc3RhbmRhcmQgZGV2aWF0aW9uLCBvciBhc3N1bWUgb25lIChwaWNrIG9uZSkNCg0K
SW4gYSBsb3Qgb2Ygc2Vuc29ycywgdW5jZXJ0YWludHkgYW5kIGNvbmZpZGVuY2UgYXJlIGtub3du
LCBidXQgZGlzY3JldGUgb2JzZXJ2YXRpb25zIGRvIG5vdCBuZWNlc3NhcmlseSBjYXJyeSBzcGVj
aWZpYyB2YWx1ZXMgZm9yIHRoZXNlLiAgSW5zdGVhZCB0aGlzIGlzIGEga25vd24gY2hhcmFjdGVy
aXN0aWMgb2YgdGhlIGRldmljZS4gIFRodXMsIGl0IGNvdWxkIG1ha2Ugc2Vuc2UgdG8gY2Fycnkg
YSBiYXNlIHZhbHVlIChhIGJhc2UgdW5jZXJ0YWludHkpLiAgV2l0aGluIHRoZSBmb3JtYXQgeW91
IGRlc2NyaWJlLCB5b3Ugd2lsbCBuZWVkIHRvIGFzc29jaWF0ZSBhIGJhc2UgdmFsdWUgd2l0aCBl
YWNoIHNlbnNvci4NCg0KICB7IHE6IHsgWyBuOiAiZm9vIiwgdW5jOiAwLjQzLCBjOiA5MCBdIH0g
fQ0KDQoNCkkgZG9uJ3Qgc2VlIGFueSB2YWx1ZSBpbiBwcm92aWRpbmcgYSB2YWxpZCB0aW1lIGlu
dGVydmFsLiAgVGhpcyBpcyBnb2luZyB0byBlaXRoZXIgYmUgYmFzZWQgb24gcHJlZGljdGlvbnMg
dGhhdCB1c2UgbWVhc3VyZWQgdmFsdWVzLCBvciBpdCdzIGdvaW5nIHRvIGJlIHZpcnR1YWxseSBp
bXBvc3NpYmxlIHRvIHByZWRpY3QuICBBbnkgY2FzZSB3aGVyZSBhIG1lYXN1cmFuZCBpcyB0aW1l
LXZhcnlpbmcgaXMgZ29pbmcgdG8gYmUga25vd24gYnkgdGhlIHJlY2lwaWVudCBmb3IgdGhhdCBy
ZWNpcGllbnQgdG8gZG8gYW55dGhpbmcgcmVhc29uYWJsZSB3aXRoIHRoZSBkYXRhLg0KDQoNCklz
IHRoZSBpbnRlbnQgZm9yIHRoZSBzZW5zb3JzIHRvIGJlIGxhYmVsbGVkIHdpdGggYSBnbG9iYWxs
eSB1bmlxdWUgaWRlbnRpZmllcj8gIElmIHNvLCB3aHk/ICBJIHdvdWxkIGhhdmUgYXNzdW1lZCB0
aGF0IHRoZSBpZGVudGlmaWVkIHNvdXJjZSBvZiBkYXRhIHdvdWxkIHByb3ZpZGUgc29tZSBhbW91
bnQgb2YgZGlzYW1iaWd1YXRpb24uDQoNCg0KWW91IGhhdmUgYSBsb3Qgb2YgcXVlc3Rpb25zLiAg
SXMgaXQgcmVhbGx5IHRoYXQgbXVjaCBtb3JlIG9mIGEgYnVyZGVuIGZvciBhIGNvbnN0cmFpbmVk
IGRldmljZSB0byBwcm9kdWNlIGFuIFJGQyAzMzM5IGRhdGUrdGltZT8gIENlcnRhaW5seSwgdGhl
IHNpemUgaXNuJ3QgZ29pbmcgdG8gYmUgYSBzaWduaWZpY2FudCBidXJkZW4uICBNYXliZSB5b3Ug
Y291bGQgaGF2ZSAnYnQnIGluY2x1ZGUgdGhpcyB2YWx1ZSwgYW5kICd0JyBjYW4gYmUgbGVmdCBh
cyBhIGRlbHRhLiAgQ2VydGFpbmx5LCBJJ2QgbGlrZSB0byBzZWUgYSByZXNvbHV0aW9uIG9mIGJl
dHRlciB0aGFuIHNlY29uZHMuICBOYW5vc2Vjb25kIHJlc29sdXRpb24gd291bGQgYmUgaGFuZHkg
Zm9yIHNvbWV0aGluZyBsaWtlIGxvY2F0aW9uIDspDQoNCg0KKE5pdDogWW91ciBleGFtcGxlcyBo
YXZlIHRyYWlsaW5nIGNvbW1hcy4gIFRoZSBKU09OIHN5bnRheCBkb2Vzbid0IGFsbG93IHRoaXMu
KQ0KDQotLU1hcnRpbg0KDQpwLnMuLCBJIGxpa2UgdGhpczoNCg0KICAgLi4uIFRoZSBudW1iZXIg
b2Ygc2lnbmlmaWNhbnQgZGlnaXRzIGluIGFueQ0KICAgbWVhc3VyZW1lbnQgaXMgbm90IHJlbGV2
YW50LCBzbyBhIHJlYWRpbmcgb2YgMS4xIGhhcyBleGFjdGx5IHRoZSBzYW1lDQogICBzZW1hbnRp
YyBtZWFuaW5nIGFzIDEuMTAuICAuLi4NCg0K

From msk@cloudmark.com  Tue Sep 21 22:19:26 2010
Return-Path: <msk@cloudmark.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3E7003A6AE0; Tue, 21 Sep 2010 22:19:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.542
X-Spam-Level: 
X-Spam-Status: No, score=-103.542 tagged_above=-999 required=5 tests=[AWL=-0.943, 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 TGxfktaje272; Tue, 21 Sep 2010 22:18:43 -0700 (PDT)
Received: from ht2-outbound.cloudmark.com (ht2-outbound.cloudmark.com [72.5.239.36]) by core3.amsl.com (Postfix) with ESMTP id 85B943A6AD2; Tue, 21 Sep 2010 22:18:28 -0700 (PDT)
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by spite.corp.cloudmark.com ([172.22.10.72]) with mapi; Tue, 21 Sep 2010 22:18:37 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: "apps-discuss@ietf.org" <apps-discuss@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
Date: Tue, 21 Sep 2010 22:18:35 -0700
Thread-Topic: apps-review comments for draft-ietf-fecframe-framework-10
Thread-Index: ActaFZt/p/r1nFvjR1mgzFy0ViDOzg==
Message-ID: <BB012BD379D7B046ABE1472D8093C61C02AFC3C1F9@EXCH-C2.corp.cloudmark.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: "watsonm@netflix.com" <watsonm@netflix.com>
Subject: [apps-discuss] apps-review comments for draft-ietf-fecframe-framework-10
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Sep 2010 05:19:27 -0000

I have been selected as the Applications Area Review Team reviewer for this=
 draft (for background on apps-review, please see http://www.apps.ietf.org/=
content/applications-area-review-team).

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

Document: draft-ietf-fecframe-framework-10
Reviewer: Murray S. Kucherawy
Review Date: September 21, 2010
IETF Last Call Date: August 9-23, 2010
IESG Telechat Date: September 23, 2010

Summary: This draft is almost ready for publication as a Standards Track RF=
C.  I believe the technical material is sound, but it has a few substantive=
 document-level issues and numerous grammatical/editorial nits that should =
be reviewed before publication.

MAJOR ISSUES: None.

MINOR ISSUES:=20

General:
- Any discussion of existing interoperating implementations and issues foun=
d during that work, if any, might be useful to include in an appendix.

Section 2: Definitions/Abbreviations
- That "Application Data Unit" can be expressed as "ADU" should be stated e=
xplicitly, even though the connection is fairly obvious.
- "Application Protocol" references "RTSP" but that is not defined elsewher=
e in this section.  It should be at least expanded if not defined or even m=
ade an informative reference.  (Or if it's merely a typo, it should be corr=
ected.)

Section 3: Architecture Overview
- The paragraph starting "Depending on the FEC Scheme, ..." presents what a=
ppears to be an implementation variant.  For the sake of user guidance, the=
 author might consider including some language about why one might choose t=
o do (or be forced to do) what is described there.  If one of the other ref=
erence documents does discuss this, perhaps a section-specific reference to=
 that here would be appropriate.

Section 4.1: General
- The language about optionally constructing an FEC Scheme that jointly pro=
tects multiple Source Data Flows could use some guidance text as suggested =
above (i.e. what are the advantages and disadvantages of those choices).  I=
f adding such pedagogy here seems intrusive, it could be included in an app=
endix and simply referenced here.
- There is mixed use of "may" and "MAY", "must" and "MUST" in this section.=
  RFC2119 doesn't actually say it applies only to the uppercase form of tho=
se words.  Thus, the author might wish to substitute a word like "might" or=
 "could" for the lowercase ones.
- There is again some text about optional ways to implement or transmit Sou=
rce FEC Payload IDs, and some language about why one approach or the other =
is appropriate in certain circumstances might be helpful.

Section 5.3: Packet format for FEC Source Packets
- There is an acronym "ROHC" in the fifth paragraph.  It may come from Robu=
st Header Compression earlier in that paragraph; if so, that should be made=
 explicit.

Section 5.5: The normative reference to ABNF is probably not necessary here=
 because the ABNF is actually contained in the referenced document.  This m=
emo itself contains no ABNF.

Section 8: Congestion Control
- The format of this section, namely a large informative preamble to a smal=
l normative paragraph, seems awkward to me.  I suggest moving the informati=
ve note text into a new "Section 8.2: Discussion".

Section 10: IANA Considerations
- I can't tell if this section is creating a new registry with IANA or refe=
rring to an existing one.  I suggest making that more explicit.  More liber=
al application of RFC5226 is probably appropriate.  If this memo is creatin=
g a new registry, a registration template, perhaps even with an example, sh=
ould be provided.  See RFC4288 for an example of a blank template and regis=
try creation in detail.  RFC5965 creates a registry, provides a template, a=
nd then uses the template to declare the registry's initial contents, thus =
providing examples as well.  It looks like FEC Framework registrations coul=
d be quite large, so an abbreviated example is probably appropriate.
- Is 256 possible registrations plenty for the foreseeable future?  It seem=
s kind of small.
- If Section 5.6 defines the registration requirements, then perhaps those =
should be enumerated here instead and 5.6 can refer to this section.


NITS:

Numerous but all grammatical, and will be sent separately so as not to slow=
 the IESG Review process.


Cheers,
-MSK

From A.Hoenes@TR-Sys.de  Wed Sep 22 11:17:15 2010
Return-Path: <A.Hoenes@TR-Sys.de>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 64AB73A6B45 for <apps-discuss@core3.amsl.com>; Wed, 22 Sep 2010 11:17:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.828
X-Spam-Level: 
X-Spam-Status: No, score=-97.828 tagged_above=-999 required=5 tests=[AWL=0.921, BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, HELO_EQ_DE=0.35, MIME_8BIT_HEADER=0.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 WmwbGotKEdwP for <apps-discuss@core3.amsl.com>; Wed, 22 Sep 2010 11:17:05 -0700 (PDT)
Received: from TR-Sys.de (gateway.tr-sys.de [213.178.172.147]) by core3.amsl.com (Postfix) with ESMTP id CF7233A6ABC for <apps-discuss@ietf.org>; Wed, 22 Sep 2010 11:17:01 -0700 (PDT)
Received: from ZEUS.TR-Sys.de by w. with ESMTP ($Revision: 1.37.109.26 $/16.3.2) id AA206449196; Wed, 22 Sep 2010 20:13:16 +0200
Received: (from ah@localhost) by z.TR-Sys.de (8.9.3 (PHNE_25183)/8.7.3) id UAA26387; Wed, 22 Sep 2010 20:13:14 +0200 (MESZ)
From: Alfred =?hp-roman8?B?SM5uZXM=?= <ah@TR-Sys.de>
Message-Id: <201009221813.UAA26387@TR-Sys.de>
To: patrik@frobbit.se
Date: Wed, 22 Sep 2010 20:13:14 +0200 (MESZ)
X-Mailer: ELM [$Revision: 1.17.214.3 $]
Mime-Version: 1.0
Content-Type: text/plain; charset=hp-roman8
Content-Transfer-Encoding: quoted-printable
Cc: dnsext-chairs@tools.ietf.org, dnsop-chairs@tools.ietf.org, apps-discuss@ietf.org
Subject: Re: [apps-discuss] Review of liaison from ITU-T regarding OIDs -- ...
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Sep 2010 18:17:15 -0000

Patrick,
slowly working down now my long backlog of matters to be reviewed
and discussed, I eventually arrived at studying the ITU-T document
(draft ITU-T X.672) referenced in the liaison #903 that you hat
brought to the attention of the apps-discuss list [*] shortly before
IETF in Maastricht.

[*]
 http://www.IETF.ORG/mail-archive/web/apps-discuss/current/msg01613.html

Please feel free to forward the information below (after verification)
via the proper liaison contact.


(1)  major issue

I found one basic misconception of DNS behavior in that document:

Clause 5.2.4 says:

     [...]  sends a query request to a DNS client for NAPTR resource
   records containing the requested ORS information type, ...


This (unfortunately) is a common misconception of DNS behavior, as
also pointed out in the IAB's "Design Choices When Expanding the DNS"
(RFC 5507): a DNS query cannot select by "indirect" keys embedded in
RRs; the DNS client (resolver) can only be commanded to retrieve (and
DNSSEC-verify) an entire RRset.  The responsibility for selecting the
NAPTR RRs containing the application tags in which the ORS client is
interested is entirely with the ORS client itself.  =


NOTE:
  Verification of the DNSSEC signature requires the full NAPTR RRset
  at the indicated DNS node -- including all possible application tags.

If the ITU-T / ISO folks want to promote modular use of common/standard
resolver libraries, they should not place unusual additional functional
requirements on these, but instead specify (in clause 5.2.6) that the
ORS has to perform the selection of the NAPTR RRs matching the =

requested ORS information type (via the service field in the returned
NAPTR RDATA).


Fortunately, clause 7 of the ITU-T draft contains a proper description
of the details, but clause 5.2.* should be aligned with the actual =

DNS behavior and clause 7.


(2) minor issues

Another, less technical issue is the definition of DNS zones and
RRsets in the ITU-T draft, which is strongly based on the concept
of a zone *files*.  Doing that in DNSEXT these days would certainly
be regarded as too BIND-centric and hence be very controversial!
In many places in the ITU-T draft, simply replacing "zone file[s]"
by "zone[s]" would be a substantial improvement.

Yet another detail I stumbled over:  In clause 6.1.3, the last two
sentences essentially state that there cannot be empty non-terminal
nodes (in the DNS subtree under consideration).
The text does not make clear that this is an additional requirement
imposed by that specification, not a DNS-internal requirement.
IMO, it would be wise to clarify that.

An ITU-T specific issue seems to be in clause 6.4.2.
I strongly suspect that the error return on finding an unsigned
NAPTR *RRset* (not RR -- a single RR cannot be signed via DNSSEC)
should only be requested if the ORS application had set the security
flag upon its call to the ORS client.  This qualification is missing
in the draft.

Finally, it should be pointed out that RFC 3490 in the meantime has
been superseded by the IDNA-2008 document set, RFCs 5890 thru 5893,
and RFC 5894, giving an overview of that specification and rationale.

I do not understand why the ITU-T draft mandates the use of NSEC3
(invented to prohibit zone enumeration) and at the same time
provides an XML-based service ("CINF") for the enumeration of
delegations (by means of EXTENDED-XER-encoded ASN.1 modules).
(Note that the <noDisclosure/> element is only related to the
ChildInformation CHOICE, not the existence of the child.)
IMO, the (operationally much simpler) use of NSEC would be appropriate
-- at least for those zones that correspond to OID branches that
support the CINF service.


Kind regards,
  Alfred H=CEnes.

-- =


+------------------------+--------------------------------------------+
| TR-Sys Alfred Hoenes   |  Alfred Hoenes   Dipl.-Math., Dipl.-Phys.  |
| Gerlinger Strasse 12   |  Phone: (+49)7156/9635-0, Fax: -18         |
| D-71254  Ditzingen     |  E-Mail:  ah@TR-Sys.de                     |
+------------------------+--------------------------------------------+


From patrik@frobbit.se  Wed Sep 22 11:19:44 2010
Return-Path: <patrik@frobbit.se>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B207A3A6A30 for <apps-discuss@core3.amsl.com>; Wed, 22 Sep 2010 11:19:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level: 
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1VuOG5DUET8k for <apps-discuss@core3.amsl.com>; Wed, 22 Sep 2010 11:19:43 -0700 (PDT)
Received: from srv01.frobbit.se (srv01.frobbit.se [IPv6:2a02:80:3ffe::39]) by core3.amsl.com (Postfix) with ESMTP id DDC263A6A58 for <apps-discuss@ietf.org>; Wed, 22 Sep 2010 11:19:42 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by srv01.frobbit.se (Postfix) with ESMTP id 833BFDEB3685; Wed, 22 Sep 2010 20:20:09 +0200 (CEST)
X-Virus-Scanned: amavisd-new at frobbit.se
Received: from srv01.frobbit.se ([127.0.0.1]) by localhost (srv01.frobbit.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ie8wi34a+SYf; Wed, 22 Sep 2010 20:20:09 +0200 (CEST)
Received: from [IPv6:2a02:80:3ffc::dead:beef] (unknown [IPv6:2a02:80:3ffc::dead:beef]) (Authenticated sender: paf01) by srv01.frobbit.se (Postfix) with ESMTP id D281FDEB3682; Wed, 22 Sep 2010 20:20:08 +0200 (CEST)
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <patrik@frobbit.se>
In-Reply-To: <201009221813.UAA26387@TR-Sys.de>
Date: Wed, 22 Sep 2010 20:20:08 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <5C3DCF0F-975D-4CC9-A58C-5815945BFD2C@frobbit.se>
References: <201009221813.UAA26387@TR-Sys.de>
To: =?iso-8859-1?Q?Alfred_H=CEnes?= <ah@TR-Sys.de>
X-Mailer: Apple Mail (2.1081)
Cc: dnsext-chairs@tools.ietf.org, dnsop-chairs@tools.ietf.org, apps-discuss@ietf.org
Subject: Re: [apps-discuss] Review of liaison from ITU-T regarding OIDs -- ...
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Sep 2010 18:19:44 -0000

Thanks!

   paf

On 22 sep 2010, at 20.13, Alfred H=CEnes wrote:

> Patrick,
> slowly working down now my long backlog of matters to be reviewed
> and discussed, I eventually arrived at studying the ITU-T document
> (draft ITU-T X.672) referenced in the liaison #903 that you hat
> brought to the attention of the apps-discuss list [*] shortly before
> IETF in Maastricht.
>=20
> [*]
> =
http://www.IETF.ORG/mail-archive/web/apps-discuss/current/msg01613.html
>=20
> Please feel free to forward the information below (after verification)
> via the proper liaison contact.
>=20
>=20
> (1)  major issue
>=20
> I found one basic misconception of DNS behavior in that document:
>=20
> Clause 5.2.4 says:
>=20
>     [...]  sends a query request to a DNS client for NAPTR resource
>   records containing the requested ORS information type, ...
>=20
>=20
> This (unfortunately) is a common misconception of DNS behavior, as
> also pointed out in the IAB's "Design Choices When Expanding the DNS"
> (RFC 5507): a DNS query cannot select by "indirect" keys embedded in
> RRs; the DNS client (resolver) can only be commanded to retrieve (and
> DNSSEC-verify) an entire RRset.  The responsibility for selecting the
> NAPTR RRs containing the application tags in which the ORS client is
> interested is entirely with the ORS client itself. =20
>=20
> NOTE:
>  Verification of the DNSSEC signature requires the full NAPTR RRset
>  at the indicated DNS node -- including all possible application tags.
>=20
> If the ITU-T / ISO folks want to promote modular use of =
common/standard
> resolver libraries, they should not place unusual additional =
functional
> requirements on these, but instead specify (in clause 5.2.6) that the
> ORS has to perform the selection of the NAPTR RRs matching the=20
> requested ORS information type (via the service field in the returned
> NAPTR RDATA).
>=20
>=20
> Fortunately, clause 7 of the ITU-T draft contains a proper description
> of the details, but clause 5.2.* should be aligned with the actual=20
> DNS behavior and clause 7.
>=20
>=20
> (2) minor issues
>=20
> Another, less technical issue is the definition of DNS zones and
> RRsets in the ITU-T draft, which is strongly based on the concept
> of a zone *files*.  Doing that in DNSEXT these days would certainly
> be regarded as too BIND-centric and hence be very controversial!
> In many places in the ITU-T draft, simply replacing "zone file[s]"
> by "zone[s]" would be a substantial improvement.
>=20
> Yet another detail I stumbled over:  In clause 6.1.3, the last two
> sentences essentially state that there cannot be empty non-terminal
> nodes (in the DNS subtree under consideration).
> The text does not make clear that this is an additional requirement
> imposed by that specification, not a DNS-internal requirement.
> IMO, it would be wise to clarify that.
>=20
> An ITU-T specific issue seems to be in clause 6.4.2.
> I strongly suspect that the error return on finding an unsigned
> NAPTR *RRset* (not RR -- a single RR cannot be signed via DNSSEC)
> should only be requested if the ORS application had set the security
> flag upon its call to the ORS client.  This qualification is missing
> in the draft.
>=20
> Finally, it should be pointed out that RFC 3490 in the meantime has
> been superseded by the IDNA-2008 document set, RFCs 5890 thru 5893,
> and RFC 5894, giving an overview of that specification and rationale.
>=20
> I do not understand why the ITU-T draft mandates the use of NSEC3
> (invented to prohibit zone enumeration) and at the same time
> provides an XML-based service ("CINF") for the enumeration of
> delegations (by means of EXTENDED-XER-encoded ASN.1 modules).
> (Note that the <noDisclosure/> element is only related to the
> ChildInformation CHOICE, not the existence of the child.)
> IMO, the (operationally much simpler) use of NSEC would be appropriate
> -- at least for those zones that correspond to OID branches that
> support the CINF service.
>=20
>=20
> Kind regards,
>  Alfred H=CEnes.
>=20
> --=20
>=20
> =
+------------------------+--------------------------------------------+
> | TR-Sys Alfred Hoenes   |  Alfred Hoenes   Dipl.-Math., Dipl.-Phys.  =
|
> | Gerlinger Strasse 12   |  Phone: (+49)7156/9635-0, Fax: -18         =
|
> | D-71254  Ditzingen     |  E-Mail:  ah@TR-Sys.de                     =
|
> =
+------------------------+--------------------------------------------+
>=20
>=20


From msk@cloudmark.com  Wed Sep 22 14:24:37 2010
Return-Path: <msk@cloudmark.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AF37A3A6B45 for <apps-discuss@core3.amsl.com>; Wed, 22 Sep 2010 14:24:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.549
X-Spam-Level: 
X-Spam-Status: No, score=-103.549 tagged_above=-999 required=5 tests=[AWL=-0.950, 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 CeqW6uJkGRwb for <apps-discuss@core3.amsl.com>; Wed, 22 Sep 2010 14:24:35 -0700 (PDT)
Received: from ht1-outbound.cloudmark.com (ht1-outbound.cloudmark.com [72.5.239.35]) by core3.amsl.com (Postfix) with ESMTP id EFCEC3A67F8 for <apps-discuss@ietf.org>; Wed, 22 Sep 2010 14:24:34 -0700 (PDT)
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by malice.corp.cloudmark.com ([172.22.10.71]) with mapi; Wed, 22 Sep 2010 14:25:02 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Date: Wed, 22 Sep 2010 14:25:02 -0700
Thread-Topic: multipart/report
Thread-Index: ActaGml/QkywnISrTzSHowTvwZP6WQAgiANQ
Message-ID: <BB012BD379D7B046ABE1472D8093C61C02AFC3C25A@EXCH-C2.corp.cloudmark.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [apps-discuss] multipart/report
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Sep 2010 21:24:37 -0000

Re-sending to a wider audience...

From: Murray S. Kucherawy=20
Sent: Tuesday, September 21, 2010 10:53 PM
To: ietf-822@imc.org
Subject: multipart/report

I'm doing some work with the OMA in the area of spam reporting.=A0 They hav=
e developed an XML message format for reporting spam from a mobile handset.=
=A0 Because SMS and MMS (and even IM) have different structure than email, =
they went with something more extensible than what we currently do with DSN=
s.=A0 I'm helping that group try to converge with what we do in the email w=
orld, especially with what the MARF working group is producing (e.g., ARF, =
specified by recently-published RFC5965).=A0 The first thing is to register=
 the MIME type they've created, and so I've crafted a template for that.

The next thing we'd like to achieve is to be able to specify multiple spam =
reports in a single message, regardless of transport (they currently use HT=
TP POST, but there's no reason SMTP couldn't be used).=A0 The most obvious =
thing to do would be to use a multipart/mixed MIME message, and then includ=
e their MIME type in each of "n" parts.=A0 However, this is different than =
what was done with ARF, which used multipart/report.=A0 The advantage to us=
ing multipart/report, which stipulates that it must be the outermost MIME t=
ype, is that you know right away that you're processing a report rather tha=
n having to parse part way into the MIME tree to figure that out.=A0 (Accor=
ding to Tony Hansen, that's why this rule was put in place.)=A0 But althoug=
h multipart/report is the most obvious construct for doing this, it doesn't=
 lend itself to multi-report messages.=A0 So to get these to converge, we h=
ave to be a little creative or be very creative (in the "create a lot of do=
cuments" sense).

We could do a message/digest, each sub-part of which is message/rfc822 and =
the MIME type within that is multipart/report.=A0 One could argue that this=
 approach conforms to the multipart/report rules by having that be the oute=
rmost MIME part of each constituent message in the aggregate message, but t=
hat might be hard to defend given the spirit of that rule.

There's also a stipulation that the MIME subtype of the second part in a mu=
ltipart/report message must be equal to the report-type of the outermost pa=
rt, with no other constraints.=A0 Thus to keep multipart/report at the oute=
rmost MIME but allow multi-message reports, we could comply by using "multi=
part/report; report-type=3Dmixed" as the outermost MIME type and then use "=
multipart/mixed" inside.=A0 But this also sure feels hack-ish.

So what would be more palatable to this community?=A0 Could multipart/repor=
t be updated to accommodate this use case?=A0 Should we register multipart/=
multi-report that relaxes some of the existing restrictions without changin=
g the existing media type?

Feedback/guidance is welcome.

-MSK

From mnot@mnot.net  Wed Sep 22 21:25:23 2010
Return-Path: <mnot@mnot.net>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 19EC13A6A9A for <apps-discuss@core3.amsl.com>; Wed, 22 Sep 2010 21:25:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.69
X-Spam-Level: 
X-Spam-Status: No, score=-104.69 tagged_above=-999 required=5 tests=[AWL=-2.991, BAYES_00=-2.599, GB_I_LETTER=-2, J_CHICKENPOX_44=0.6, MANGLED_MEDS=2.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 PTXwyFLQxRE5 for <apps-discuss@core3.amsl.com>; Wed, 22 Sep 2010 21:25:19 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by core3.amsl.com (Postfix) with ESMTP id 7C77C3A69C5 for <discuss@apps.ietf.org>; Wed, 22 Sep 2010 21:25:17 -0700 (PDT)
Received: from chancetrain-lm.mnot.net (unknown [118.209.171.160]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 2ADE322E1F4; Thu, 23 Sep 2010 00:25:38 -0400 (EDT)
From: Mark Nottingham <mnot@mnot.net>
Content-Type: multipart/mixed; boundary=Apple-Mail-17--181425568
Date: Thu, 23 Sep 2010 14:25:35 +1000
Message-Id: <D92B699E-32AA-4CD8-94B8-469296A4D48B@mnot.net>
To: HTTP Working Group <ietf-http-wg@w3.org>, Apps Discuss <discuss@apps.ietf.org>, Atom-Syntax Syntax <atom-syntax@imc.org>
Mime-Version: 1.0 (Apple Message framework v1081)
X-Mailer: Apple Mail (2.1081)
Subject: [apps-discuss] IANA hanges to draft-nottingham-http-link-header
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Sep 2010 04:25:23 -0000

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

Draft-nottingham-http-link-header =
<https://datatracker.ietf.org/doc/draft-nottingham-http-link-header/> =
has been the AUTH48 state for a few weeks, pending resolution of some =
issues with IANA.

It turns out that the text specifying interactions between the =
Designated Experts and IANA was too constraining; furthermore, the =
specification of a one-off registry XML format doesn't work well with =
IANA's toolchain for managing registries.

As a result, I'm proposing removal of some text, as part of the AUTH48 =
process. Alexey (the responsible AD) has asked me to communicate this to =
the various stakeholder communities for feedback.

I've attached the proposed RFC, with a diff available at =
<http://www.mnot.net/test/link-diff.html>. Note that the diff also =
incorporates editorial changes from the RFC Editor.=20

The changes under discussion here are:

1) Removal of the following paragraph from section 6.2.1, "Registering =
Link Relation Types":

   When a registration request is successful, the Designated Expert(s)	 =
	=09
   will update the registry XML file (using the format described in	 =
	=09
   Appendix A including the MIT license) and send it to the [TBD-2]@	 =
	=09
   ietf.org mailing list (which SHOULD NOT be centrally archived, so as	 =
	=09
   to avoid load issues from automated agents, and only accept posts	 =
	=09
   from the Designated Expert(s)), so that implementers interested in	 =
	=09
   receiving a machine-readable registry can do so.  Simultaneously,	 =
	=09
   they will send a text (not XML) version of the registry to IANA for	 =
	=09
   publication.	 	=09

2) Removal of Appendix A in its entirety.=20

Instead, the Designated Experts will inform IANA of new entries, and =
they will be produced and published as normal on the IANA Web site. =
I.e., they will be available in text, HTML and XML -- the latter using =
the same format as other registries (for an example, see =
<http://www.iana.org/assignments/aaa-parameters/aaa-parameters.xml>).=20

3) Adding the following to the beginning of section 6.2, "Link Relation =
Type Registry":

   The underlying registry data (e.g., the XML file) must include
   Simplified BSD License text as described in Section 4.e of the Trust
   Legal Provisions (<http://trustee.ietf.org/license-info>).

One open question is the issue of whether an announcement list is still =
necessary, since the registry data will be available from the Web site. =
However, this does not necessarily need to be specified in the RFC =
itself; the registry page can advertise the list if people would like =
one.

Feedback appreciated; Alexey will be able to use that as input to the =
next steps.

Regards,


--Apple-Mail-17--181425568
Content-Disposition: attachment;
	filename=rfc5988.txt
Content-Type: text/plain;
	name="rfc5988.txt"
Content-Transfer-Encoding: quoted-printable




Network Working Group                                      M. Nottingham
Request for Comments: 5988                                   August 2010
Updates: 4287
Category: Standards Track


                              Web Linking

Abstract

   This document specifies relation types for Web links, and defines a
   registry for them.  It also defines the use of such links in HTTP
   headers with the Link header field.

Status of This Memo

   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) for the standardization state
   and status of this protocol.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (c) 2010 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
   described in the Simplified BSD License.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 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, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.



Nottingham                   Standards Track                    [Page 1]
=0C
RFC 5988                       Web Linking                   August 2010


Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Notational Conventions . . . . . . . . . . . . . . . . . . . .  3
   3.  Links  . . . . . . . . . . . . . . . . . . . . . . . . . . . .  4
   4.  Link Relation Types  . . . . . . . . . . . . . . . . . . . . .  4
     4.1.  Registered Relation Types  . . . . . . . . . . . . . . . .  5
     4.2.  Extension Relation Types . . . . . . . . . . . . . . . . .  6
   5.  The Link Header Field  . . . . . . . . . . . . . . . . . . . .  6
     5.1.  Target IRI . . . . . . . . . . . . . . . . . . . . . . . .  7
     5.2.  Context IRI  . . . . . . . . . . . . . . . . . . . . . . .  7
     5.3.  Relation Type  . . . . . . . . . . . . . . . . . . . . . .  8
     5.4.  Target Attributes  . . . . . . . . . . . . . . . . . . . .  8
     5.5.  Examples . . . . . . . . . . . . . . . . . . . . . . . . .  9
   6.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 10
     6.1.  Link HTTP Header Registration  . . . . . . . . . . . . . . 10
     6.2.  Link Relation Type Registry  . . . . . . . . . . . . . . . 10
       6.2.1.  Registering New Link Relation Types  . . . . . . . . . 11
       6.2.2.  Initial Registry Contents  . . . . . . . . . . . . . . 12
     6.3.  Link Relation Application Data Registry  . . . . . . . . . 16
   7.  Security Considerations  . . . . . . . . . . . . . . . . . . . 17
   8.  Internationalisation Considerations  . . . . . . . . . . . . . 18
   9.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 19
     9.1.  Normative References . . . . . . . . . . . . . . . . . . . 19
     9.2.  Informative References . . . . . . . . . . . . . . . . . . 19
   Appendix A.  Notes on Using the Link Header with the HTML4
                Format  . . . . . . . . . . . . . . . . . . . . . . . 21
   Appendix B.  Notes on Using the Link Header with the Atom
                Format  . . . . . . . . . . . . . . . . . . . . . . . 22
   Appendix C.  Acknowledgements  . . . . . . . . . . . . . . . . . . 23





















Nottingham                   Standards Track                    [Page 2]
=0C
RFC 5988                       Web Linking                   August 2010


1.  Introduction

   A means of indicating the relationships between resources on the Web,
   as well as indicating the type of those relationships, has been
   available for some time in HTML [W3C.REC-html401-19991224], and more
   recently in Atom [RFC4287].  These mechanisms, although conceptually
   similar, are separately specified.  However, links between resources
   need not be format specific; it can be useful to have typed links
   that are independent of their serialisation, especially when a
   resource has representations in multiple formats.

   To this end, this document defines a framework for typed links that
   isn't specific to a particular serialisation or application.  It does
   so by redefining the link relation registry established by Atom to
   have a broader domain, and adding to it the relations that are
   defined by HTML.

   Furthermore, an HTTP header field for conveying typed links was
   defined in Section 19.6.2.4 of [RFC2068], but removed from [RFC2616],
   due to a lack of implementation experience.  Since then, it has been
   implemented in some User Agents (e.g., for stylesheets), and several
   additional use cases have surfaced.

   Because it was removed, the status of the Link header is unclear,
   leading some to consider minting new application-specific HTTP
   headers instead of reusing it.  This document addresses this by re-
   specifying the Link header as one such serialisation, with updated
   but backwards-compatible syntax.

2.  Notational Conventions

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in BCP 14, [RFC2119], as
   scoped to those conformance targets.

   This document uses the Augmented Backus-Naur Form (ABNF) notation of
   [RFC2616], and explicitly includes the following rules from it:
   quoted-string, token, SP (space), LOALPHA, DIGIT.

   Additionally, the following rules are included from [RFC3986]: URI
   and URI-Reference; from [RFC4288]: type-name and subtype-name; from
   [W3C.REC-html401-19991224]: MediaDesc; from [RFC5646]: Language-Tag;
   and from [RFC5987], ext-value and parmname.







Nottingham                   Standards Track                    [Page 3]
=0C
RFC 5988                       Web Linking                   August 2010


3.  Links

   In this specification, a link is a typed connection between two
   resources that are identified by Internationalised Resource
   Identifiers (IRIs) [RFC3987], and is comprised of:

   o  A context IRI,

   o  a link relation type (Section 4),

   o  a target IRI, and

   o  optionally, target attributes.

   A link can be viewed as a statement of the form "{context IRI} has a
   {relation type} resource at {target IRI}, which has {target
   attributes}".

   Note that in the common case, the context IRI will also be a URI
   [RFC3986], because many protocols (such as HTTP) do not support
   dereferencing IRIs.  Likewise, the target IRI will be converted to a
   URI (see [RFC3987], Section 3.1) in serialisations that do not
   support IRIs (e.g., the Link header).

   This specification does not place restrictions on the cardinality of
   links; there can be multiple links to and from a particular IRI, and
   multiple links of different types between two given IRIs.  Likewise,
   the relative ordering of links in any particular serialisation, or
   between serialisations (e.g., the Link header and in-content links)
   is not specified or significant in this specification; applications
   that wish to consider ordering significant can do so.

   Target attributes are a set of key/value pairs that describe the link
   or its target; for example, a media type hint.  This specification
   does not attempt to coordinate their names or use, but does provide
   common target attributes for use in the Link HTTP header.

   Finally, this specification does not define a general syntax for
   expressing links, nor does it mandate a specific context for any
   given link; it is expected that serialisations of links will specify
   both aspects.  One such serialisation is communication of links
   through HTTP headers, specified in Section 5.

4.  Link Relation Types

   In the simplest case, a link relation type identifies the semantics
   of a link.  For example, a link with the relation type "copyright"
   indicates that the resource identified by the target IRI is a



Nottingham                   Standards Track                    [Page 4]
=0C
RFC 5988                       Web Linking                   August 2010


   statement of the copyright terms applying to the current context IRI.

   Link relation types can also be used to indicate that the target
   resource has particular attributes, or exhibits particular
   behaviours; for example, a "service" link implies that the identified
   resource is part of a defined protocol (in this case, a service
   description).

   Relation types are not to be confused with media types [RFC4288];
   they do not identify the format of the representation that results
   when the link is dereferenced.  Rather, they only describe how the
   current context is related to another resource.

   Relation types SHOULD NOT infer any additional semantics based upon
   the presence or absence of another link relation type, or its own
   cardinality of occurrence.  An exception to this is the combination
   of the "alternate" and "stylesheet" registered relation types, which
   has special meaning in HTML4 for historical reasons.

   There are two kinds of relation types: registered and extension.

4.1.  Registered Relation Types

   Well-defined relation types can be registered as tokens for
   convenience and/or to promote reuse by other applications.  This
   specification establishes an IANA registry of such relation types;
   see Section 6.2.

   Registered relation type names MUST conform to the reg-rel-type rule,
   and MUST be compared character-by-character in a case-insensitive
   fashion.  They SHOULD be appropriate to the specificity of the
   relation type; i.e., if the semantics are highly specific to a
   particular application, the name should reflect that, so that more
   general names are available for less specific use.

   Registered relation types MUST NOT constrain the media type of the
   context IRI, and MUST NOT constrain the available representation
   media types of the target IRI.  However, they can specify the
   behaviours and properties of the target resource (e.g., allowable
   HTTP methods, request and response media types that must be
   supported).

   Additionally, specific applications of linking may require additional
   data to be included in the registry.  For example, Web browsers might
   want to know what kinds of links should be downloaded when they
   archive a Web page; if this application-specific information is in
   the registry, new link relation types can control this behaviour
   without unnecessary coordination.



Nottingham                   Standards Track                    [Page 5]
=0C
RFC 5988                       Web Linking                   August 2010


   To accommodate this, per-entry application data can be added to the
   Link Relation Type registry, by registering it in the Link Relation
   Application Data registry (Section 6.3).

4.2.  Extension Relation Types

   Applications that don't wish to register a relation type can use an
   extension relation type, which is a URI [RFC3986] that uniquely
   identifies the relation type.  Although the URI can point to a
   resource that contains a definition of the semantics of the relation
   type, clients SHOULD NOT automatically access that resource to avoid
   overburdening its server.

   When extension relation types are compared, they MUST be compared as
   strings (after converting to URIs if serialised in a different
   format, such as a Curie [W3C.CR-curie-20090116]) in a case-
   insensitive fashion, character-by-character.  Because of this, all-
   lowercase URIs SHOULD be used for extension relations.

   Note that while extension relation types are required to be URIs, a
   serialisation of links can specify that they are expressed in another
   form, as long as they can be converted to URIs.

5.  The Link Header Field

   The Link entity-header field provides a means for serialising one or
   more links in HTTP headers.  It is semantically equivalent to the
   <LINK> element in HTML, as well as the atom:link feed-level element
   in Atom [RFC4287].






















Nottingham                   Standards Track                    [Page 6]
=0C
RFC 5988                       Web Linking                   August 2010


  Link           =3D "Link" ":" #link-value
  link-value     =3D "<" URI-Reference ">" *( ";" link-param )
  link-param     =3D ( ( "rel" "=3D" relation-types )
                 | ( "anchor" "=3D" <"> URI-Reference <"> )
                 | ( "rev" "=3D" relation-types )
                 | ( "hreflang" "=3D" Language-Tag )
                 | ( "media" "=3D" ( MediaDesc | ( <"> MediaDesc <"> ) ) =
)
                 | ( "title" "=3D" quoted-string )
                 | ( "title*" "=3D" ext-value )
                 | ( "type" "=3D" ( media-type | quoted-mt ) )
                 | ( link-extension ) )
  link-extension =3D ( parmname [ "=3D" ( ptoken | quoted-string ) ] )
                 | ( ext-name-star "=3D" ext-value )
  ext-name-star  =3D parmname "*" ; reserved for RFC2231-profiled
                                ; extensions. Whitespace NOT
                                ; allowed in between.
  ptoken         =3D 1*ptokenchar
  ptokenchar     =3D "!" | "#" | "$" | "%" | "&" | "'" | "("
                 | ")" | "*" | "+" | "-" | "." | "/" | DIGIT
                 | ":" | "<" | "=3D" | ">" | "?" | "@" | ALPHA
                 | "[" | "]" | "^" | "_" | "`" | "{" | "|"
                 | "}" | "~"
  media-type     =3D type-name "/" subtype-name
  quoted-mt      =3D <"> media-type <">
  relation-types =3D relation-type
                 | <"> relation-type *( 1*SP relation-type ) <">
  relation-type  =3D reg-rel-type | ext-rel-type
  reg-rel-type   =3D LOALPHA *( LOALPHA | DIGIT | "." | "-" )
  ext-rel-type   =3D URI

5.1.  Target IRI

   Each link-value conveys one target IRI as a URI-Reference (after
   conversion to one, if necessary; see [RFC3987], Section 3.1) inside
   angle brackets ("<>").  If the URI-Reference is relative, parsers
   MUST resolve it as per [RFC3986], Section 5.  Note that any base IRI
   from the message's content is not applied.

5.2.  Context IRI

   By default, the context of a link conveyed in the Link header field
   is the IRI of the requested resource.

   When present, the anchor parameter overrides this with another URI,
   such as a fragment of this resource, or a third resource (i.e., when
   the anchor value is an absolute URI).  If the anchor parameter's
   value is a relative URI, parsers MUST resolve it as per [RFC3986],
   Section 5.  Note that any base URI from the body's content is not



Nottingham                   Standards Track                    [Page 7]
=0C
RFC 5988                       Web Linking                   August 2010


   applied.

   Consuming implementations can choose to ignore links with an anchor
   parameter.  For example, the application in use may not allow the
   context IRI to be assigned to a different resource.  In such cases,
   the entire link is to be ignored; consuming implementations MUST NOT
   process the link without applying the anchor.

   Note that depending on HTTP status code and response headers, the
   context IRI might be "anonymous" (i.e., no context IRI is available).
   For instance, this is the case on a 404 response to a GET request.

5.3.  Relation Type

   The relation type of a link is conveyed in the "rel" parameter's
   value.  The "rel" parameter MUST NOT appear more than once in a given
   link-value; occurrences after the first MUST be ignored by parsers.

   The "rev" parameter has been used in the past to indicate that the
   semantics of the relationship are in the reverse direction.  That is,
   a link from A to B with REL=3D"X" expresses the same relationship as =
a
   link from B to A with REV=3D"X". "rev" is deprecated by this
   specification because it often confuses authors and readers; in most
   cases, using a separate relation type is preferable.

   Note that extension relation types are REQUIRED to be absolute URIs
   in Link headers, and MUST be quoted if they contain a semicolon (";")
   or comma (",") (as these characters are used as delimiters in the
   header itself).

5.4.  Target Attributes

   The "hreflang", "media", "title", "title*", "type", and any link-
   extension link-params are considered to be target attributes for the
   link.

   The "hreflang" parameter, when present, is a hint indicating what the
   language of the result of dereferencing the link should be.  Note
   that this is only a hint; for example, it does not override the
   Content-Language header of a HTTP response obtained by actually
   following the link.  Multiple "hreflang" parameters on a single link-
   value indicate that multiple languages are available from the
   indicated resource.

   The "media" parameter, when present, is used to indicate intended
   destination medium or media for style information (see
   [W3C.REC-html401-19991224], Section 6.13).  Note that this may be
   updated by [W3C.CR-css3-mediaqueries-20090915]).  Its value MUST be



Nottingham                   Standards Track                    [Page 8]
=0C
RFC 5988                       Web Linking                   August 2010


   quoted if it contains a semicolon (";") or comma (","), and there
   MUST NOT be more than one "media" parameter in a link-value.

   The "title" parameter, when present, is used to label the destination
   of a link such that it can be used as a human-readable identifier
   (e.g., a menu entry) in the language indicated by the Content-
   Language header (if present).  The "title" parameter MUST NOT appear
   more than once in a given link-value; occurrences after the first
   MUST be ignored by parsers.

   The "title*" parameter can be used to encode this label in a
   different character set, and/or contain language information as per
   [RFC5987].  The "title*" parameter MUST NOT appear more than once in
   a given link-value; occurrences after the first MUST be ignored by
   parsers.  If the parameter does not contain language information, its
   language is indicated by the Content-Language header (when present).

   If both the "title" and "title*" parameters appear in a link-value,
   processors SHOULD use the "title*" parameter's value.

   The "type" parameter, when present, is a hint indicating what the
   media type of the result of dereferencing the link should be.  Note
   that this is only a hint; for example, it does not override the
   Content-Type header of a HTTP response obtained by actually following
   the link.  There MUST NOT be more than one type parameter in a link-
   value.

5.5.  Examples

   For example:

   Link: <http://example.com/TheBook/chapter2>; rel=3D"previous";
         title=3D"previous chapter"

   indicates that "chapter2" is previous to this resource in a logical
   navigation path.

   Similarly,

   Link: </>; rel=3D"http://example.net/foo"

   indicates that the root resource ("/") is related to this resource
   with the extension relation type "http://example.net/foo".

   The example below shows an instance of the Link header encoding
   multiple links, and also the use of RFC 2231 encoding to encode both
   non-ASCII characters and language information.




Nottingham                   Standards Track                    [Page 9]
=0C
RFC 5988                       Web Linking                   August 2010


   Link: </TheBook/chapter2>;
         rel=3D"previous"; title*=3DUTF-8'de'letztes%20Kapitel,
         </TheBook/chapter4>;
         rel=3D"next"; title*=3DUTF-8'de'n%c3%a4chstes%20Kapitel

   Here, both links have titles encoded in UTF-8, use the German
   language ("de"), and the second link contains the Unicode code point
   U+00E4 ("LATIN SMALL LETTER A WITH DIAERESIS").

   Note that link-values can convey multiple links between the same
   target and context IRIs; for example:

       Link: <http://example.org/>;
             rel=3D"start http://example.net/relation/other"

   Here, the link to "http://example.org/" has the registered relation
   type "start" and the extension relation type
   "http://example.net/relation/other".

6.  IANA Considerations

6.1.  Link HTTP Header Registration

   This specification updates the Message Header registry entry for
   "Link" in HTTP [RFC3864] to refer to this document.

   Header field: Link
   Applicable protocol: http
   Status: standard
   Author/change controller:
       IETF  (iesg@ietf.org)
       Internet Engineering Task Force
   Specification document(s):
       [RFC5988]

6.2.  Link Relation Type Registry

   This specification establishes the Link Relation Type registry, and
   updates Atom [RFC4287] to refer to it in place of the "Registry of
   Link Relations".

   The underlying registry data (e.g., the XML file) must include
   Simplified BSD License text as described in Section 4.e of the Trust
   Legal Provisions (<http://trustee.ietf.org/license-info>).







Nottingham                   Standards Track                   [Page 10]
=0C
RFC 5988                       Web Linking                   August 2010


6.2.1.  Registering New Link Relation Types

   Relation types are registered on the advice of a Designated Expert
   (appointed by the IESG or their delegate), with a Specification
   Required (using terminology from [RFC5226]).

   The requirements for registered relation types are described in
   Section 4.1.

   Registration requests consist of the completed registration template
   below, typically published in an RFC or Open Standard (in the sense
   described by [RFC2026], Section 7).  However, to allow for the
   allocation of values prior to publication, the Designated Expert may
   approve registration once they are satisfied that a specification
   will be published.

   Note that relation types can be registered by third parties, if the
   Designated Expert determines that an unregistered relation type is
   widely deployed and not likely to be registered in a timely manner.

   The registration template is:

   o  Relation Name:

   o  Description:

   o  Reference:

   o  Notes: [optional]

   o  Application Data: [optional]

   Registration requests should be sent to the link-relations@ietf.org
   mailing list, marked clearly in the subject line (e.g., "NEW RELATION
   REQUEST").

   Within at most 14 days of the request, the Designated Expert(s) will
   either approve or deny the registration request, communicating this
   decision to the review list.  Denials should include an explanation
   and, if applicable, suggestions as to how to make the request
   successful.

   Decisions (or lack thereof) made by the Designated Expert can be
   first appealed to Application Area Directors (contactable using
   app-ads@tools.ietf.org email address or directly by looking up their
   email addresses on http://www.iesg.org/ website) and, if the
   appellant is not satisfied with the response, to the full IESG (using
   the iesg@iesg.org mailing list).



Nottingham                   Standards Track                   [Page 11]
=0C
RFC 5988                       Web Linking                   August 2010


   IANA should only accept registry updates from the Designated
   Expert(s), and should direct all requests for registration to the
   review mailing list.

6.2.2.  Initial Registry Contents

   The Link Relation Type registry's initial contents are:

   o  Relation Name: alternate
   o  Description: Designates a substitute for the link's context.
   o  Reference: [W3C.REC-html401-19991224]

   o  Relation Name: appendix
   o  Description: Refers to an appendix.
   o  Reference: [W3C.REC-html401-19991224]

   o  Relation Name: bookmark
   o  Description: Refers to a bookmark or entry point.
   o  Reference: [W3C.REC-html401-19991224]

   o  Relation Name: chapter
   o  Description: Refers to a chapter in a collection of resources.
   o  Reference: [W3C.REC-html401-19991224]

   o  Relation Name: contents
   o  Description: Refers to a table of contents.
   o  Reference: [W3C.REC-html401-19991224]

   o  Relation Name: copyright
   o  Description: Refers to a copyright statement that applies to the
      link's context.
   o  Reference: [W3C.REC-html401-19991224]

   o  Relation Name: current
   o  Description: Refers to a resource containing the most recent
      item(s) in a collection of resources.
   o  Reference: [RFC5005]

   o  Relation Name: describedby
   o  Description: Refers to a resource providing information about the
      link's context.
   o  Documentation: <http://www.w3.org/TR/powder-dr/#assoc-linking>

   o  Relation Name: edit
   o  Description: Refers to a resource that can be used to edit the
      link's context.





Nottingham                   Standards Track                   [Page 12]
=0C
RFC 5988                       Web Linking                   August 2010


   o  Reference: [RFC5023]

   o  Relation Name: edit-media
   o  Description: Refers to a resource that can be used to edit media
      associated with the link's context.
   o  Reference: [RFC5023]

   o  Relation Name: enclosure
   o  Description: Identifies a related resource that is potentially
      large and might require special handling.
   o  Reference: [RFC4287]

   o  Relation Name: first
   o  Description: An IRI that refers to the furthest preceding resource
      in a series of resources.
   o  Reference: [RFC5988]
   o  Notes: this relation type registration did not indicate a
      reference.  Originally requested by Mark Nottingham in December
      2004.

   o  Relation Name: glossary
   o  Description: Refers to a glossary of terms.
   o  Reference: [W3C.REC-html401-19991224]

   o  Relation Name: help
   o  Description: Refers to a resource offering help (more information,
      links to other sources information, etc.)
   o  Reference: [W3C.REC-html401-19991224]

   o  Relation Name: hub
   o  Description: Refers to a hub that enables registration for
      notification of updates to the context.
   o  Reference: <http://pubsubhubbub.googlecode.com/> <http://
      pubsubhubbub.googlecode.com/svn/trunk/pubsubhubbub-core-0.3.html>
   o  Notes: this relation type was requested by Brett Slatkin.

   o  Relation Name: index
   o  Description: Refers to an index.
   o  Reference: [W3C.REC-html401-19991224]

   o  Relation Name: last
   o  Description: An IRI that refers to the furthest following resource
      in a series of resources.
   o  Reference: [RFC5988]
   o  Notes: this relation type registration did not indicate a
      reference.  Originally requested by Mark Nottingham in December
      2004.




Nottingham                   Standards Track                   [Page 13]
=0C
RFC 5988                       Web Linking                   August 2010


   o  Relation Name: latest-version
   o  Description: Points to a resource containing the latest (e.g.,
      current) version of the context.
   o  Reference: [RFC5829]

   o  Relation Name: license
   o  Description: Refers to a license associated with the link's
      context.
   o  Reference: [RFC4946]

   o  Relation Name: next
   o  Description: Refers to the next resource in a ordered series of
      resources.
   o  Reference: [W3C.REC-html401-19991224]

   o  Relation Name: next-archive
   o  Description: Refers to the immediately following archive resource.
   o  Reference: [RFC5005]

   o  Relation Name: payment
   o  Description: indicates a resource where payment is accepted.
   o  Reference: [RFC5988]
   o  Notes: this relation type registration did not indicate a
      reference.  Requested by Joshua Kinberg and Robert Sayre.  It is
      meant as a general way to facilitate acts of payment, and thus
      this specification makes no assumptions on the type of payment or
      transaction protocol.  Examples may include a Web page where
      donations are accepted or where goods and services are available
      for purchase. rel=3D"payment" is not intended to initiate an
      automated transaction.  In Atom documents, a link element with a
      rel=3D"payment" attribute may exist at the feed/channel level =
and/or
      the entry/item level.  For example, a rel=3D"payment" link at the
      feed/channel level may point to a "tip jar" URI, whereas an entry/
      item containing a book review may include a rel=3D"payment" link
      that points to the location where the book may be purchased
      through an online retailer.

   o  Relation Name: prev
   o  Description: Refers to the previous resource in an ordered series
      of resources.  Synonym for "previous".
   o  Reference: [W3C.REC-html401-19991224]

   o  Relation Name: predecessor-version
   o  Description: Points to a resource containing the predecessor
      version in the version history.
   o  Reference: [RFC5829]





Nottingham                   Standards Track                   [Page 14]
=0C
RFC 5988                       Web Linking                   August 2010


   o  Relation Name: previous
   o  Description: Refers to the previous resource in an ordered series
      of resources.  Synonym for "prev".
   o  Reference: [W3C.REC-html401-19991224]

   o  Relation Name: prev-archive
   o  Description: Refers to the immediately preceding archive resource.
   o  Reference: [RFC5005]

   o  Relation Name: related
   o  Description: Identifies a related resource.
   o  Reference: [RFC4287]

   o  Relation Name: replies
   o  Description: Identifies a resource that is a reply to the context
      of the link.
   o  Reference: [RFC4685]

   o  Relation Name: section
   o  Description: Refers to a section in a collection of resources.
   o  Reference: [W3C.REC-html401-19991224]

   o  Relation Name: self
   o  Description: Conveys an identifier for the link's context.
   o  Reference: [RFC4287]

   o  Relation Name: service
   o  Description: Indicates a URI that can be used to retrieve a
      service document.
   o  Reference: [RFC5023]
   o  Notes: When used in an Atom document, this relation type specifies
      Atom Publishing Protocol service documents by default.  Requested
      by James Snell.

   o  Relation Name: start
   o  Description: Refers to the first resource in a collection of
      resources.
   o  Reference: [W3C.REC-html401-19991224]

   o  Relation Name: stylesheet
   o  Description: Refers to an external style sheet.
   o  Reference: [W3C.REC-html401-19991224]

   o  Relation Name: subsection
   o  Description: Refers to a resource serving as a subsection in a
      collection of resources.





Nottingham                   Standards Track                   [Page 15]
=0C
RFC 5988                       Web Linking                   August 2010


   o  Reference: [W3C.REC-html401-19991224]

   o  Relation Name: successor-version
   o  Description: Points to a resource containing the successor version
      in the version history.
   o  Reference: [RFC5829]

   o  Relation Name: up
   o  Description: Refers to a parent document in a hierarchy of
      documents.
   o  Reference: [RFC5988]
   o  Notes: this relation type registration did not indicate a
      reference.  Requested by Noah Slater.

   o  Relation Name: version-history
   o  Description: points to a resource containing the version history
      for the context.
   o  Reference: [RFC5829]

   o  Relation Name: via
   o  Description: Identifies a resource that is the source of the
      information in the link's context.
   o  Reference: [RFC4287]

   o  Relation Name: working-copy
   o  Description: Points to a working copy for this resource.
   o  Reference: [RFC5829]

   o  Relation Name: working-copy-of
   o  Description: Points to the versioned resource from which this
      working copy was obtained.
   o  Reference: [RFC5829]

6.3.  Link Relation Application Data Registry

   This specification also establishes the Link Relation Application
   Field registry, to allow entries in the Link Relation Type registry
   to be extended with application-specific data (hereafter, "app data")
   specific to all instances of a given link relation type.

   Application data is registered on the advice of a Designated Expert
   (appointed by the IESG or their delegate), with a Specification
   Required (using terminology from [RFC5226]).

   Registration requests consist of the completed registration template
   below;





Nottingham                   Standards Track                   [Page 16]
=0C
RFC 5988                       Web Linking                   August 2010


   o  Application Name:

   o  Description:

   o  Default Value:

   o  Notes: [optional]

   The Description SHOULD identify the value space of the app data.  The
   Default Value MUST be appropriate to entries to which the app data
   does not apply.

   Entries that pre-date the addition of app data will automatically be
   considered to have the default value for that app data; if there are
   exceptions, the modification of such entries should be coordinated by
   the Designated Expert(s), in consultation with the author of the
   proposed app data as well as the registrant of the existing entry (if
   possible).

   Registration requests should be sent to the link-relations@ietf.org
   mailing list, marked clearly in the subject line (e.g., "NEW APP
   DATA").

   Within at most 14 days of the request, the Designated Expert will
   either approve or deny the registration request, communicating this
   decision to the review list.  Denials should include an explanation
   and, if applicable, suggestions as to how to make the request
   successful.  Registration requests that are undetermined for a period
   longer than 21 days can be brought to the IESG's attention (using the
   iesg@iesg.org mailing list) for resolution.

   When a registration request is successful, the Designated Expert will
   forward it to IANA for publication.  IANA should only accept registry
   updates from the Designated Expert(s), and should direct all requests
   for registration to the review mailing list.

7.  Security Considerations

   The content of the Link header field is not secure, private or
   integrity-guaranteed, and due caution should be exercised when using
   it.  Use of Transport Layer Security (TLS) with HTTP ([RFC2818] and
   [RFC2817]) is currently the only end-to-end way to provide such
   protection.

   Applications that take advantage of typed links should consider the
   attack vectors opened by automatically following, trusting, or
   otherwise using links gathered from HTTP headers.  In particular,
   Link headers that use the "anchor" parameter to associate a link's



Nottingham                   Standards Track                   [Page 17]
=0C
RFC 5988                       Web Linking                   August 2010


   context with another resource should be treated with due caution.

   The Link entity-header field makes extensive use of IRIs and URIs.
   See [RFC3987] for security considerations relating to IRIs.  See
   [RFC3986] for security considerations relating to URIs.  See
   [RFC2616] for security considerations relating to HTTP headers.

8.  Internationalisation Considerations

   Target IRIs may need to be converted to URIs in order to express them
   in serialisations that do not support IRIs.  This includes the Link
   HTTP header.

   Similarly, the anchor parameter of the Link header does not support
   IRIs, and therefore IRIs must be converted to URIs before inclusion
   there.

   Relation types are defined as URIs, not IRIs, to aid in their
   comparison.  It is not expected that they will be displayed to end
   users.































Nottingham                   Standards Track                   [Page 18]
=0C
RFC 5988                       Web Linking                   August 2010


9.  References

9.1.  Normative References

   [RFC2026]  Bradner, S., "The Internet Standards Process -- Revision
              3", BCP 9, RFC 2026, October 1996.

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119, March 1997.

   [RFC2616]  Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,
              Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext
              Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999.

   [RFC3864]  Klyne, G., Nottingham, M., and J. Mogul, "Registration
              Procedures for Message Header Fields", BCP 90, RFC 3864,
              September 2004.

   [RFC3986]  Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
              Resource Identifier (URI): Generic Syntax", STD 66,
              RFC 3986, January 2005.

   [RFC3987]  Duerst, M. and M. Suignard, "Internationalized Resource
              Identifiers (IRIs)", RFC 3987, January 2005.

   [RFC4288]  Freed, N. and J. Klensin, "Media Type Specifications and
              Registration Procedures", BCP 13, RFC 4288, December 2005.

   [RFC5226]  Narten, T. and H. Alvestrand, "Guidelines for Writing an
              IANA Considerations Section in RFCs", BCP 26, RFC 5226,
              May 2008.

   [RFC5646]  Phillips, A. and M. Davis, "Tags for Identifying
              Languages", BCP 47, RFC 5646, September 2009.

   [RFC5987]  Reschke, J., "Character Set and Language Encoding for
              Hypertext Transfer Protocol (HTTP) Header Field
              Parameters", RFC 5987, August 2010.

9.2.  Informative References

   [RFC2068]  Fielding, R., Gettys, J., Mogul, J., Nielsen, H., and T.
              Berners-Lee, "Hypertext Transfer Protocol -- HTTP/1.1",
              RFC 2068, January 1997.

   [RFC2817]  Khare, R. and S. Lawrence, "Upgrading to TLS Within
              HTTP/1.1", RFC 2817, May 2000.




Nottingham                   Standards Track                   [Page 19]
=0C
RFC 5988                       Web Linking                   August 2010


   [RFC2818]  Rescorla, E., "HTTP Over TLS", RFC 2818, May 2000.

   [RFC4287]  Nottingham, M., Ed. and R. Sayre, Ed., "The Atom
              Syndication Format", RFC 4287, December 2005.

   [RFC4685]  Snell, J., "Atom Threading Extensions", RFC 4685,
              September 2006.

   [RFC4946]  Snell, J., "Atom License Extension", RFC 4946, July 2007.

   [RFC5005]  Nottingham, M., "Feed Paging and Archiving", RFC 5005,
              September 2007.

   [RFC5023]  Gregorio, J. and B. de hOra, "The Atom Publishing
              Protocol", RFC 5023, October 2007.

   [RFC5829]  Brown, A., Clemm, G., and J. Reschke, "Link Relation Types
              for Simple Version Navigation between Web Resources",
              RFC 5829, April 2010.

   [W3C.CR-css3-mediaqueries-20090915]
              van Kesteren, A., Glazman, D., Lie, H., and T. Celik,
              "Media Queries", W3C Candidate Recommendation CR-css3-
              mediaqueries-20090915, September 2009,
              <http://www.w3.org/TR/2009/
              CR-css3-mediaqueries-20090915/>.

              Latest version available at
              <http://www.w3.org/TR/css3-mediaqueries/>.

   [W3C.CR-curie-20090116]
              Birbeck, M. and S. McCarron, "CURIE Syntax 1.0", W3C
              Candidate Recommendation CR-curie-20090116, January 2009,
              <http://www.w3.org/TR/2009/CR-curie-20090116>.

              Latest version available at <http://www.w3.org/TR/curie>.

   [W3C.REC-html401-19991224]
              Le Hors, A., Raggett, D., and I. Jacobs, "HTML 4.01
              Specification", W3C Recommendation REC-html401-19991224,
              December 1999,
              <http://www.w3.org/TR/1999/REC-html401-19991224>.

              Latest version available at
              <http://www.w3.org/TR/html401>.

   [W3C.REC-rdfa-syntax-20081014]
              Adida, B., Birbeck, M., McCarron, S., and S. Pemberton,



Nottingham                   Standards Track                   [Page 20]
=0C
RFC 5988                       Web Linking                   August 2010


              "RDFa in XHTML: Syntax and Processing", W3C
              Recommendation REC-rdfa-syntax-20081014, October 2008,
              <http://www.w3.org/TR/2008/REC-rdfa-syntax-20081014>.

              Latest version available at
              <http://www.w3.org/TR/rdfa-syntax>.

   [W3C.REC-xhtml-basic-20080729]
              Baker, M., Ishikawa, M., Stark, P., Matsui, S., Wugofski,
              T., and T. Yamakami, "XHTML[TM] Basic 1.1", W3C
              Recommendation REC-xhtml-basic-20080729, July 2008,
              <http://www.w3.org/TR/2008/REC-xhtml-basic-20080729>.

              Latest version available at
              <http://www.w3.org/TR/xhtml-basic>.

Appendix A.  Notes on Using the Link Header with the HTML4 Format

   HTML motivated the original syntax of the Link header, and many of
   the design decisions in this document are driven by a desire to stay
   compatible with these uses.

   In HTML4, the link element can be mapped to links as specified here
   by using the "href" attribute for the target URI, and "rel" to convey
   the relation type, as in the Link header.  The context of the link is
   the URI associated with the entire HTML document.

   All of the link relation types defined by HTML4 have been included in
   the Link Relation Type registry, so they can be used without
   modification.  However, there are several potential ways to serialise
   extension relation types into HTML4, including

   o  As absolute URIs,

   o  using the document-wide "profile" attribute's URI as a prefix for
      relation types, or

   o  using the RDFa [W3C.REC-rdfa-syntax-20081014] convention of
      mapping token prefixes to URIs (in a manner similar to XML name
      spaces) (note that RDFa is only defined to work in XHTML
      [W3C.REC-xhtml-basic-20080729], but is sometimes used in HTML4).

   Individual applications of linking will therefore need to define how
   their extension links should be serialised into HTML4.

   Surveys of existing HTML content have shown that unregistered link
   relation types that are not URIs are (perhaps inevitably) common.
   Consuming HTML implementations should not consider such unregistered



Nottingham                   Standards Track                   [Page 21]
=0C
RFC 5988                       Web Linking                   August 2010


   short links to be errors, but rather relation types with a local
   scope (i.e., their meaning is specific and perhaps private to that
   document).

   HTML4 also defines several attributes on links that are not
   explicitly defined by the Link header.  These attributes can be
   serialised as link-extensions to maintain fidelity.

   Finally, the HTML4 specification gives a special meaning when the
   "alternate" and "stylesheet" relation types coincide in the same
   link.  Such links should be serialised in the Link header using a
   single list of relation-types (e.g., rel=3D"alternate stylesheet") to
   preserve this relationship.

Appendix B.  Notes on Using the Link Header with the Atom Format

   Atom conveys links in the atom:link element, with the "href"
   attribute indicating the target IRI and the "rel" attribute
   containing the relation type.  The context of the link is either a
   feed IRI or an entry ID, depending on where it appears; generally,
   feed-level links are obvious candidates for transmission as a Link
   header.

   When serialising an atom:link into a Link header, it is necessary to
   convert target IRIs (if used) to URIs.

   Atom defines extension relation types in terms of IRIs.  This
   specification re-defines them as URIs, to simplify and reduce errors
   in their comparison.

   Atom allows registered link relation types to be serialised as
   absolute URIs.  Such relation types SHOULD be converted to the
   appropriate registered form (e.g.,
   "http://www.iana.org/assignments/relation/self" to "self") so that
   they are not mistaken for extension relation types.

   Furthermore, Atom link relation types are always compared in a case-
   sensitive fashion; therefore, registered link relation types SHOULD
   be converted to their registered form (usually, lowercase) when
   serialised in an Atom document.

   Note also that while the Link header allows multiple relations to be
   serialised in a single link, atom:link does not.  In this case, a
   single link-value may map to several atom:link elements.

   As with HTML, atom:link defines some attributes that are not
   explicitly mirrored in the Link header syntax, but they can also be
   used as link-extensions to maintain fidelity.



Nottingham                   Standards Track                   [Page 22]
=0C
RFC 5988                       Web Linking                   August 2010


Appendix C.  Acknowledgements

   This specification lifts the idea and definition for the Link header
   from RFC 2068; credit for it belongs entirely to the authors of and
   contributors to that document.  The link relation type registrations
   themselves are sourced from several documents; see the applicable
   references.

   The author would like to thank the many people who commented upon,
   encouraged and gave feedback to this specification, especially
   including Frank Ellermann, Roy Fielding, Eran Hammer-Lahav, and
   Julian Reschke.

Author's Address

   Mark Nottingham

   EMail: mnot@mnot.net
   URI:   http://www.mnot.net/
































Nottingham                   Standards Track                   [Page 23]
=0C

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



--
Mark Nottingham     http://www.mnot.net/


--Apple-Mail-17--181425568--

From phil@juniper.net  Thu Sep 23 06:02:47 2010
Return-Path: <phil@juniper.net>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6A4FA28C0F2; Thu, 23 Sep 2010 06:02:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.61
X-Spam-Level: 
X-Spam-Status: No, score=-6.61 tagged_above=-999 required=5 tests=[AWL=-0.011,  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 09fR2A60yMIM; Thu, 23 Sep 2010 06:02:45 -0700 (PDT)
Received: from exprod7og109.obsmtp.com (exprod7og109.obsmtp.com [64.18.2.171]) by core3.amsl.com (Postfix) with ESMTP id C92FC3A6929; Thu, 23 Sep 2010 06:02:37 -0700 (PDT)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob109.postini.com ([64.18.6.12]) with SMTP ID DSNKTJtQBy707gDccqdW2HMaRU/1Y8OhnWaI@postini.com; Thu, 23 Sep 2010 06:03:15 PDT
Received: from magenta.juniper.net (172.17.27.123) by P-EMHUB03-HQ.jnpr.net (172.24.192.33) with Microsoft SMTP Server (TLS) id 8.2.254.0; Thu, 23 Sep 2010 05:59:37 -0700
Received: from idle.juniper.net (idleski.juniper.net [172.25.4.26])	by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id o8NCxaU64050; Thu, 23 Sep 2010 05:59:36 -0700 (PDT)	(envelope-from phil@juniper.net)
Received: from idle.juniper.net (localhost [127.0.0.1])	by idle.juniper.net (8.14.3/8.14.3) with ESMTP id o8NCd8Hn019039; Thu, 23 Sep 2010 12:39:08 GMT (envelope-from phil@idle.juniper.net)
Message-ID: <201009231239.o8NCd8Hn019039@idle.juniper.net>
To: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <8FE3C30A-D376-4226-B253-208402285032@tzi.org> 
Date: Thu, 23 Sep 2010 08:39:08 -0400
From: Phil Shafer <phil@juniper.net>
MIME-Version: 1.0
Content-Type: text/plain
X-Mailman-Approved-At: Thu, 23 Sep 2010 08:26:30 -0700
Cc: david.partain@ericsson.com, iesg@ietf.org, apps-discuss@ietf.org, david.kessens@nsn.com
Subject: Re: [apps-discuss] apps-team review of draft-ietf-netmod-arch
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Sep 2010 13:02:47 -0000

Carsten Bormann writes:
>I have been selected as the Applications Area Review Team reviewer

Thank you for your review.

>Section 3.2, which reads like a list of selling points, is somewhat
>opaque (e.g., what is the semantics of "text-friendly"?) and contains
>some statements that are not supported by the rest of the document.

"text-friendly" means I can use the text-oriented tools mentioned
in RFC3535 ("can be made with arbitrary text processing tools",
"text processing tools such as diff, and version management tools
such as RCS or CVS, can be used to process configurations").  The
ability to post a diff or brief section of a module to a mailing
list is also crucial.  By comparison, binary protocols are not
friendly to these tools, and posting a diff of a binary file would
not be friendly.

>Where does the list of item headings come from?  (Not from RFC 3535,
>e.g. section 5, which would be a natural source.)  A better
>introduction might adjust the expectations of the reader to fit what
>is there now.

The headers are based on 3535, but in a more brief format, e.g. "Dump
and restore" instead of:

   7.  A mechanism to dump and restore configurations is a primitive
       operation needed by operators.  Standards for pulling and pushing
       configurations from/to devices are desirable.

>But sentences such as:
>
>       NETCONF and YANG are solid and reliable technologies.
>
>simply are not RFC material (even if my personal opinion does happen
>to agree).

Perhaps "NETCONF and YANG are designed to be robust and reliable
technologies, with attention paid to real world use case and
operator scenarios."?

>For me, the introduction appears slightly optimistic about the value
>of data modeling languages -- "A client knows how to create valid data
>for the server, and knows what data will be sent from the server.  A
>server knows the rules that govern the data and how it should behave."
>Of course, this can only be true within the limits of what the data
>modeling language can describe (or more precisely: the limits of what we
>can expect modelers to be able to describe through this language).

I see this as a more generic description, not an optimistic one.  We
build models to describe not only the domain being modeled but the
interactions between parties manipulating elements of those models.
The model tries to fully describe the domain in a way that removes
surprises from that interaction.  If the model says a leaf is an
integer, then neither side should feel that "cow" is an acceptable
value.

>(And this, BTW, is exactly the most important reason why a data
>modeling language benefits from being adapted to the problem domain; a
>reason not otherwise given in the introduction.)

This is mentioned:

    The use of NETCONF operations
    place requirements on the data content that are not shared with the
    static document problem domain addressed by schema languages like XSD
    or Relax NG.

>The Description for "delete-config" in the table of operations says:
>    Delete a portion of a configuration datastore
>To me, section 7.4 of RFC 4741 reads as if the operation can be used
>to delete an entire configuration datastore.

Good catch.  I was thinking of the delete attribute, not the RPC.
Will fix.

>The XML example in 2.2.3 misses the namespace declaration for the
>namespace prefix "vendorx".  [Have all examples been validated?]

Will fix.

>Section 2.3.2 mentions RELAX NG in the title and is then silent about
>that in the text.  Contrary to the second paragraph, DSDL is a
>*family* of schema languages, not a single standard (and
>draft-ietf-netmod-dsdl-map-07.txt does address the family, not just
>RELAX NG).

DSDL includes Relax NG, and Relax NG has far better name recognition,
so it was added in parens.  I can add text to fully describe this
relationship.

>We dont have a good way to reference the genesis of an IETF activity
>in RFCs.  This draft makes two mistakes in handling this difficult =
>problem:
>-- it references an expired Internet-Draft by just giving a draft
>   name (draft-presuhn-rcdml-03.txt).  There is no really good
>   solution to this problem (except turning this document into another
>   RFC, which the WG may have decided not to do).

This is an unfortunate side effect of allowing drafts to expire.
Is there a more proper way to reference this?  I was to at least
give something an interested reader can google to get complete
information.

>-- it references an ietf@ietf.org email message by giving a URI to a
>   random mail archiving site.  This message, if it is as useful for
>   this document as it seems to be, should be either cited through its
>   ietf.org URI
>   (http://www.ietf.org/mail-archive/web/ietf/current/msg51644.html)
>   or, preferably (if the message author concurs), it should instead
>   be replicated in an annex.

I'll correct the URL.  The message is merely a historical note
and is not worth replicating IMHO.

>Is the intention to publish this document in a cluster with the
>referenced documents:
>-- [RFCYANG] draft-ietf-netmod-yang-13,
>-- [RFCYANGDSDL] draft-ietf-netmod-dsdl-map-06,
>-- [RFCYANGTYPES] draft-ietf-netmod-yang-types-09.txt, and
>-- [RFCYANGUSAGE] draft-ietf-netmod-yang-usage-10.txt?
>If not, the reference labels should probably not be called "RFCXXX".

Yes, and I believe all these documents are in last call.

>Section 1: "This brings NETCONF to a point where is can be used to
>develop standards within the IETF." -- I assume this statement is
>about data model standards?  Or what kind of standard?

Yes, standards that contain data models.  I'll correct it to
"standard data models".

>Section 3.3.3.2 entraps itself by first using "over the wire" and then
>having to add a strange retraction that in fact the wire will only see
>encrypted material.  But the point here is not the wire, but the fact
>that NETCONF implementations can "ascertain whether a specific NETCONF
>payload is obeying the rules".  Strike the "over the wire".

Changed to "XML encoding for data sent via NETCONF."

>  -- The document has a disclaimer for pre-RFC5378 work, but was first
>     submitted on or after 10 November 2008.  Does it really need the
>     disclaimer?

I was surprised that id-nits complains about this, but work predates
200902.  Please let me know if there's a more appropriate setting than
the current one (<rfc ipr="pre5378Trust200902" ...).

>  =3D=3D Outdated reference: A later version (-07) exists of
>     draft-ietf-netmod-dsdl-map-06

A consequence of the number of drafts the WG is producing.

Thanks,
 Phil

From barryleiba.mailing.lists@gmail.com  Thu Sep 23 08:41:56 2010
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A80993A6AE5 for <apps-discuss@core3.amsl.com>; Thu, 23 Sep 2010 08:41:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.849
X-Spam-Level: 
X-Spam-Status: No, score=-2.849 tagged_above=-999 required=5 tests=[AWL=-0.250, 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 nVj56yBXJrdl for <apps-discuss@core3.amsl.com>; Thu, 23 Sep 2010 08:41:07 -0700 (PDT)
Received: from mail-px0-f172.google.com (mail-px0-f172.google.com [209.85.212.172]) by core3.amsl.com (Postfix) with ESMTP id 0B4E03A69E4 for <apps-discuss@ietf.org>; Thu, 23 Sep 2010 08:40:00 -0700 (PDT)
Received: by pxi6 with SMTP id 6so592468pxi.31 for <apps-discuss@ietf.org>; Thu, 23 Sep 2010 08:40:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:reply-to :in-reply-to:references:date:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=TtTjn34B4GAsjewAWYsORpep+B/zgwJcdkIeZb+gpxQ=; b=FGo4YF3BbSxUxYiE8DpI2bEyPDX0AfhA0sKcMJb3IpgodN+70iWt3FL6JdIaGXsjbG Lgkshse3TVM9WszirymB3NzAphUWyLgUusm/oFRjgyXe8371YxiUdDOwhHmu/NYHXLzo m/wvp8wQVJkn/TutWs1WYaelVzKIGwUbkhfLQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; b=qjMHpaJ6DQxQp76NTnaChM6ET0cXXmvm8Q2jgakYiLQ7IBj0eijBWAbx3TSboNQ8kC X/OVPYLquS1LLartB8+1s/GaWAfetHfQ3tj4YuIJfWO/lBTclUIaFVLr9yxQ2tYJ4cjA iq3/6ZWmJT+YEjn+gYNnGqig/EXh0t12B8XKA=
MIME-Version: 1.0
Received: by 10.114.131.19 with SMTP id e19mr1994696wad.147.1285256429299; Thu, 23 Sep 2010 08:40:29 -0700 (PDT)
Received: by 10.42.3.75 with HTTP; Thu, 23 Sep 2010 08:40:29 -0700 (PDT)
In-Reply-To: <BB012BD379D7B046ABE1472D8093C61C02AFC3C25A@EXCH-C2.corp.cloudmark.com>
References: <BB012BD379D7B046ABE1472D8093C61C02AFC3C25A@EXCH-C2.corp.cloudmark.com>
Date: Thu, 23 Sep 2010 11:40:29 -0400
Message-ID: <AANLkTikqEQFtKB0s2jee48CtbmBZQAhJ8q8mpA4eE17N@mail.gmail.com>
From: Barry Leiba <barryleiba.mailing.lists@gmail.com>
To: "Murray S. Kucherawy" <msk@cloudmark.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] multipart/report
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: barryleiba@computer.org
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Sep 2010 15:41:56 -0000

> We could do a message/digest, each sub-part of which is message/rfc822 an=
d
> the MIME type within that is multipart/report.=A0 One could argue that th=
is approach
> conforms to the multipart/report rules by having that be the outermost MI=
ME part
> of each constituent message in the aggregate message, but that might be h=
ard
> to defend given the spirit of that rule.

What happens if you forward a multipart/report as an imbedded message?
 My guess is that you wind up with something like this:

0 multipart/mixed
   1.0   text/plain
   1.1   message/rfc822
      2.1      multipart/report

I don't think anyone would call the forwarded message a violation.
By the same token, I think what you describe above makes sense.

Barry

From alexey.melnikov@isode.com  Thu Sep 23 11:14:18 2010
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D4F0B3A69F3 for <apps-discuss@core3.amsl.com>; Thu, 23 Sep 2010 11:14:18 -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 PP3tWQM11TZz for <apps-discuss@core3.amsl.com>; Thu, 23 Sep 2010 11:14:16 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id 16C273A6943 for <Apps-Discuss@ietf.org>; Thu, 23 Sep 2010 11:14:16 -0700 (PDT)
Received: from [192.168.1.124] ((unknown) [62.3.217.253])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <TJuZDABIEBCJ@rufus.isode.com>; Thu, 23 Sep 2010 19:14:36 +0100
X-SMTP-Protocol-Errors: NORDNS
Message-ID: <4C9B98EE.80605@isode.com>
Date: Thu, 23 Sep 2010 19:14:06 +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: Apps-Discuss@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [apps-discuss] WG meeting request deadline is on Monday
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Sep 2010 18:14:19 -0000

This is just a reminder for WG chairs (and editors), that the deadline 
for requesting WG meeting slots for Beijing is next Monday (September 27).


From stpeter@stpeter.im  Thu Sep 23 11:27:04 2010
Return-Path: <stpeter@stpeter.im>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 051753A6AC4 for <apps-discuss@core3.amsl.com>; Thu, 23 Sep 2010 11:27:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.545
X-Spam-Level: 
X-Spam-Status: No, score=-102.545 tagged_above=-999 required=5 tests=[AWL=0.054, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FFLLByUZB8sw for <apps-discuss@core3.amsl.com>; Thu, 23 Sep 2010 11:27:03 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id 062FB3A6AC0 for <apps-discuss@ietf.org>; Thu, 23 Sep 2010 11:27:03 -0700 (PDT)
Received: from dhcp-64-101-72-245.cisco.com (dhcp-64-101-72-245.cisco.com [64.101.72.245]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id AE19C40074 for <apps-discuss@ietf.org>; Thu, 23 Sep 2010 12:32:32 -0600 (MDT)
Message-ID: <4C9B9C13.8070707@stpeter.im>
Date: Thu, 23 Sep 2010 12:27: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.1.12) Gecko/20100914 Thunderbird/3.0.8
MIME-Version: 1.0
To: apps-discuss@ietf.org
References: <4C9B98EE.80605@isode.com>
In-Reply-To: <4C9B98EE.80605@isode.com>
X-Enigmail-Version: 1.0.1
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [apps-discuss] WG meeting request deadline is on Monday
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Sep 2010 18:27:04 -0000

On 9/23/10 12:14 PM, Alexey Melnikov wrote:
> This is just a reminder for WG chairs (and editors), that the deadline
> for requesting WG meeting slots for Beijing is next Monday (September 27).

Heh, I just sent a message to my chairs about that. :)

The session request tool is here:

https://datatracker.ietf.org/cgi-bin/wg/wg_session_requester.cgi

Peter

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



From moore@network-heretics.com  Thu Sep 23 17:42:59 2010
Return-Path: <moore@network-heretics.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8AC7E3A68FA for <apps-discuss@core3.amsl.com>; Thu, 23 Sep 2010 17:42:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.556
X-Spam-Level: 
X-Spam-Status: No, score=-2.556 tagged_above=-999 required=5 tests=[AWL=0.042,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 0hNMdf9oXydU for <apps-discuss@core3.amsl.com>; Thu, 23 Sep 2010 17:42:57 -0700 (PDT)
Received: from m1.imap-partners.net (m1.imap-partners.net [64.13.152.131]) by core3.amsl.com (Postfix) with ESMTP id BE2853A6804 for <apps-discuss@ietf.org>; Thu, 23 Sep 2010 17:42:57 -0700 (PDT)
Received: from 99-205-255-194.pools.spcsdns.net (99-205-255-194.pools.spcsdns.net [99.205.255.194]) by m1.imap-partners.net (MOS 4.1.8-GA) with ESMTP id CFQ08969 (AUTH admin@network-heretics.com); Thu, 23 Sep 2010 17:43:21 -0700
X-Mirapoint-Received-SPF: 99.205.255.194 99-205-255-194.pools.spcsdns.net <moore@network-heretics.com> 5 none
X-Mirapoint-Received-SPF: 99.205.255.194 99-205-255-194.pools.spcsdns.net <moore@network-heretics.com> 5 none
X-Mirapoint-Received-SPF: 99.205.255.194 99-205-255-194.pools.spcsdns.net <moore@network-heretics.com> 5 none
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: multipart/alternative; boundary=Apple-Mail-39--108360690
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <BB012BD379D7B046ABE1472D8093C61C02AFC3C25A@EXCH-C2.corp.cloudmark.com>
Date: Thu, 23 Sep 2010 20:43:20 -0400
Message-Id: <F99C7C1F-CA11-49DC-BE4D-F8E4BC065E43@network-heretics.com>
References: <BB012BD379D7B046ABE1472D8093C61C02AFC3C25A@EXCH-C2.corp.cloudmark.com>
To: "Murray S. Kucherawy" <msk@cloudmark.com>
X-Mailer: Apple Mail (2.1081)
Cc: "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] multipart/report
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Sep 2010 00:42:59 -0000

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

[NB: top posting is evil.]

> I'm doing some work with the OMA in the area of spam reporting.  They =
have developed an XML message format for reporting spam from a mobile =
handset.  Because SMS and MMS (and even IM) have different structure =
than email, they went with something more extensible than what we =
currently do with DSNs.  I'm helping that group try to converge with =
what we do in the email world, especially with what the MARF working =
group is producing (e.g., ARF, specified by recently-published RFC5965). =
 The first thing is to register the MIME type they've created, and so =
I've crafted a template for that.
>=20
> The next thing we'd like to achieve is to be able to specify multiple =
spam reports in a single message, regardless of transport (they =
currently use HTTP POST, but there's no reason SMTP couldn't be used).  =
The most obvious thing to do would be to use a multipart/mixed MIME =
message, and then include their MIME type in each of "n" parts.  =
However, this is different than what was done with ARF, which used =
multipart/report.  The advantage to using multipart/report, which =
stipulates that it must be the outermost MIME type, is that you know =
right away that you're processing a report rather than having to parse =
part way into the MIME tree to figure that out.  (According to Tony =
Hansen, that's why this rule was put in place.)  But although =
multipart/report is the most obvious construct for doing this, it =
doesn't lend itself to multi-report messages.  So to get these to =
converge, we have to be a little creative or be very creative (in the =
"create a lot of documents" sense).

My vague recollection is that multipart/report was constrained to be the =
top-level MIME type mostly to ease the burden on mail gateways that =
would have wanted to automatically map between DSN and another kind of =
(non)delivery report.  =20

The requirement that it be the outermost MIME type might be a bit =
misstated.   I don't think anyone intended that you shouldn't be able to =
forward a DSN as an attachment to another message.  But there's a subtle =
but important semantic difference between sending a multipart/report at =
the top level of a message and sending a multipart/report as a body part =
within some other multipart or message type.  In the first case, the =
mail system is sending a report in response to a specific delivery =
attempt; in the second, a sender is just sending an attachment to a =
recipient and there's no reason that the mail system should care what =
that attachment is.   It might be reasonable, say, for a user agent or =
message submission agent of some kind (could be traditional, fax, or =
voice) to use received multipart/report messages to keep track of =
whether a sent message were delivered or whether delivery failed; but it =
would not be reasonable for that same user agent or message submission =
agent to look past the top level of received messages to see if they =
happen to contain a multipart/report.

(In a very ideal world, reporting should have been purely an SMTP =
function... we're mixing layers by sending reports in ordinary email =
messages.  But SMTP has worked that way for ~30 years; RFC 1891 et seq =
just tried to standardize the format.)

So my top-level response would be that multipart/report as a top-level =
type is appropriate when (and only when) the mail system is issuing a =
report in response to a delivery attempt.   I don't see anything =
inherently wrong with shipping multipart/reports around as children of a =
multipart/mixed, say, but when you do that, it no longer means that the =
mail system is sending a report in response to a delivery attempt.

I'm not sure I understand in what context you propose to use =
multipart/report for spam reporting.  It seems obvious that if the mail =
system is issuing a spam report to an envelope sender ("we refuse to =
deliver this; we think it's spam"), that a top-level multipart/report =
would be appropriate, but my guess is that this is not the intended use. =
  If you're using multipart/report for other purposes, e.g. to transmit =
a batch of spam reports from one MSP to another, I don't see any reason =
why it should be the top-level type, and I'd actually suggest that =
making it the top-level type would be inappropriate.  A multipart/mixed =
at the top level with multipart/reports body parts seems much more =
appropriate. =20

Note also that multipart/report was designed to report potentially =
multiple delivery attempts - but for a single message.  It seems =
inappropriate to try to use a single multipart/report to report =
information about multiple messages.=20

Bottom line: I doubt that using multipart/report as a top-level type is =
appropriate for what you seem to want to do.  And while I wouldn't have =
a problem with your using multipart/report underneath a multipart/mixed =
for this purpose, I have to wonder whether multipart/report is what you =
need at all.  If you want to use it as a way to send a report about a =
single message, consisting of human-readable explanatory text, an XML =
spam report, and optionally the original message - it's probably a good =
fit and maybe better than defining another type for that purpose.  But =
if that's not what you want to do, you're probably better off defining a =
new type for it.

Keith


--Apple-Mail-39--108360690
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>[NB: top posting is evil.]</div><div><br><blockquote =
type=3D"cite"><div>I'm doing some work with the OMA in the area of spam =
reporting.&nbsp; They have developed an XML message format for reporting =
spam from a mobile handset.&nbsp; Because SMS and MMS (and even IM) have =
different structure than email, they went with something more extensible =
than what we currently do with DSNs.&nbsp; I'm helping that group try to =
converge with what we do in the email world, especially with what the =
MARF working group is producing (e.g., ARF, specified by =
recently-published RFC5965).&nbsp; The first thing is to register the =
MIME type they've created, and so I've crafted a template for =
that.<br><br>The next thing we'd like to achieve is to be able to =
specify multiple spam reports in a single message, regardless of =
transport (they currently use HTTP POST, but there's no reason SMTP =
couldn't be used).&nbsp; The most obvious thing to do would be to use a =
multipart/mixed MIME message, and then include their MIME type in each =
of "n" parts.&nbsp; However, this is different than what was done with =
ARF, which used multipart/report.&nbsp; The advantage to using =
multipart/report, which stipulates that it must be the outermost MIME =
type, is that you know right away that you're processing a report rather =
than having to parse part way into the MIME tree to figure that =
out.&nbsp; (According to Tony Hansen, that's why this rule was put in =
place.)&nbsp; But although multipart/report is the most obvious =
construct for doing this, it doesn't lend itself to multi-report =
messages.&nbsp; So to get these to converge, we have to be a little =
creative or be very creative (in the "create a lot of documents" =
sense).<br></div></blockquote><div><br></div>My vague recollection is =
that multipart/report was constrained to be the top-level MIME type =
mostly to ease the burden on mail gateways that would have wanted to =
automatically map between DSN and another kind of (non)delivery report. =
&nbsp;&nbsp;</div><div><br></div><div>The requirement that it be the =
outermost MIME type might be a bit misstated. &nbsp; I don't think =
anyone intended that you shouldn't be able to forward a DSN as an =
attachment to another message. &nbsp;But there's a subtle but important =
semantic difference between sending a multipart/report at the top level =
of a message and sending a multipart/report as a body part within some =
other multipart or message type. &nbsp;In the first case, the mail =
system is sending a report in response to a specific delivery attempt; =
in the second, a sender is just sending an attachment to a recipient and =
there's no reason that the mail system should care what that attachment =
is. &nbsp; It might be reasonable, say, for a user agent or message =
submission agent of some kind (could be traditional, fax, or voice) to =
use received multipart/report messages to keep track of whether a sent =
message were delivered or whether delivery failed; but it would not be =
reasonable for that same user agent or message submission agent to look =
past the top level of received messages to see if they happen to contain =
a multipart/report.</div><div><br></div><div>(In a very ideal world, =
reporting should have been purely an SMTP function... we're mixing =
layers by sending reports in ordinary email messages. &nbsp;But SMTP has =
worked that way for ~30 years; RFC 1891 <i>et seq</i> just tried to =
standardize the format.)</div><div><br></div><div>So my top-level =
response would be that multipart/report as a top-level type is =
appropriate when (and only when) the mail system is issuing a report in =
response to a delivery attempt. &nbsp; I don't see anything inherently =
wrong with shipping multipart/reports around as children of a =
multipart/mixed, say, but when you do that, it no longer means that the =
mail system is sending a report in response to a delivery =
attempt.</div><div><br></div><div>I'm not sure I understand in what =
context you propose to use multipart/report for spam reporting. &nbsp;It =
seems obvious that if the mail system is issuing a spam report to an =
envelope sender ("we refuse to deliver this; we think it's spam"), that =
a top-level multipart/report would be appropriate, but my guess is that =
this is not the intended use. &nbsp; If you're using multipart/report =
for other purposes, e.g. to transmit a batch of spam reports from one =
MSP to another, I don't see any reason why it should be the top-level =
type, and I'd actually suggest that making it the top-level type would =
be inappropriate. &nbsp;A multipart/mixed at the top level with =
multipart/reports body parts seems much more appropriate. =
&nbsp;</div><div><br></div><div>Note also that multipart/report was =
designed to report potentially multiple delivery attempts - but for a =
single message. &nbsp;It seems inappropriate to try to use a single =
multipart/report to report information about multiple =
messages.&nbsp;</div><div><br></div><div>Bottom line: I doubt that using =
multipart/report as a top-level type is appropriate for what you seem to =
want to do. &nbsp;And while I wouldn't have a problem with your using =
multipart/report underneath a multipart/mixed for this purpose, I have =
to wonder whether multipart/report is what you need at all. &nbsp;If you =
want to use it as a way to send a report about a single message, =
consisting of human-readable explanatory text, an XML spam report, and =
optionally the original message - it's probably a good fit and maybe =
better than defining another type for that purpose. &nbsp;But if that's =
not what you want to do, you're probably better off defining a new type =
for =
it.</div><div><br></div><div>Keith</div><div><br></div></body></html>=

--Apple-Mail-39--108360690--

From Claudio.Allocchio@garr.it  Fri Sep 24 00:33:02 2010
Return-Path: <Claudio.Allocchio@garr.it>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0AAFE3A6848 for <apps-discuss@core3.amsl.com>; Fri, 24 Sep 2010 00:33:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.255
X-Spam-Level: 
X-Spam-Status: No, score=-1.255 tagged_above=-999 required=5 tests=[AWL=1.344,  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 XMm-VORH-H4g for <apps-discuss@core3.amsl.com>; Fri, 24 Sep 2010 00:33:00 -0700 (PDT)
Received: from cyrus.dir.garr.it (cyrus.dir.garr.it [IPv6:2001:760:0:158::29]) by core3.amsl.com (Postfix) with ESMTP id 820CF3A69CD for <apps-discuss@ietf.org>; Fri, 24 Sep 2010 00:32:59 -0700 (PDT)
Received: from mac-allocchio3.elettra.trieste.it (mac-allocchio3.elettra.trieste.it [140.105.2.18]) (authenticated bits=0) by cyrus.dir.garr.it (8.14.4/8.14.4) with ESMTP id o8O7XL19078364 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 24 Sep 2010 09:33:22 +0200 (CEST)
X-DomainKeys: Sendmail DomainKeys Filter v1.0.2 cyrus.dir.garr.it o8O7XL19078364
DomainKey-Signature: a=rsa-sha1; s=mail; d=garr.it; c=simple; q=dns; b=UnFfPrB+9Lx9rmyfH+sT/JVqlGLWntDfy44Pv631NrzNmAYlZBpe/oPrKXeUPEP69 sEstet8/wjA+lDXthRoQ2R55WLg0M9cmC+mhwvfJX4hVNqXQ6UEyqGrzxnGxeRA3IO/ z/N+pMLKEUIHMpMEVVQNS2+CPMXe0b37EWkF72w=
Date: Fri, 24 Sep 2010 09:33:18 +0200 (CEST)
From: Claudio Allocchio <Claudio.Allocchio@garr.it>
X-X-Sender: claudio@mac-allocchio3.elettra.trieste.it
To: Keith Moore <moore@network-heretics.com>
In-Reply-To: <F99C7C1F-CA11-49DC-BE4D-F8E4BC065E43@network-heretics.com>
Message-ID: <Pine.OSX.4.64.1009240922500.1959@mac-allocchio3.elettra.trieste.it>
References: <BB012BD379D7B046ABE1472D8093C61C02AFC3C25A@EXCH-C2.corp.cloudmark.com> <F99C7C1F-CA11-49DC-BE4D-F8E4BC065E43@network-heretics.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] multipart/report
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Sep 2010 07:33:02 -0000

Hello all,

> I'm not sure I understand in what context you propose to use 
> multipart/report for spam reporting.  It seems obvious that if the mail 
> system is issuing a spam report to an envelope sender ("we refuse to 
> deliver this; we think it's spam"), that a top-level multipart/report 
> would be appropriate, but my guess is that this is not the intended use. 
> If you're using multipart/report for other purposes, e.g. to transmit a 
> batch of spam reports from one MSP to another, I don't see any reason 
> why it should be the top-level type, and I'd actually suggest that 
> making it the top-level type would be inappropriate.  A multipart/mixed 
> at the top level with multipart/reports body parts seems much more 
> appropriate.

I have an additional concern about the whole concept of sending a report 
stating "we refuse to deliver this; we think it's spam", in whichever 
format (machine or human readable) is could be:

  - it will likely happen in VERY FEW cases (compared to the total number 
of e-mail messages including real spam) that a real, non-spam message is 
mistaken as a spam one, and thus the relivery report is sent to a real 
user which needs to know his e-mail was mistaken by the recipient antispam 
system and hence the sender needs to act somehow.

  - in the great majority of cases the report will be sent becasue it was 
generated by REAM spam messages. But real spam messages have an 
originating (from/sender...) which either:

   - is a real e-mail address of an innocent user, who has nothing to do
     with the spam message itself, and also his/her client and MTA are
     innocent. In this case they will be annoyed by receiving tons of
     reports for a problem where they cannot do any action about. I
     believe this is unacceptable.

   - is a non valid e-mail address. In this other case, the report will
     just generate a useless overload on the MTAs, springing out non
     delivery reports, etc... also this is unacceptable IMHO.

Are we sure we are not just worsening the problems?

For the rest, I fully agree with Keith position.

------------------------------------------------------------------------------ 
Claudio Allocchio G A R R Claudio.Allocchio@garr.it
                         Senior Technical Officer tel: +39 040 3758523 
Italian Academic and G=Claudio; S=Allocchio; fax: +39 040 3758565 Research 
Network P=garr; A=garr; C=it;

            PGP Key: http://www.cert.garr.it/PGP/keys.php3#ca

From cabo@tzi.org  Fri Sep 24 01:52:45 2010
Return-Path: <cabo@tzi.org>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 37D2A3A6AF6; Fri, 24 Sep 2010 01:52:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.173
X-Spam-Level: 
X-Spam-Status: No, score=-106.173 tagged_above=-999 required=5 tests=[AWL=0.076, BAYES_00=-2.599, HELO_EQ_DE=0.35, 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 enrMAuEhkhJH; Fri, 24 Sep 2010 01:52:44 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9:209:3dff:fe00:7136]) by core3.amsl.com (Postfix) with ESMTP id 7775E3A6A72; Fri, 24 Sep 2010 01:52:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.3/8.14.3) with ESMTP id o8O8rBuo024213; Fri, 24 Sep 2010 10:53:11 +0200 (CEST)
Received: from eduroam-0016.wlan.uni-bremen.de (eduroam-0016.wlan.uni-bremen.de [134.102.16.16]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id F1FF3F63; Fri, 24 Sep 2010 10:53:10 +0200 (CEST)
From: Carsten Bormann <cabo@tzi.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Fri, 24 Sep 2010 10:53:10 +0200
To: apps-discuss@ietf.org, iesg@ietf.org, phil@juniper.net, david.partain@ericsson.com, david.kessens@nsn.com
Message-Id: <61F9178C-454D-4862-8695-67115288DA5A@tzi.org>
Mime-Version: 1.0 (Apple Message framework v1081)
X-Mailer: Apple Mail (2.1081)
Subject: [apps-discuss] apps-team review of draft-ietf-netmod-arch
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Sep 2010 08:52:45 -0000

[Resend -- original copy did not show up in mailing list archive, 
but has already been replied to by Phil.]

I have been selected as the Applications Area Review Team reviewer for
draft-ietf-netmod-arch (for background on apps-review, please see
http://www.apps.ietf.org/content/applications-area-review-team).

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

Document: draft-ietf-netmod-arch-09.txt
Reviewer: Carsten Bormann
Review Date: 2010-09-22
IETF Last Call Date: 2010-07-22 (draft-ietf-netmod-arch-07.txt)
IESG Telechat Date: 2010-09-23

SUMMARY: This draft is almost ready for publication as an
Informational RFC.  I believe the technical material is a sound
introduction and roadmap to the standards-track documents, and only a
few minor potential improvements remain.

MAJOR ISSUES:

Section 3.2, which reads like a list of selling points, is somewhat
opaque (e.g., what is the semantics of "text-friendly"?) and contains
some statements that are not supported by the rest of the document.
Where does the list of item headings come from?  (Not from RFC 3535,
e.g. section 5, which would be a natural source.)  A better
introduction might adjust the expectations of the reader to fit what
is there now.  But sentences such as:

      NETCONF and YANG are solid and reliable technologies.

simply are not RFC material (even if my personal opinion does happen
to agree).

MINOR ISSUES:

* Technical

For me, the introduction appears slightly optimistic about the value
of data modeling languages -- "A client knows how to create valid data
for the server, and knows what data will be sent from the server.  A
server knows the rules that govern the data and how it should behave."
Of course, this can only be true within the limits of what the data
modeling language can describe (or more precisely: the limits of what we
can expect modelers to be able to describe through this language).
(And this, BTW, is exactly the most important reason why a data
modeling language benefits from being adapted to the problem domain; a
reason not otherwise given in the introduction.)

The Description for "delete-config" in the table of operations says:
   Delete a portion of a configuration datastore
To me, section 7.4 of RFC 4741 reads as if the operation can be used
to delete an entire configuration datastore.

The XML example in 2.2.3 misses the namespace declaration for the
namespace prefix "vendorx".  [Have all examples been validated?]

Section 2.3.2 mentions RELAX NG in the title and is then silent about
that in the text.  Contrary to the second paragraph, DSDL is a
*family* of schema languages, not a single standard (and
draft-ietf-netmod-dsdl-map-07.txt does address the family, not just
RELAX NG).

* Editorial

The draft is written in a clear and pleasant manner.
Not being a native speaker, I'm not going to try to review for style.
(A couple of editorial suggestions, including typos/grammar fixes,
have been sent directly to the author.)

We dont have a good way to reference the genesis of an IETF activity
in RFCs.  This draft makes two mistakes in handling this difficult problem:
-- it references an expired Internet-Draft by just giving a draft
  name (draft-presuhn-rcdml-03.txt).  There is no really good
  solution to this problem (except turning this document into another
  RFC, which the WG may have decided not to do).
-- it references an ietf@ietf.org email message by giving a URI to a
  random mail archiving site.  This message, if it is as useful for
  this document as it seems to be, should be either cited through its
  ietf.org URI
  (http://www.ietf.org/mail-archive/web/ietf/current/msg51644.html)
  or, preferably (if the message author concurs), it should instead
  be replicated in an annex.

Is the intention to publish this document in a cluster with the
referenced documents:
-- [RFCYANG] draft-ietf-netmod-yang-13,
-- [RFCYANGDSDL] draft-ietf-netmod-dsdl-map-06,
-- [RFCYANGTYPES] draft-ietf-netmod-yang-types-09.txt, and
-- [RFCYANGUSAGE] draft-ietf-netmod-yang-usage-10.txt?
If not, the reference labels should probably not be called "RFCXXX".

Apparently due to Lars Eggert's quite reasonable ballot comment, the
Introduction is no longer called Introduction (this upsets ID-Nits and
maybe later the RFC editor).

Section 1: "This brings NETCONF to a point where is can be used to
develop standards within the IETF." -- I assume this statement is
about data model standards?  Or what kind of standard?

Section 3.3.3.2 entraps itself by first using "over the wire" and then
having to add a strange retraction that in fact the wire will only see
encrypted material.  But the point here is not the wire, but the fact
that NETCONF implementations can "ascertain whether a specific NETCONF
payload is obeying the rules".  Strike the "over the wire".

* Relevant ID-nits comments

 Miscellaneous warnings:
 ----------------------------------------------------------------------------

 -- The document has a disclaimer for pre-RFC5378 work, but was first
    submitted on or after 10 November 2008.  Does it really need the
    disclaimer?

 Checking references for intended status: Informational
 ----------------------------------------------------------------------------

 == Outdated reference: A later version (-07) exists of
    draft-ietf-netmod-dsdl-map-06


From barryleiba.mailing.lists@gmail.com  Fri Sep 24 08:40:44 2010
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 32BD03A6AB7 for <apps-discuss@core3.amsl.com>; Fri, 24 Sep 2010 08:40:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.669
X-Spam-Level: 
X-Spam-Status: No, score=-101.669 tagged_above=-999 required=5 tests=[AWL=0.308, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 wviBFFOH1g9o for <apps-discuss@core3.amsl.com>; Fri, 24 Sep 2010 08:40:43 -0700 (PDT)
Received: from mail-px0-f172.google.com (mail-px0-f172.google.com [209.85.212.172]) by core3.amsl.com (Postfix) with ESMTP id CC1B53A6AB1 for <apps-discuss@ietf.org>; Fri, 24 Sep 2010 08:40:42 -0700 (PDT)
Received: by pxi6 with SMTP id 6so1049998pxi.31 for <apps-discuss@ietf.org>; Fri, 24 Sep 2010 08:41:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=w3uWiWj3vpbpZH4p4bAOlM/QKo/7b4bHtIthUo4PaK4=; b=IBWre0IJ8jmOqVyhy1YDhJuUptQOEOJff96v8u/C9WIvFcJu6v2dMexgUWrpu93JE0 YkgG/pHyOycHiHf0nbPNhMbewM59k/IzjbdFao76m4uCzgriLt4V+5wHjYPmrMRyFsWP e5IMcu6N4gEEHl7DyEzyXolGgi+b2SeQCrFK8=
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:cc:content-type :content-transfer-encoding; b=U7CjfOQDzRM22jdl+TIFhkaJd4ynafsjTxtS1H2oq709Jn3iP/XjYTijYQOSbLLc8z WQphzOtoq+EaV5/El2QGfPPfJcz36php/9KNEMjR9lSyIrZNi+sMtad9f4DQb6MUo3j4 33CIs6vRGHaW4z693Pfr7wbc2dJn6ViEQZEUo=
MIME-Version: 1.0
Received: by 10.143.33.3 with SMTP id l3mr2849444wfj.203.1285342874644; Fri, 24 Sep 2010 08:41:14 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.42.3.75 with HTTP; Fri, 24 Sep 2010 08:41:14 -0700 (PDT)
In-Reply-To: <Pine.OSX.4.64.1009240922500.1959@mac-allocchio3.elettra.trieste.it>
References: <BB012BD379D7B046ABE1472D8093C61C02AFC3C25A@EXCH-C2.corp.cloudmark.com> <F99C7C1F-CA11-49DC-BE4D-F8E4BC065E43@network-heretics.com> <Pine.OSX.4.64.1009240922500.1959@mac-allocchio3.elettra.trieste.it>
Date: Fri, 24 Sep 2010 11:41:14 -0400
X-Google-Sender-Auth: r1BRd8JHMaYe9JZ0uOVOrO5zkEE
Message-ID: <AANLkTi=0QBXoG4K=_G0yqvGiYt0J1krnhW=WNTJziWTO@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Claudio Allocchio <Claudio.Allocchio@garr.it>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Keith Moore <moore@network-heretics.com>, "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] multipart/report
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Sep 2010 15:40:44 -0000

Claudio says...
> =A0- in the great majority of cases the report will be sent becasue it wa=
s
> generated by REAM spam messages. But real spam messages have an originati=
ng
> (from/sender...) which either:
>
> =A0- is a real e-mail address of an innocent user, who has nothing to do
> =A0 =A0with the spam message itself, and also his/her client and MTA are
> =A0 =A0innocent. In this case they will be annoyed by receiving tons of
> =A0 =A0reports for a problem where they cannot do any action about. I
> =A0 =A0believe this is unacceptable.
>
> =A0- is a non valid e-mail address. In this other case, the report will
> =A0 =A0just generate a useless overload on the MTAs, springing out non
> =A0 =A0delivery reports, etc... also this is unacceptable IMHO.
>
> Are we sure we are not just worsening the problems?

I think you misunderstand the point here; perhaps if you read RFC
5965, you'll get the whole picture.  The short version is that these
are not SMTP-level bounces that say "unable to deliver [because I
think it's spam]".  Those, you'd expect would get sent back to the
sending user.

These are reports, triggered either by spam filters or by users, that
will be processed automatically by the sending domain.  The sending
domain MIGHT choose to send some of them back to the sending user, but
that's according to its handling policy.  In practice (this is already
fairly widely deployed), end users are not seeing these for "spam"
they didn't really send.


But Keith brings up an important point that I hadn't thought of, and
that might make us think again about the mechanism here.  As he says,
the intent of multipart/report as the top-level message was exactly to
allow automated processing of these things.  ARF is actually using
that feature as intended, but I now wonder if there might be
unintended consequences, exactly because these reports ARE different
to the usual non-delivery reports.

Do we have good data on how these are being handled by domains that
*don't* play the ARF game?  If my domain helpfully pushes an ARF
report back to your domain, but your domain doesn't know from ARF,
what will it do?  Won't it just treat it as a normal non-delivery
report and try to give it to the (purported) sending user?

Maybe the right thing to do in general is to wrap the multipart/report
in a multipart/mixed, so only ARF-knowing systems will do anything
with it.

Barry

From lear@cisco.com  Fri Sep 24 10:45:53 2010
Return-Path: <lear@cisco.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1D9333A69D6 for <apps-discuss@core3.amsl.com>; Fri, 24 Sep 2010 10:45:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.598
X-Spam-Level: 
X-Spam-Status: No, score=-109.598 tagged_above=-999 required=5 tests=[AWL=1.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 BrsM0vJBaOoH for <apps-discuss@core3.amsl.com>; Fri, 24 Sep 2010 10:45:51 -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 CFB953A695D for <apps-discuss@ietf.org>; Fri, 24 Sep 2010 10:45:50 -0700 (PDT)
Authentication-Results: ams-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAC+BnEyQ/khL/2dsb2JhbACDHJ8mcasQigiSH4MECIFEcwSKOosR
X-IronPort-AV: E=Sophos;i="4.57,231,1283731200"; d="scan'208,217";a="65143702"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-1.cisco.com with ESMTP; 24 Sep 2010 17:46:22 +0000
Received: from ams3-vpn-dhcp8031.cisco.com (ams3-vpn-dhcp8031.cisco.com [10.61.95.94]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id o8OHkLGd023093; Fri, 24 Sep 2010 17:46:21 GMT
Message-ID: <4C9CE3FF.1040600@cisco.com>
Date: Fri, 24 Sep 2010 19:46:39 +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.9) Gecko/20100915 Lightning/1.0b2 Thunderbird/3.1.4
MIME-Version: 1.0
To: Larry Blunk <ljb@merit.edu>
References: <4C8DF1CC.2010306@cisco.com> <4C9CC628.7070006@merit.edu>
In-Reply-To: <4C9CC628.7070006@merit.edu>
X-Enigmail-Version: 1.1.1
Content-Type: multipart/alternative; boundary="------------080704010100070900030802"
Cc: draft-ietf-grow-mrt@tools.ietf.org, "apps-discuss@ietf.org" <apps-discuss@ietf.org>, grow-chairs@tools.ietf.org
Subject: Re: [apps-discuss] Apps Area Review of draft-grow-mrt-13
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Sep 2010 17:45:53 -0000

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

 Hi Larry,

Thanks for taking the time to read the review and to respond.  Please
see below.


>
>>    1. Section 3. There are several 32-bit timestamp values, which
>>       will mean that a wrap will occur in 2038.  For most *protocols*
>>       this is not a problem because one can manage with wrap
>>       conditions.  However, this is a data export format meant for
>>       researchers.  Researchers tend to want to do longitudinal
>>       studies, and as such, it may prove difficult to use
>>       conventional wrapping mechanisms.   (The 32bit value also
>>       varies from the POSIX time_t definition; a nit to be sure, but
>>       an annoying one).
>>
>
>    Would adding text dealing with wrap conditions be sufficient?
> I'm assuming creating new types with 64-bit timestamp values is
> not particularly desired for this document.

Yes, the wrap condition should be addressed.  There are a few ways to
deal with it (just off the top of my head):

    * Use 64 bit values (this way you never have a wrap– or at least
      it's really REALLY someone else's problem ;-)
    * Provide an indication in a *single* 64 bit value – SOMEWHERE – as
      to when the epoch is.
          o That could be in the external wrapping of this data;
          o It could be through some form of extension.
          o A protocol revision (my least favorite preference).

>
>>    1. Sections 5.2 and 5.3.  There are  two table dump mechanisms
>>       (TABLE_DUMP and TABLE_DUMP_V2) defined.  This  complicates
>>       implementations without any justification.  Very limited
>>       guidance is given as to when one is needed versus the other. 
>>       The authors are advised to strongly consider deprecating
>>       TABLE_DUMP in favor of TABLE_DUMP_V2, or in the alternative,
>>       providing much clearer guidance as to when one should be used
>>       by an exporter.  This problem replays itself throughout the
>>       document in other circumstances (c.f.., BGP4MP_MESSAGE &
>>       BGP4MP_MESSAGE_AS4).
>>
>
>    I think it's reasonable to deprecate the TABLE_DUMP type.
> Although there is quite a bit of data archived with this type,
> I believe that both RIPE and Routeviews have now moved to
> archiving table dumps in the TABLE_DUMP_V2 type.    BGP4MP_MESSAGE
> is still actively used and BGP4MP_MESSAGE_AS4 is only
> used when 4 byte AS numbers are present in the path.   I can
> add some text to clarify this.

I could easily see the argument that once this stuff is out there, it's
out there and you will forever have to parse it.  On the other hand, it
may make sense for someone to simply convert data once and simplify the
parsing later.  I can't really say.  I would recommend a "MUST
NOT"/"MUST" combination to at least begin the process.

>
>>    1. In Section 5.4.1 & 5.4.2 it appears that IANA-specified values
>>       are listed, and are as such limited.  This seems unnecessarily
>>       restrictive, and would force updates of this document when work
>>       is done on BGP.  That might prove necessary anyway becasue
>>       there may be insufficient length information to ignore a single
>>       table entry.
>>
>
>    I received separate feedback from IANA.  I'm still in the process of
> reviewing their comments.
>
>>    1. The TABLE_DUMP_V2 subtypes are not sufficiently specified.  A
>>       good example of how to specify something sufficiently is the
>>       MRT header, where all fields are defined and explained.  For
>>       instance, in the case of TABLE_DUMP*, is a single entry encoded
>>       with format specified in Figures 3-5?  the use of records
>>       versus messages isn't clear.  In part this is due to
>>       inconsistent or poorly defined use of terminology (record
>>       versus message) A diagram or example should be included in the
>>       text that says:
>>
>>>    The MRT records which follow the PEER_INDEX_TABLE MRT record contain
>>>    the RIB entries and include a header which specifies a sequence
>>>    number, NLRI, and a count of the number of RIB entries which follow.
>>>     
>             Understood, I'll make the text consistent and add an example.
>
>>    6. There is not a single example in the document.  This further
>>       hinders implementation of an already unclear specification.
>>
>
>         Agreed, I will add some additional examples.
>
>>   6.
>>
>>
>>
>> Minor issues:
>>
>>    7. Section 4.  There seems to be a desired to deprecate START and
>>       I_AM_DEAD from the outset.  While I can easily envision uses
>>       for this information, and for archival purposes, it seems
>>       useful to indicate start and end collection times (e.g., it may
>>       be useful to know when someone thought they were collecting
>>       routing updates but had in fact none), perhaps a bit more
>>       discussion and guidance should be given to implementors.
>>
>
>         I don't believe there are any implementations when generate the
> START and I_AM_DEAD messages.  While I thought there might be some
> use for them, I am inclined to move them to the deprecated Appendix
> as well.

Ok.  FWIW - you could use this sort of mechanism to deal with your epoch
problem at some point in the future.
>
>>    7. The document really should have a glossary of terms.
>>
>
>   Agree.
>
>>
>> Nits:
>>
>>    9. NLRI is not defined.
>>
>
>    This could go in the glossary perhaps?
>
>>
>> Other (not within Apps charter):
>>
>>   10. Section 8: Security Considerations do not describe data privacy
>>       concerns (consider the case where information being exported
>>       might indicate connectivity of specific individuals or systems,
>>       as could be possible with IGP information).  A fuller review is
>>       recommended.
>>
>
>     I have received additional feedback from the security directorate
> which
> also mentions the privacy issues.   I will add text to the document
> reflecting
> these concerns.
>
>
>  -Larry Blunk
>

Again, thanks for taking into account this review.  I hope it has helped
improve the work.

Eliot

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#ffffff" text="#000000">
    Hi Larry,<br>
    <br>
    Thanks for taking the time to read the review and to respond. 
    Please see below.<br>
    <br>
    <br>
    <blockquote cite="mid:4C9CC628.7070006@merit.edu" type="cite">
      <br>
      <blockquote cite="mid:4C8DF1CC.2010306@cisco.com" type="cite">
        <ol>
          <li>Section 3. There are several 32-bit timestamp values,
            which
            will mean that a wrap will occur in 2038.  For most <b>protocols</b>
            this is not a problem because one can manage with wrap
            conditions. 
            However, this is a data export format meant for
            researchers. 
            Researchers tend to want to do longitudinal studies, and as
            such, it
            may prove difficult to use conventional wrapping
            mechanisms.   (The
            32bit value also varies from the POSIX time_t definition; a
            nit to be
            sure, but an annoying one).</li>
        </ol>
      </blockquote>
      <br>
         Would adding text dealing with wrap conditions be sufficient?<br>
      I'm assuming creating new types with 64-bit timestamp values is<br>
      not particularly desired for this document.<br>
    </blockquote>
    <br>
    Yes, the wrap condition should be addressed.  There are a few ways
    to deal with it (just off the top of my head):<br>
    <ul>
      <li>Use 64 bit values (this way you never have a wrap– or at least
        it's really REALLY someone else's problem ;-)</li>
      <li>Provide an indication in a *single* 64 bit value – SOMEWHERE –
        as to when the epoch is.</li>
      <ul>
        <li>That could be in the external wrapping of this data;</li>
        <li>It could be through some form of extension.</li>
        <li>A protocol revision (my least favorite preference).<br>
        </li>
      </ul>
    </ul>
    <blockquote cite="mid:4C9CC628.7070006@merit.edu" type="cite">
      <br>
      <blockquote cite="mid:4C8DF1CC.2010306@cisco.com" type="cite">
        <ol>
          <li>Sections 5.2 and 5.3.  There are  two table dump
            mechanisms
            (TABLE_DUMP and TABLE_DUMP_V2) defined.  This  complicates
            implementations without any justification.  Very limited
            guidance is
            given as to when one is needed versus the other.  The
            authors are
            advised to strongly consider deprecating TABLE_DUMP in favor
            of
            TABLE_DUMP_V2, or in the alternative, providing much clearer
            guidance
            as to when one should be used by an exporter.  This problem
            replays
            itself throughout the document in other circumstances
            (c.f..,
            BGP4MP_MESSAGE &amp; BGP4MP_MESSAGE_AS4).</li>
        </ol>
      </blockquote>
      <br>
         I think it's reasonable to deprecate the TABLE_DUMP type.<br>
      Although there is quite a bit of data archived with this type,<br>
      I believe that both RIPE and Routeviews have now moved to<br>
      archiving table dumps in the TABLE_DUMP_V2 type.    BGP4MP_MESSAGE<br>
      is still actively used and BGP4MP_MESSAGE_AS4 is only<br>
      used when 4 byte AS numbers are present in the path.   I can<br>
      add some text to clarify this.<br>
    </blockquote>
    <br>
    I could easily see the argument that once this stuff is out there,
    it's out there and you will forever have to parse it.  On the other
    hand, it may make sense for someone to simply convert data once and
    simplify the parsing later.  I can't really say.  I would recommend
    a "MUST NOT"/"MUST" combination to at least begin the process.<br>
    <br>
    <blockquote cite="mid:4C9CC628.7070006@merit.edu" type="cite">
      <br>
      <blockquote cite="mid:4C8DF1CC.2010306@cisco.com" type="cite">
        <ol>
          <li>In Section 5.4.1 &amp; 5.4.2 it appears that
            IANA-specified
            values are listed, and are as such limited.  This seems
            unnecessarily
            restrictive, and would force updates of this document when
            work is done
            on BGP.  That might prove necessary anyway becasue there may
            be
            insufficient length information to ignore a single table
            entry.</li>
        </ol>
      </blockquote>
      <br>
         I received separate feedback from IANA.  I'm still in the
      process of<br>
      reviewing their comments.<br>
      <br>
      <blockquote cite="mid:4C8DF1CC.2010306@cisco.com" type="cite">
        <ol>
          <li>The TABLE_DUMP_V2 subtypes are not sufficiently
            specified.  A
            good example of how to specify something sufficiently is the
            MRT
            header, where all fields are defined and explained.  For
            instance, in
            the case of TABLE_DUMP*, is a single entry encoded with
            format
            specified in Figures 3-5?  the use of records versus
            messages isn't
            clear.  In part this is due to inconsistent or poorly
            defined use of
            terminology (record versus message) A diagram or example
            should be
            included in the text that says:</li>
        </ol>
        <blockquote type="cite">
          <pre class="newpage">   The MRT records which follow the PEER_INDEX_TABLE MRT record contain
   the RIB entries and include a header which specifies a sequence
   number, NLRI, and a count of the number of RIB entries which follow.
    </pre>
        </blockquote>
      </blockquote>
                  Understood, I'll make the text consistent and add an
      example.<br>
      <br>
      <blockquote cite="mid:4C8DF1CC.2010306@cisco.com" type="cite">
        <blockquote type="cite"> </blockquote>
        <ol start="6">
          <li>There is not a single example in the document.  This
            further
            hinders implementation of an already unclear specification.<br>
          </li>
        </ol>
      </blockquote>
      <br>
              Agreed, I will add some additional examples.<br>
      <br>
      <blockquote cite="mid:4C8DF1CC.2010306@cisco.com" type="cite">
        <ol start="6">
          <li> <br>
          </li>
        </ol>
        <br>
        Minor issues:<br>
        <br>
        <ol start="7">
          <li>Section 4.  There seems to be a desired to deprecate START
            and
            I_AM_DEAD from the outset.  While I can easily envision uses
            for this
            information, and for archival purposes, it seems useful to
            indicate
            start and end collection times (e.g., it may be useful to
            know when
            someone thought they were collecting routing updates but had
            in fact
            none), perhaps a bit more discussion and guidance should be
            given to
            implementors.</li>
        </ol>
      </blockquote>
      <br>
              I don't believe there are any implementations when
      generate the<br>
      START and I_AM_DEAD messages.  While I thought there might be some<br>
      use for them, I am inclined to move them to the deprecated
      Appendix<br>
      as well.<br>
    </blockquote>
    <br>
    Ok.  FWIW - you could use this sort of mechanism to deal with your
    epoch problem at some point in the future.<br>
    <blockquote cite="mid:4C9CC628.7070006@merit.edu" type="cite">
      <br>
      <blockquote cite="mid:4C8DF1CC.2010306@cisco.com" type="cite">
        <ol start="7">
          <li>The document really should have a glossary of terms.</li>
        </ol>
      </blockquote>
      <br>
        Agree.<br>
      <br>
      <blockquote cite="mid:4C8DF1CC.2010306@cisco.com" type="cite">
        <ol start="7">
        </ol>
        <br>
        Nits:<br>
        <ol start="9">
          <li>NLRI is not defined.</li>
        </ol>
      </blockquote>
      <br>
         This could go in the glossary perhaps?<br>
      <br>
      <blockquote cite="mid:4C8DF1CC.2010306@cisco.com" type="cite">
        <ol start="9">
        </ol>
        <br>
        Other (not within Apps charter):<br>
        <ol start="10">
          <li>Section 8: Security Considerations do not describe data
            privacy
            concerns (consider the case where information being exported
            might
            indicate connectivity of specific individuals or systems, as
            could be
            possible with IGP information).  A fuller review is
            recommended.<br>
          </li>
        </ol>
      </blockquote>
      <br>
          I have received additional feedback from the security
      directorate
      which<br>
      also mentions the privacy issues.   I will add text to the
      document
      reflecting<br>
      these concerns.<br>
      <br>
      <br>
       -Larry Blunk<br>
      <br>
    </blockquote>
    <br>
    Again, thanks for taking into account this review.  I hope it has
    helped improve the work.<br>
    <br>
    Eliot<br>
  </body>
</html>

--------------080704010100070900030802--

From alexey.melnikov@isode.com  Fri Sep 24 12:20:04 2010
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3474A3A67A3 for <apps-discuss@core3.amsl.com>; Fri, 24 Sep 2010 12:20:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.582
X-Spam-Level: 
X-Spam-Status: No, score=-101.582 tagged_above=-999 required=5 tests=[AWL=-1.397, BAYES_40=-0.185, 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 AMX0xnaEqARC for <apps-discuss@core3.amsl.com>; Fri, 24 Sep 2010 12:20:03 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id 7A1CC3A6783 for <Apps-Discuss@ietf.org>; Fri, 24 Sep 2010 12:20:01 -0700 (PDT)
Received: from [172.16.2.163] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <TJz6AABchrct@rufus.isode.com>; Fri, 24 Sep 2010 20:20:33 +0100
Message-ID: <4C9CF9B8.50203@isode.com>
Date: Fri, 24 Sep 2010 20:19:20 +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: Apps-Discuss@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [apps-discuss] Not running for another Applications Area Director term
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Sep 2010 19:20:04 -0000

Greetings,
As people started to ask me privately about this, I think I should 
publicly state that after much thought I decided not to run for another 
term as an Applications Area Director. So if you were volunteered for 
the job, but haven't accepted it, please think hard before declining it. 
If you already declined, maybe you should reconsider.

If you want to know more about pros. and cons., feel free to contact me 
and I will be happy to talk about that. I have to say I had terrific 
time as an Application AD and I will enjoy the rest of my term.

If you want to read more about my reasons and what else I am up to, look 
here: <http://thehemul.blogspot.com/2010/09/i-shall-not-return.html>

Best Regards,
Alexey

-- 
IETF Application Area Director, <http://www.ietf.org/iesg/members.html>
Internet Messaging Team Lead, <http://www.isode.com>
JID: same as my email address
Twitter: http://twitter.com/aamelnikov



From mnot@mnot.net  Fri Sep 24 18:52:03 2010
Return-Path: <mnot@mnot.net>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A7C693A6835; Fri, 24 Sep 2010 18:52:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.079
X-Spam-Level: 
X-Spam-Status: No, score=-105.079 tagged_above=-999 required=5 tests=[AWL=-2.480, 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 f9WHJ1KmC-Ug; Fri, 24 Sep 2010 18:52:02 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by core3.amsl.com (Postfix) with ESMTP id C3D8A3A6783; Fri, 24 Sep 2010 18:52:01 -0700 (PDT)
Received: from chancetrain-lm.mnot.net (unknown [118.209.143.94]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id ACF4F509DC; Fri, 24 Sep 2010 21:52:27 -0400 (EDT)
From: Mark Nottingham <mnot@mnot.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Sat, 25 Sep 2010 11:52:23 +1000
Message-Id: <80FDD367-70D7-4EA1-8A03-A560F43024F5@mnot.net>
To: draft-merrick-jms-uri@tools.ietf.org
Mime-Version: 1.0 (Apple Message framework v1081)
X-Mailer: Apple Mail (2.1081)
Cc: IESG IESG <iesg@ietf.org>, apps-discuss@ietf.org
Subject: [apps-discuss] APP Area Review of draft-merrick-jms-uri-09
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Sep 2010 01:52:04 -0000

Hello,

I have been selected as the Applications Area Review Team reviewer for =
this draft (for background on apps-review, please see =
<http://www.apps.ietf.org/content/applications-area-review-team>).

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

Document: draft-merrick-jms-uri-09
Reviewer: Mark Nottingham
Review Date: 2010-09-25

Summary: This draft is not ready for publication as an Informational RFC =
and should be revised before publication.

Major Issues:=20

1. Section 3: The proposed syntax reuses "path-rootless" from RFC3986. =
However, it does not match the "absolute-URI" production from the same =
RFC, because of the introduction of the extra "jms-variant" rule. This =
means that URI parsing implementations may not be able to recognise the =
hierarchical components and expose them meaningfully, and is in conflict =
section 2.2 of RFC4395. That specification requires that such issues be =
documented in provisional registrations.

2. The proposed URI scheme does allow resources to be located, but does =
not define a protocol to do so; rather it defines it in terms of an API =
(JMS). Thus, there is no wire-level protocol that can be used to build =
an interoperable implementation; rather, one needs to rely on a vendor's =
mapping of the API to a wire-level protocol (an issue which Section 1 =
attempts to address).=20

It doesn't necessarily follow that the registration is invalid as a =
result, but allowing a URI scheme to specify an API rather than a =
protocol for purposes of interoperability is counter to widely-held =
beliefs in the IETF, and arguably also conflicts with the spirit of the =
Architecture of the World Wide Web =
<http://www.w3.org/TR/webarch/#dereference-uri>. Besides effectively =
limiting the use of this URI scheme to one language (Java), it also =
means that interoperability will be difficult to achieve between =
implementations.

While it may be appropriate to register widely-used schemes in order to =
document current use, but that doesn't appear to be the case here (as =
evident in the abstract). As such, the document should more prominently =
warn about interoperability issues inherent in this approach.

3. It's not clear whether this registration reflects the position of all =
potential users. In particular, the specification of JMS and associated =
APIs is maintained by the Java Community Process <http://jcp.org/>, but =
this request does not state what its relation to the JCP is. An informal =
liaison might clarify this issue.

Minor Issues:=20

1. The proposed scheme specifies an extensibility point, "jms-variant", =
but does not specify a registry or other means of disambiguating =
variants and avoiding collisions.=20

Regards,


--
Mark Nottingham     http://www.mnot.net/


From ljb@merit.edu  Fri Sep 24 08:38:51 2010
Return-Path: <ljb@merit.edu>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EBA4E3A6AB1 for <apps-discuss@core3.amsl.com>; Fri, 24 Sep 2010 08:38:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.965
X-Spam-Level: 
X-Spam-Status: No, score=-1.965 tagged_above=-999 required=5 tests=[AWL=-1.967, BAYES_50=0.001, HTML_MESSAGE=0.001]
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 VER7r8KzeBJG for <apps-discuss@core3.amsl.com>; Fri, 24 Sep 2010 08:38:49 -0700 (PDT)
Received: from thor.merit.edu (thor.merit.edu [198.108.1.14]) by core3.amsl.com (Postfix) with ESMTP id DDFA23A69E2 for <apps-discuss@ietf.org>; Fri, 24 Sep 2010 08:38:48 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EADljnEzGbD6X/2dsb2JhbACDHJ8lcbN5iUKIZYJxgV9zBIo6
X-IronPort-AV: E=Sophos;i="4.57,230,1283745600"; d="scan'208,217";a="40408087"
Received: from ablate.merit.edu ([198.108.62.151]) by thor.merit.edu with ESMTP/TLS/DHE-RSA-CAMELLIA256-SHA; 24 Sep 2010 11:39:21 -0400
Message-ID: <4C9CC628.7070006@merit.edu>
Date: Fri, 24 Sep 2010 11:39:20 -0400
From: Larry Blunk <ljb@merit.edu>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.12) Gecko/20100915 Thunderbird/3.0.8
MIME-Version: 1.0
To: Eliot Lear <lear@cisco.com>
References: <4C8DF1CC.2010306@cisco.com>
In-Reply-To: <4C8DF1CC.2010306@cisco.com>
Content-Type: multipart/alternative; boundary="------------070500000205070204020005"
X-Mailman-Approved-At: Sat, 25 Sep 2010 08:58:24 -0700
Cc: draft-ietf-grow-mrt@tools.ietf.org, "apps-discuss@ietf.org" <apps-discuss@ietf.org>, grow-chairs@tools.ietf.org
Subject: Re: [apps-discuss] Apps Area Review of draft-grow-mrt-13
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Sep 2010 15:38:51 -0000

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

On 09/13/2010 05:41 AM, Eliot Lear wrote:
> I have been selected as the Applications Area Review Team reviewer for 
> this draft (for background on apps-review, please see 
> http://www.apps.ietf.org/content/applications-area-review-team).
>
> Please resolve these comments along with any other Last Call comments 
> you may receive. Please wait for direction from your document shepherd 
> or AD before posting a new version of the draft.
>
> Document: draft-ietf-grow-mrt-13
> Reviewer: Eliot Lear
> Review Date: 13 September 2010
>
> Summary:
>
> This draft is not yet ready for publication, but will require at least 
> a review of the issues mentioned below.
>
> Major Issues:
>
> This specification suffers from two complicating effects:
>
>     * The fact that it already deployed, and hence is attempting to
>       document existing practice; and
>     * there is substantial "feature creep" in an attempt to continue
>       to use the same collector, while extending capabilities.
>
> Consideration should be given to breaking this effort into two: an 
> informational document that explains what is going on today, and a new 
> clean specification for standardization.
>
> This specification could perhaps benefit from review of those who 
> developed IPFIX and PSAMP.  In particular, consistent terminology 
> would be nice.


     Eliot, there is currently some work going on to define an XML
format for archiving BGP routing information.   There is a draft
at http://tools.ietf.org/html/draft-cheng-grow-bgp-xml-00 (although
it is currently expired).    While the GROW WG has yet to adopt this
draft, it seems this would be the likely base of a new clean specification.



>
> Specific issues:
>
>    1. Section 3.  There is no versioning information in the packet
>       header.  This means that format upgrades will require external
>       information to identify their changes.
>

    Unfortunately,  I don't think there is a way around this.   This
is one of the issues that is resolved by the XML work.

>    1. Section 3. There are several 32-bit timestamp values, which will
>       mean that a wrap will occur in 2038.  For most *protocols* this
>       is not a problem because one can manage with wrap conditions. 
>       However, this is a data export format meant for researchers. 
>       Researchers tend to want to do longitudinal studies, and as
>       such, it may prove difficult to use conventional wrapping
>       mechanisms.   (The 32bit value also varies from the POSIX time_t
>       definition; a nit to be sure, but an annoying one).
>

    Would adding text dealing with wrap conditions be sufficient?
I'm assuming creating new types with 64-bit timestamp values is
not particularly desired for this document.

>    1. Sections 5.2 and 5.3.  There are  two table dump mechanisms
>       (TABLE_DUMP and TABLE_DUMP_V2) defined.  This  complicates
>       implementations without any justification.  Very limited
>       guidance is given as to when one is needed versus the other. 
>       The authors are advised to strongly consider deprecating
>       TABLE_DUMP in favor of TABLE_DUMP_V2, or in the alternative,
>       providing much clearer guidance as to when one should be used by
>       an exporter.  This problem replays itself throughout the
>       document in other circumstances (c.f.., BGP4MP_MESSAGE &
>       BGP4MP_MESSAGE_AS4).
>

    I think it's reasonable to deprecate the TABLE_DUMP type.
Although there is quite a bit of data archived with this type,
I believe that both RIPE and Routeviews have now moved to
archiving table dumps in the TABLE_DUMP_V2 type.    BGP4MP_MESSAGE
is still actively used and BGP4MP_MESSAGE_AS4 is only
used when 4 byte AS numbers are present in the path.   I can
add some text to clarify this.

>    1. In Section 5.4.1 & 5.4.2 it appears that IANA-specified values
>       are listed, and are as such limited.  This seems unnecessarily
>       restrictive, and would force updates of this document when work
>       is done on BGP.  That might prove necessary anyway becasue there
>       may be insufficient length information to ignore a single table
>       entry.
>

    I received separate feedback from IANA.  I'm still in the process of
reviewing their comments.

>    1. The TABLE_DUMP_V2 subtypes are not sufficiently specified.  A
>       good example of how to specify something sufficiently is the MRT
>       header, where all fields are defined and explained.  For
>       instance, in the case of TABLE_DUMP*, is a single entry encoded
>       with format specified in Figures 3-5?  the use of records versus
>       messages isn't clear.  In part this is due to inconsistent or
>       poorly defined use of terminology (record versus message) A
>       diagram or example should be included in the text that says:
>
>>     The MRT records which follow the PEER_INDEX_TABLE MRT record contain
>>     the RIB entries and include a header which specifies a sequence
>>     number, NLRI, and a count of the number of RIB entries which follow.
>>      
             Understood, I'll make the text consistent and add an example.

>    6. There is not a single example in the document.  This further
>       hinders implementation of an already unclear specification.
>

         Agreed, I will add some additional examples.

>   6.
>
>
>
> Minor issues:
>
>    7. Section 4.  There seems to be a desired to deprecate START and
>       I_AM_DEAD from the outset.  While I can easily envision uses for
>       this information, and for archival purposes, it seems useful to
>       indicate start and end collection times (e.g., it may be useful
>       to know when someone thought they were collecting routing
>       updates but had in fact none), perhaps a bit more discussion and
>       guidance should be given to implementors.
>

         I don't believe there are any implementations when generate the
START and I_AM_DEAD messages.  While I thought there might be some
use for them, I am inclined to move them to the deprecated Appendix
as well.

>    7. The document really should have a glossary of terms.
>

   Agree.

>
> Nits:
>
>    9. NLRI is not defined.
>

    This could go in the glossary perhaps?

>
> Other (not within Apps charter):
>
>   10. Section 8: Security Considerations do not describe data privacy
>       concerns (consider the case where information being exported
>       might indicate connectivity of specific individuals or systems,
>       as could be possible with IGP information).  A fuller review is
>       recommended.
>

     I have received additional feedback from the security directorate which
also mentions the privacy issues.   I will add text to the document 
reflecting
these concerns.


  -Larry Blunk



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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  <title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
On 09/13/2010 05:41 AM, Eliot Lear wrote:
<blockquote cite="mid:4C8DF1CC.2010306@cisco.com" type="cite">
  <meta http-equiv="content-type" content="text/html; charset=UTF-8">
I have been selected as the Applications Area Review Team reviewer for
this draft (for background on apps-review, please see <a
 moz-do-not-send="true" class="moz-txt-link-freetext"
 href="http://www.apps.ietf.org/content/applications-area-review-team">http://www.apps.ietf.org/content/applications-area-review-team</a>).<br>
  <br>
Please resolve these comments along with any other Last Call comments
you may receive. Please wait for direction from your document shepherd
or AD before posting a new version of the draft.<br>
  <br>
Document: draft-ietf-grow-mrt-13<br>
Reviewer: Eliot Lear<br>
Review Date: 13 September 2010<br>
  <br>
Summary:<br>
  <br>
This draft is not yet ready for publication, but will require at least
a review of the issues mentioned below.<br>
  <br>
Major Issues:<br>
  <br>
This specification suffers from two complicating effects:<br>
  <ul>
    <li>The fact that it already deployed, and hence is attempting to
document existing practice; and<br>
    </li>
    <li>there is substantial "feature creep" in an attempt to continue
to use the same collector, while extending capabilities.</li>
  </ul>
Consideration should be given to breaking this effort into two: an
informational document that explains what is going on today, and a new
clean specification for standardization.<br>
  <br>
This specification could perhaps benefit from review of those who
developed IPFIX and PSAMP.  In particular, consistent terminology would
be nice.<br>
</blockquote>
<br>
<br>
    Eliot, there is currently some work going on to define an XML<br>
format for archiving BGP routing information.   There is a draft<br>
at <a class="moz-txt-link-freetext" href="http://tools.ietf.org/html/draft-cheng-grow-bgp-xml-00">http://tools.ietf.org/html/draft-cheng-grow-bgp-xml-00</a> (although<br>
it is currently expired).    While the GROW WG has yet to adopt this<br>
draft, it seems this would be the likely base of a new clean
specification.<br>
<br>
<br>
<br>
<blockquote cite="mid:4C8DF1CC.2010306@cisco.com" type="cite"> <br>
Specific issues:<br>
  <br>
  <ol>
    <li>Section 3.  There is no versioning information in the packet
header.  This means that format upgrades will require external
information to identify their changes.</li>
  </ol>
</blockquote>
<br>
   Unfortunately,  I don't think there is a way around this.   This<br>
is one of the issues that is resolved by the XML work.<br>
<br>
<blockquote cite="mid:4C8DF1CC.2010306@cisco.com" type="cite">
  <ol>
    <li>Section 3. There are several 32-bit timestamp values, which
will mean that a wrap will occur in 2038.  For most <b>protocols</b>
this is not a problem because one can manage with wrap conditions. 
However, this is a data export format meant for researchers. 
Researchers tend to want to do longitudinal studies, and as such, it
may prove difficult to use conventional wrapping mechanisms.   (The
32bit value also varies from the POSIX time_t definition; a nit to be
sure, but an annoying one).</li>
  </ol>
</blockquote>
<br>
   Would adding text dealing with wrap conditions be sufficient?<br>
I'm assuming creating new types with 64-bit timestamp values is<br>
not particularly desired for this document.<br>
<br>
<blockquote cite="mid:4C8DF1CC.2010306@cisco.com" type="cite">
  <ol>
    <li>Sections 5.2 and 5.3.  There are  two table dump mechanisms
(TABLE_DUMP and TABLE_DUMP_V2) defined.  This  complicates
implementations without any justification.  Very limited guidance is
given as to when one is needed versus the other.  The authors are
advised to strongly consider deprecating TABLE_DUMP in favor of
TABLE_DUMP_V2, or in the alternative, providing much clearer guidance
as to when one should be used by an exporter.  This problem replays
itself throughout the document in other circumstances (c.f..,
BGP4MP_MESSAGE &amp; BGP4MP_MESSAGE_AS4).</li>
  </ol>
</blockquote>
<br>
   I think it's reasonable to deprecate the TABLE_DUMP type.<br>
Although there is quite a bit of data archived with this type,<br>
I believe that both RIPE and Routeviews have now moved to<br>
archiving table dumps in the TABLE_DUMP_V2 type.    BGP4MP_MESSAGE<br>
is still actively used and BGP4MP_MESSAGE_AS4 is only<br>
used when 4 byte AS numbers are present in the path.   I can<br>
add some text to clarify this.<br>
<br>
<blockquote cite="mid:4C8DF1CC.2010306@cisco.com" type="cite">
  <ol>
    <li>In Section 5.4.1 &amp; 5.4.2 it appears that IANA-specified
values are listed, and are as such limited.  This seems unnecessarily
restrictive, and would force updates of this document when work is done
on BGP.  That might prove necessary anyway becasue there may be
insufficient length information to ignore a single table entry.</li>
  </ol>
</blockquote>
<br>
   I received separate feedback from IANA.  I'm still in the process of<br>
reviewing their comments.<br>
<br>
<blockquote cite="mid:4C8DF1CC.2010306@cisco.com" type="cite">
  <ol>
    <li>The TABLE_DUMP_V2 subtypes are not sufficiently specified.  A
good example of how to specify something sufficiently is the MRT
header, where all fields are defined and explained.  For instance, in
the case of TABLE_DUMP*, is a single entry encoded with format
specified in Figures 3-5?  the use of records versus messages isn't
clear.  In part this is due to inconsistent or poorly defined use of
terminology (record versus message) A diagram or example should be
included in the text that says:</li>
  </ol>
  <blockquote type="cite">
    <pre class="newpage">   The MRT records which follow the PEER_INDEX_TABLE MRT record contain
   the RIB entries and include a header which specifies a sequence
   number, NLRI, and a count of the number of RIB entries which follow.
    </pre>
  </blockquote>
</blockquote>
            Understood, I'll make the text consistent and add an
example.<br>
<br>
<blockquote cite="mid:4C8DF1CC.2010306@cisco.com" type="cite">
  <blockquote type="cite"> </blockquote>
  <ol start="6">
    <li>There is not a single example in the document.  This further
hinders implementation of an already unclear specification.<br>
    </li>
  </ol>
</blockquote>
<br>
        Agreed, I will add some additional examples.<br>
<br>
<blockquote cite="mid:4C8DF1CC.2010306@cisco.com" type="cite">
  <ol start="6">
    <li> <br>
    </li>
  </ol>
  <br>
Minor issues:<br>
  <br>
  <ol start="7">
    <li>Section 4.  There seems to be a desired to deprecate START and
I_AM_DEAD from the outset.  While I can easily envision uses for this
information, and for archival purposes, it seems useful to indicate
start and end collection times (e.g., it may be useful to know when
someone thought they were collecting routing updates but had in fact
none), perhaps a bit more discussion and guidance should be given to
implementors.</li>
  </ol>
</blockquote>
<br>
        I don't believe there are any implementations when generate the<br>
START and I_AM_DEAD messages.  While I thought there might be some<br>
use for them, I am inclined to move them to the deprecated Appendix<br>
as well.<br>
<br>
<blockquote cite="mid:4C8DF1CC.2010306@cisco.com" type="cite">
  <ol start="7">
    <li>The document really should have a glossary of terms.</li>
  </ol>
</blockquote>
<br>
  Agree.<br>
<br>
<blockquote cite="mid:4C8DF1CC.2010306@cisco.com" type="cite">
  <ol start="7">
  </ol>
  <br>
Nits:<br>
  <ol start="9">
    <li>NLRI is not defined.</li>
  </ol>
</blockquote>
<br>
   This could go in the glossary perhaps?<br>
<br>
<blockquote cite="mid:4C8DF1CC.2010306@cisco.com" type="cite">
  <ol start="9">
  </ol>
  <br>
Other (not within Apps charter):<br>
  <ol start="10">
    <li>Section 8: Security Considerations do not describe data privacy
concerns (consider the case where information being exported might
indicate connectivity of specific individuals or systems, as could be
possible with IGP information).  A fuller review is recommended.<br>
    </li>
  </ol>
</blockquote>
<br>
    I have received additional feedback from the security directorate
which<br>
also mentions the privacy issues.   I will add text to the document
reflecting<br>
these concerns.<br>
<br>
<br>
 -Larry Blunk<br>
<br>
<br>
</body>
</html>

--------------070500000205070204020005--

From julian.reschke@gmx.de  Mon Sep 27 06:32:14 2010
Return-Path: <julian.reschke@gmx.de>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A18263A6A1A for <apps-discuss@core3.amsl.com>; Mon, 27 Sep 2010 06:32:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.668
X-Spam-Level: 
X-Spam-Status: No, score=-103.668 tagged_above=-999 required=5 tests=[AWL=-3.483, BAYES_40=-0.185, 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 V9pnsNfoFMGp for <apps-discuss@core3.amsl.com>; Mon, 27 Sep 2010 06:32:13 -0700 (PDT)
Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.23]) by core3.amsl.com (Postfix) with SMTP id 030F23A6D1B for <apps-discuss@ietf.org>; Mon, 27 Sep 2010 06:32:08 -0700 (PDT)
Received: (qmail invoked by alias); 27 Sep 2010 13:32:45 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.146]) [217.91.35.233] by mail.gmx.net (mp013) with SMTP; 27 Sep 2010 15:32:45 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX19lG2kOwPJl7x4mlN8aMXdK/ATokZ/YiWyScJIpPT hR860gEYBpagI/
Message-ID: <4CA09CFD.7030405@gmx.de>
Date: Mon, 27 Sep 2010 15:32:45 +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.9) Gecko/20100915 Lightning/1.0b2 Thunderbird/3.1.4
MIME-Version: 1.0
To: IETF Apps Discuss <apps-discuss@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: Henning Schulzrinne <hgs@cs.columbia.edu>
Subject: [apps-discuss] APP Area Review of draft-ietf-ecrit-lost-sync-09
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Sep 2010 13:32:14 -0000

I have been selected as the Applications Area Review Team reviewer for 
this draft (for background on apps-review, please see 
http://www.apps.ietf.org/content/applications-area-review-team).

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

Document: draft-ietf-ecrit-lost-sync-09
Reviewer: Julian Reschke
Review Date: 2010-09-27
IETF Last Call Date: -
IESG Telechat Date: -

Summary: This draft is almost ready for publication as an Experimental 
RFC (*) but has a few issues that should be fixed before publication

(*) The draft doesn't state the intended status, but this is what the WG 
charter says.

Major Issues:

It appears that this protocol essentially uses HTTP POST as a tunnel. As 
this also is used for *retrieval*, the message format re-invents certain 
mechanisms that are already available in HTTP (such as conditional 
requests, and state tokens). I'd like to encourage the Working Group to 
consider making the retrieval requests pure GET requests.

In LoST Sync Relax NG Schema Registration:

This registers a Relax NG schema in a registry for XML Schemas (not in 
general, but the W3C ones). I sympathize with the use of Relax NG over 
XML Schema, but this is not going to work unless we revise RFC 3688 first.


Minor Issues:

The spec doesn't seem to define ESRP and "forest", nor could I find 
those in RFC 5222 (at least no explanations).

The XML example in Figure 2 needs a namespace declaration for the prefix 
"p2".

In the examples, <displayName> sometimes uses leading/trailing 
whitespace. If this WS is supposed to be ignored, it should be stated 
(maybe this is a problem with the base format, though).

It's not clear to me why some examples use an empty <uri> element 
instead of leaving this out. Is this a funny constraint in the base syntax?

In the media type registration:

"Encoding considerations: Uses XML, which can employ 8-bit characters, 
depending on the character encoding used." - this is a bit misleading; 
did you mean to say something like "non-US-ASCII"?

"Security considerations: This content type is designed to carry LoST 
Syncronization protocol payloads." - how is that a security 
consideration? (also note the typo in "Syncronization").


In LoST Synchronization Namespace Registration:

   <meta http-equiv="content-type"
         content="text/html;charset=iso-8859-1"/>

I recommend dropping the meta/@http-equiv: (a) it's not needed, (b) 
it'll be harmful if the file actually gets served in a different 
encoding, such as UTF-16 :-)

Nits:

Section 6: did you consider using the RNC syntax instead?

IANA considerations:

For reviewers it would be easier if each section stated which registry 
is being used (with a ref to the the registration procedure RFC).

In References:

REC-xmldsig-core-20020212: [FirstEdition] obsoleted by 
REC-xmldsig-core-20080610 -- please update.

Note: I did not check all XML examples for well-formedness; I assume the 
document shepherd will do this.

Best regards, Julian

From stpeter@stpeter.im  Mon Sep 27 15:20:56 2010
Return-Path: <stpeter@stpeter.im>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4DE423A6BCF for <apps-discuss@core3.amsl.com>; Mon, 27 Sep 2010 15:20:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.521
X-Spam-Level: 
X-Spam-Status: No, score=-102.521 tagged_above=-999 required=5 tests=[AWL=0.078, 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 5RKLj4Zdubp0 for <apps-discuss@core3.amsl.com>; Mon, 27 Sep 2010 15:20:54 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id EA0853A69B4 for <apps-discuss@ietf.org>; Mon, 27 Sep 2010 15:20:53 -0700 (PDT)
Received: from moveme.cisco.com (72-163-0-129.cisco.com [72.163.0.129]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 37D88400EE for <apps-discuss@ietf.org>; Mon, 27 Sep 2010 16:26:55 -0600 (MDT)
Message-ID: <4CA118E9.2090203@stpeter.im>
Date: Mon, 27 Sep 2010 16:21:29 -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.1.12) Gecko/20100914 Thunderbird/3.0.8
MIME-Version: 1.0
To: "apps-discuss@ietf.org" <apps-discuss@ietf.org>
X-Enigmail-Version: 1.0.1
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: multipart/mixed; boundary="------------030203000909070005070307"
Subject: [apps-discuss] Fwd: I-D Action:draft-hartmann-default-port-for-irc-via-tls-ssl-01.txt
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Sep 2010 22:20:56 -0000

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

I'm not sure if IRC counts as Apps or RAI these days, but I figured this
I-D might be of interest here...


-------- Original Message --------
Subject: I-D Action:draft-hartmann-default-port-for-irc-via-tls-ssl-01.txt
Date: Sun, 26 Sep 2010 17:15:05 -0700 (PDT)
From: Internet-Drafts@ietf.org
Reply-To: internet-drafts@ietf.org
To: i-d-announce@ietf.org

A New Internet-Draft is available from the on-line Internet-Drafts
directories.

	Title           : Default Port for IRC via TLS/SSL
	Author(s)       : R. Hartmann
	Filename        : draft-hartmann-default-port-for-irc-via-tls-ssl-01.txt
	Pages           : 5
	Date            : 2010-09-26

This document describes the established best industry practice of
listening on TCP port 6697 for incoming IRC connections encrypted via
TLS/SSL.

This document does not try to limit the use of lesser-used ports like
7000 and 9999.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-hartmann-default-port-for-irc-via-tls-ssl-01.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.


--------------030203000909070005070307
Content-Type: Message/External-body;
 name="draft-hartmann-default-port-for-irc-via-tls-ssl-01.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="draft-hartmann-default-port-for-irc-via-tls-ssl-01.txt"

Content-Type: text/plain
Content-ID: <2010-09-26171352.I-D@ietf.org>



--------------030203000909070005070307
Content-Type: text/plain;
 name="Attached Message Part"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename="Attached Message Part"

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KSS1ELUFu
bm91bmNlIG1haWxpbmcgbGlzdApJLUQtQW5ub3VuY2VAaWV0Zi5vcmcKaHR0cHM6Ly93d3cu
aWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pLWQtYW5ub3VuY2UKSW50ZXJuZXQtRHJhZnQg
ZGlyZWN0b3JpZXM6IGh0dHA6Ly93d3cuaWV0Zi5vcmcvc2hhZG93Lmh0bWwKb3IgZnRwOi8v
ZnRwLmlldGYub3JnL2lldGYvMXNoYWRvdy1zaXRlcy50eHQKCg==
--------------030203000909070005070307--

From stpeter@stpeter.im  Tue Sep 28 10:31:15 2010
Return-Path: <stpeter@stpeter.im>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EA7543A6E1F for <apps-discuss@core3.amsl.com>; Tue, 28 Sep 2010 10:31:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.526
X-Spam-Level: 
X-Spam-Status: No, score=-102.526 tagged_above=-999 required=5 tests=[AWL=0.073, 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 X6dwxiFDmalS for <apps-discuss@core3.amsl.com>; Tue, 28 Sep 2010 10:30:51 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id 0CA4C3A6E06 for <apps-discuss@ietf.org>; Tue, 28 Sep 2010 10:30:40 -0700 (PDT)
Received: from moveme.cisco.com (72-163-0-129.cisco.com [72.163.0.129]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 2BE14400EE for <apps-discuss@ietf.org>; Tue, 28 Sep 2010 11:36:45 -0600 (MDT)
Message-ID: <4CA22665.1090008@stpeter.im>
Date: Tue, 28 Sep 2010 11:31:17 -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.1.12) Gecko/20100914 Thunderbird/3.0.8
MIME-Version: 1.0
To: "apps-discuss@ietf.org" <apps-discuss@ietf.org>
X-Enigmail-Version: 1.0.1
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: [apps-discuss] Fwd: WG Review: Applications Area Working Group (APPSAWG)
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Sep 2010 17:31:15 -0000

FYI.

-------- Original Message --------
Subject: WG Review: Applications Area Working Group (APPSAWG)
Date: Tue, 28 Sep 2010 10:30:02 -0700 (PDT)
From: IESG Secretary <iesg-secretary@ietf.org>
Reply-To: iesg@ietf.org
To: ietf-announce@ietf.org

A new IETF working group has been proposed in the Applications Area.  The
IESG has not made any determination as yet. The following draft charter
was submitted, and is provided for informational purposes only. Please
send your comments to the IESG mailing list (iesg@ietf.org) by Tuesday,
October 5, 2010.

Applications Area Working Group (APPSAWG)
------------------------------------------
Current Status: Proposed Working Group
Last updated: 2010-09-24

Chair(s): TBD

Applications Area Directors:
 Alexey Melnikov <alexey.melnikov@isode.com>
 Peter Saint-Andre <stpeter@stpeter.im>

Applications Area Advisor:
 Alexey Melnikov <alexey.melnikov@isode.com>

Mailing Lists: TBD

Description of Working Group:

The Applications Area Directors sometimes receives proposals for the
development of specifications dealing with application-related topics
that are not in scope for an existing working group and do not justify
the formation of a new working group.

The Applications Area Working Group (APPSAWG) can serve as a forum for
such work in the IETF.  The APPSAWG accepts work items in accordance
with the  consensus of the Working Group and the best judgment of the
Applications Area Directors, who are responsible for updating the
working group milestones as needed.  The working group meets if there
are active proposals that require intensive discussion.

Work items that are appropriate for the APPSAWG mostly fall under the
following topics:

(A) Well-defined security issues that are relevant to multiple
application technologies (e.g., draft-saintandre-tls-server-id-check).

(B) Small-scale additions to the protocol stack for HTTP and other
application technologies, mostly related to service discovery and
meta-data (e.g., RFC 5785, draft-nottingham-http-link-header, and
draft-hammer-hostmeta).

(C) Selected other work items addressing topics that historically fall
within the Applications Area, such as calendaring, date and time
formats, HTTP, internationalization, language tags, MIME, URIs and XML.

When considering whether to accept a proposed work item, the APPSAWG and
the Applications Area Directors shall take into account the following
factors, among others:

(1) Whether the WG has consensus on the suitability, importance, and
projected quality of the proposed work item.

(2) Whether there is core team of WG participants with sufficient energy
and expertise to advance the proposed work item according to the
proposed schedule.

(3) Whether there are enough WG participants who are willing to review
the work produced by the document authors or editors.

(4) Whether the Area Directors judge that wider input is needed before
accepting the proposed work item (e.g., from the IESG, IAB, or another
standards development organization).

(5) There is no existing related Working Group that is willing to
recharter to take on this work, and the document doesn't justify the
formation of a new working group.

In order to evaluate success of this WG, it is deliberately limited in
its duration. The WG needs to close or be rechartered to remove this
restriction before July 2011.

From stpeter@stpeter.im  Tue Sep 28 10:47:24 2010
Return-Path: <stpeter@stpeter.im>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 234553A6E17 for <apps-discuss@core3.amsl.com>; Tue, 28 Sep 2010 10:47:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.527
X-Spam-Level: 
X-Spam-Status: No, score=-102.527 tagged_above=-999 required=5 tests=[AWL=0.072, 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 b1ctlAqZSOoV for <apps-discuss@core3.amsl.com>; Tue, 28 Sep 2010 10:47:21 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id 856EC3A6D8C for <apps-discuss@ietf.org>; Tue, 28 Sep 2010 10:47:21 -0700 (PDT)
Received: from moveme.cisco.com (72-163-0-129.cisco.com [72.163.0.129]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 79102400EE for <apps-discuss@ietf.org>; Tue, 28 Sep 2010 11:53:29 -0600 (MDT)
Message-ID: <4CA22A4F.3080502@stpeter.im>
Date: Tue, 28 Sep 2010 11:47:59 -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.1.12) Gecko/20100914 Thunderbird/3.0.8
MIME-Version: 1.0
To: "apps-discuss@ietf.org" <apps-discuss@ietf.org>
X-Enigmail-Version: 1.0.1
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: [apps-discuss] Fwd: WG Review: Web Security (websec)
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Sep 2010 17:47:24 -0000

FYI.

-------- Original Message --------
Subject: WG Review: Web Security (websec)
Date: Tue, 28 Sep 2010 10:15:06 -0700 (PDT)
From: IESG Secretary <iesg-secretary@ietf.org>
Reply-To: iesg@ietf.org
To: ietf-announce@ietf.org
CC: hasmat@ietf.org

A new IETF working group has been proposed in the Applications Area.  The
IESG has not made any determination as yet. The following draft charter
was submitted, and is provided for informational purposes only. Please
send your comments to the IESG mailing list (iesg@ietf.org) by Tuesday,
October 5, 2010.

Web Security (websec)
---------------------------------------------
Status: Proposed Working Group
Last updated: 2010-09-23

Chairs(s)
   Tobias Gondrom <tobias.gondrom@gondrom.org>

Applications Area Directors:
   Alexey Melnikov <alexey.melnikov@isode.com>
   Peter Saint-Andre <stpeter@stpeter.im>

Applications Area Advisor:
   Peter Saint-Andre <stpeter@stpeter.im>

Security Area Advisor:
   Sean Turner <turners@ieca.com>

Mailing Lists:
  General Discussion: hasmat@ietf.org
  To Subscribe: <https://www.ietf.org/mailman/listinfo/hasmat>
  Archive: <http://www.ietf.org/mail-archive/web/hasmat/>
  [to be changed to websec@ietf.org if approved]

Problem Statement

Although modern Web applications are built on top of HTTP, they provide
rich functionality and have requirements beyond the original vision of
static web pages.  HTTP, and the applications built on it, have evolved
organically.  Over the past few years, we have seen a proliferation of
AJAX-based web applications (AJAX being shorthand for asynchronous
JavaScript and XML), as well as Rich Internet Applications (RIAs), based
on so-called Web 2.0 technologies.  These applications bring both
luscious eye-candy and convenient functionality, e.g. social networking,
to their users, making them quite compelling.  At the same time, we are
seeing an increase in attacks against these applications and their
underlying technologies.

The list of attacks is long and includes Cross-Site-Request Forgery
(CSRF)-based attacks, content-sniffing, cross-site-scripting (XSS)
attacks, attacks against browsers supporting anti-XSS policies,
clickjacking attacks, malvertising attacks, as well as man-in-the-middle
(MITM) attacks against "secure" (e.g. Transport Layer Security
(TLS/SSL)-based) web sites along with distribution of the tools to carry
out such attacks (e.g. sslstrip).

Objectives and Scope

With the arrival of new attacks the introduction of new web security
indicators, security techniques, and policy communication mechanisms
have sprinkled throughout the various layers of the Web and HTTP.

The goal of this working group is to compose an overall "problem
statement and requirements" document derived from surveying the
issues outlined in the above section ([1] provides a starting point).
The requirements guiding the work will be taken from the Web
application and Web security communities.  The scope of this document
is HTTP applications security, but does not include HTTP authentication,
nor internals of transport security which are addressed by other working
groups (although it may make reference to transport security as an
available security "primitive").  See the "Out of Scope" section, below.

Additionally, the WG will standardize a small number of selected
specifications that have proven to improve security of Internet
Web applications.  Initial work will be the following topics:

  - Same origin policy, as discussed in draft-abarth-origin
    (see also Appendices A and B, below)

  - HTTP Strict transport security, as discussed in
    draft-hodges-strict-transport-sec

  - Media type sniffing, as discussed in draft-abarth-mime-sniff

This working group will work closely with IETF Apps Area WGs (such as
HYBI, HTTPstate, and HTTPbis), as well as appropriate W3C working
group(s) (e.g. HTML, WebApps).

Out of Scope

As noted in the objectives and scope (above), this working group's
scope does not include working on HTTP Authentication nor underlying
transport (secure or not) topics. So, for example, these items are
out-of-scope for this WG:

  - Replacements for BASIC and DIGEST authentication

  - New transports (e.g. SCTP and the like)

Deliverables

1. A document illustrating the security problems Web applications are
facing and listing design requirements.  This document shall be
Informational.

2. A selected set of technical specifications documenting deployed
HTTP-based Web security solutions. These documents shall be Standards
Track.

Goals and Milestones

Oct 2010    Submit "HTTP Application Security Problem Statement and
           Requirements" as initial WG item.

Oct 2010    Submit "Media Type Sniffing" as initial WG item.

Oct 2010    Submit "Web Origin Concept" as initial WG item.

Oct 2010    Submit "Strict Transport Security" as initial WG item.

Feb 2011    Submit "HTTP Application Security Problem Statement and
           Requirements" to the IESG for consideration as an
           Informational RFC.

Mar 2011    Submit "Media Type Sniffing" to the IESG for consideration
           as a Standards Track RFC.

Mar 2011    Submit "Web Origin Concept" to the IESG for consideration as
           a Standards Track RFC.

Mar 2011    Submit "Strict Transport Security" to the IESG for
           consideration as a Standards Track RFC.

Apr 2011    Possible re-chartering

References

[1] Hodges and Steingruebl, "The Need for a Coherent Web Security Policy
Framework", W2SP position paper, 2010.
http://w2spconf.com/2010/papers/p11.pdf

Appendices

A. Relationship between origin work in IETF WebSec and W3C HTML WG

draft-abarth-origin defines the nuts-and-bolts of working with
origins (computing them from URIs, comparing them to each other, etc).
HTML5 defines HTML-specific usage of origins.  For example, when
making an HTTP request, HTML5 defines how to compute which origin
among all the origins rendering HTML is the one responsible for making
the request.  draft-abarth-origin then takes that origin, serializes
it to a string, and shoves it in a header.

B. Origin work may yield two specifications

There also seems to be demand for a document that describes the
same-origin security model overall.  However, it seems like that
document ought to be more informative rather than normative. The
working group may split draft-abarth-origin into separate informative
and standards track specifications, the former describing same-origin
security model, and the latter specifying the nuts-and-bolts of working
with origins (computing them from URLs, comparing them to each other,
etc).

From eran@hueniverse.com  Tue Sep 28 13:45:20 2010
Return-Path: <eran@hueniverse.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AD36C3A6DF8 for <apps-discuss@core3.amsl.com>; Tue, 28 Sep 2010 13:45:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.496
X-Spam-Level: 
X-Spam-Status: No, score=-2.496 tagged_above=-999 required=5 tests=[AWL=0.102,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 4bsZOW2dnLEp for <apps-discuss@core3.amsl.com>; Tue, 28 Sep 2010 13:44:58 -0700 (PDT)
Received: from p3plex1out01.prod.phx3.secureserver.net (p3plex1out01.prod.phx3.secureserver.net [72.167.180.17]) by core3.amsl.com (Postfix) with SMTP id 1D1893A6CAD for <apps-discuss@ietf.org>; Tue, 28 Sep 2010 13:44:58 -0700 (PDT)
Received: (qmail 14075 invoked from network); 28 Sep 2010 20:45:39 -0000
Received: from unknown (HELO smtp.ex1.secureserver.net) (72.167.180.21) by p3plex1out01.prod.phx3.secureserver.net with SMTP; 28 Sep 2010 20:45:38 -0000
Received: from P3PW5EX1MB01.EX1.SECURESERVER.NET ([10.6.135.20]) by P3PW5EX1HT003.EX1.SECURESERVER.NET ([72.167.180.21]) with mapi; Tue, 28 Sep 2010 13:45:31 -0700
From: Eran Hammer-Lahav <eran@hueniverse.com>
To: "apps-discuss@ietf.org" <apps-discuss@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
Date: Tue, 28 Sep 2010 13:45:38 -0700
Thread-Topic: apps-review comments for draft-lundberg-app-tei-xml-03
Thread-Index: ActfR78A919if47BTaiNVGH8hZ1m3Q==
Message-ID: <90C41DD21FB7C64BB94121FBBC2E72343D460DB7CB@P3PW5EX1MB01.EX1.SECURESERVER.NET>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_90C41DD21FB7C64BB94121FBBC2E72343D460DB7CBP3PW5EX1MB01E_"
MIME-Version: 1.0
Cc: "laurent.romary@inria.fr" <laurent.romary@inria.fr>, "slu@kb.dk" <slu@kb.dk>
Subject: [apps-discuss] apps-review comments for draft-lundberg-app-tei-xml-03
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Sep 2010 20:45:20 -0000

--_000_90C41DD21FB7C64BB94121FBBC2E72343D460DB7CBP3PW5EX1MB01E_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I have been selected as the Applications Area Review Team reviewer for this=
 draft (for background on apps-review, please see http://www.apps.ietf.org/=
content/applications-area-review-team).



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



Document: draft-lundberg-app-tei-xml-03

Reviewer: Eran Hammer-Lahav

Review Date: September 28, 2010

IETF Last Call Date: September 2-30, 2010

IESG Telechat Date: Unknown



Summary: This draft is almost ready for publication as a Standards Track RF=
C.  The technical material is straight forward, but has a few minor documen=
t-level issues and numerous grammatical/editorial nits that should be revie=
wed before publication.



MAJOR ISSUES: None.



MINOR ISSUES:



- Section 2


* 'Published specification' should point to this draft, not the [TEI] speci=
fication.


* Interoperability considerations should be none, and the '.xml' comment mo=
ved to 'file extensions'.



* 'Security considerations' should refer to [[this specification]], and the=
 comment about 'the security issues of [RFC3986], section 7' moved to the S=
ecurity Consideration section. Also add "In addition, as this media type us=
es the "+xml" convention, it shares the same security considerations as des=
cribed in RFC 3023 [RFC3023], section 10.".



- Section 3



* The examples should be XML snippets of actual TEI documents, not just rep=
hrasing of the previous paragraph.



- Section 5.2


* I don't understand why this text is needed or why it is part of the secur=
ity consideration section. If the authors insist on including it, I suggest=
 moving it to an appendix and changing the title to something like 'TEI Doc=
ument Content Intellectual Property Rights' to make it clear this is not ab=
out this specification or TEI, but the actual documents.



NITS:



- Section 1



* "The TEI is" reads funny. Should be "TEI is".



* "This document defines the 'application/tei+xml' media type in accordance=
 with [RFC3023], in order to enable generic XML processing of TEI documents=
 on the Internet."



- Section 2



* Move this section into a subsection of 'IANA Considerations' titled "appl=
ication/tei+xml media type registration".



* Optional parameters: "charset":  This parameter has identical semantics t=
o the charset parameter of the "application/xml" media type as specified in=
 RFC 3023 [RFC3023].  [RFC3023].



* Encoding considerations:  Identical to those of "application/xml" as desc=
ribed in RFC 3023 [RFC3023], section 3.2.



* Applications which use this media type: There are currently no applicatio=
ns using the media type 'application/tei+xml'.



- Section 3



* TEI files are XML documents or fragments with a root element in a TEI nam=
espace. TEI namespace URIs start with 'http://www.tei-c.org/ns/', followed =
by the version number of the namespace.  The current namespace is 'http://w=
ww.tei-c.org/ns/1.0'.



- Section 4



* "Documents having the media type 'application/tei+xml', use the fragment =
identifier notation as specified in [RFC3023] for the 'application/xml' med=
ia type.




Thanks,

EHL

--_000_90C41DD21FB7C64BB94121FBBC2E72343D460DB7CBP3PW5EX1MB01E_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	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:11.0pt;
	font-family:"Calibri","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
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:"Calibri","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoPlainText>I have been s=
elected as the Applications Area Review Team reviewer for this draft (for b=
ackground on apps-review, please see <a href=3D"http://www.apps.ietf.org/co=
ntent/applications-area-review-team">http://www.apps.ietf.org/content/appli=
cations-area-review-team</a>).<o:p></o:p></p><p class=3DMsoPlainText><o:p>&=
nbsp;</o:p></p><p class=3DMsoPlainText>Please resolve these comments along =
with any other Last Call comments you may receive. Please wait for directio=
n from your document shepherd or AD before posting a new version of the dra=
ft.<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DM=
soPlainText>Document: draft-lundberg-app-tei-xml-03<o:p></o:p></p><p class=
=3DMsoPlainText>Reviewer: Eran Hammer-Lahav<o:p></o:p></p><p class=3DMsoPla=
inText>Review Date: September 28, 2010<o:p></o:p></p><p class=3DMsoPlainTex=
t>IETF Last Call Date: September 2-30, 2010<o:p></o:p></p><p class=3DMsoPla=
inText>IESG Telechat Date: Unknown<o:p></o:p></p><p class=3DMsoPlainText><o=
:p>&nbsp;</o:p></p><p class=3DMsoPlainText>Summary: This draft is almost re=
ady for publication as a Standards Track RFC.&nbsp; The technical material =
is straight forward, but has a few minor document-level issues and numerous=
 grammatical/editorial nits that should be reviewed before publication.<o:p=
></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlain=
Text>MAJOR ISSUES: None.<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;<=
/o:p></p><p class=3DMsoPlainText>MINOR ISSUES: <o:p></o:p></p><p class=3DMs=
oPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>- Section 2<o:p></o=
:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>* =
&#8216;Published specification&#8217; should point to this draft, not the [=
TEI] specification.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p=
><p class=3DMsoPlainText>* Interoperability considerations should be none, =
and the &#8216;.xml&#8217; comment moved to &#8216;file extensions&#8217;.<=
o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPl=
ainText>* &#8216;Security considerations&#8217; should refer to [[this spec=
ification]], and the comment about &#8216;the security issues of [RFC3986],=
 section 7&#8217; moved to the Security Consideration section. Also add &#8=
220;In addition, as this media type uses the &quot;+xml&quot; convention, i=
t shares the same security considerations as described in RFC 3023 [RFC3023=
], section 10.&#8221;.<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o=
:p></p><p class=3DMsoPlainText>- Section 3<o:p></o:p></p><p class=3DMsoPlai=
nText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>* The examples should be=
 XML snippets of actual TEI documents, not just rephrasing of the previous =
paragraph.<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p cl=
ass=3DMsoPlainText>- Section 5.2<o:p></o:p></p><p class=3DMsoPlainText><o:p=
>&nbsp;</o:p></p><p class=3DMsoNormal>* I don&#8217;t understand why this t=
ext is needed or why it is part of the security consideration section. If t=
he authors insist on including it, I suggest moving it to an appendix and c=
hanging the title to something like &#8216;TEI Document Content Intellectua=
l Property Rights&#8217; to make it clear this is not about this specificat=
ion or TEI, but the actual documents.<o:p></o:p></p><p class=3DMsoPlainText=
><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>NITS:<o:p></o:p></p><p class=
=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>- Section 1<o:=
p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlai=
nText>* &#8220;The TEI is&#8221; reads funny. Should be &#8220;TEI is&#8221=
;.<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMs=
oPlainText>* &#8220;This document defines the 'application/tei+xml' media t=
ype in accordance with [RFC3023], in order to enable generic XML processing=
 of TEI documents on the Internet.&#8221;<o:p></o:p></p><p class=3DMsoPlain=
Text><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>- Section 2<o:p></o:p></p=
><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>* Mov=
e this section into a subsection of &#8216;IANA Considerations&#8217; title=
d &#8220;application/tei+xml media type registration&#8221;.<o:p></o:p></p>=
<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>* Opti=
onal parameters: &quot;charset&quot;:&nbsp; This parameter has identical se=
mantics to the charset parameter of the &quot;application/xml&quot; media t=
ype as specified in RFC 3023 [RFC3023].&nbsp; [RFC3023].<o:p></o:p></p><p c=
lass=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>* Encoding=
 considerations:&nbsp; Identical to those of &quot;application/xml&quot; as=
 described in RFC 3023 [RFC3023], section 3.2.<o:p></o:p></p><p class=3DMso=
PlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>* Applications which=
 use this media type: There are currently no applications using the media t=
ype 'application/tei+xml&#8217;.<o:p></o:p></p><p class=3DMsoPlainText><o:p=
>&nbsp;</o:p></p><p class=3DMsoPlainText>- Section 3<o:p></o:p></p><p class=
=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>* TEI files ar=
e XML documents or fragments with a root element in a TEI namespace. TEI na=
mespace URIs start with &#8216;http://www.tei-c.org/ns/&#8217;, followed by=
 the version number of the namespace.&nbsp; The current namespace is &#8216=
;http://www.tei-c.org/ns/1.0&#8217;.<o:p></o:p></p><p class=3DMsoPlainText>=
<o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>- Section 4<o:p></o:p></p><p c=
lass=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>* &#8220;D=
ocuments having the media type 'application/tei+xml', use the fragment iden=
tifier notation as specified in [RFC3023] for the 'application/xml' media t=
ype.<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3D=
MsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Thanks,<o:p></o:p></=
p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>EHL<o:p></=
o:p></p></div></body></html>=

--_000_90C41DD21FB7C64BB94121FBBC2E72343D460DB7CBP3PW5EX1MB01E_--

From sm@elandsys.com  Tue Sep 28 17:05:58 2010
Return-Path: <sm@elandsys.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C8FD93A6E4A; Tue, 28 Sep 2010 17:05:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.462
X-Spam-Level: 
X-Spam-Status: No, score=-102.462 tagged_above=-999 required=5 tests=[AWL=0.137, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M+fHgW6xjdQd; Tue, 28 Sep 2010 17:05:56 -0700 (PDT)
Received: from mail.elandsys.com (mail.elandsys.com [208.69.177.125]) by core3.amsl.com (Postfix) with ESMTP id 579A83A6E48; Tue, 28 Sep 2010 17:05:56 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([41.136.232.119]) (authenticated bits=0) by mail.elandsys.com (8.13.8/8.13.8) with ESMTP id o8T06SR2012245; Tue, 28 Sep 2010 17:06:33 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=elandsys.com; s=mail; t=1285718796; bh=KmprMnYeT4IKtM5T9vGSZDhitgg=; h=Message-Id:Date:To:From:Subject:Cc:Mime-Version:Content-Type; b=VgwtQjFx7E4WFVqoXMdqYiZyfobyq9YRYjtw8TA7q7xbxFlQvabqZQ/RaUXIp3Dqq K5L+A/iZbzdChKbvZRFhCbSeVOnKOrgxpZKjY1qaZm6E7//5C9Ch2iHAOZQsBJ3erM eAi/EQkjWTu5DLSllID6S84hcjzFC5tPm8NZoFpQ=
Message-Id: <6.2.5.6.2.20100928130147.0cb0c870@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 28 Sep 2010 17:06:03 -0700
To: apps-discuss@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: Mark Townsley <townsley@cisco.com>, Jari Arkko <jari.arkko@piuha.net>, iesg@ietf.org
Subject: [apps-discuss] Apps-team review of draft-arkko-townsley-coexistence-04
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Sep 2010 00:05:58 -0000

Hello,

I have been selected as the Applications Area Review Team reviewer 
for this draft (for background on apps-review, please see 
http://www.apps.ietf.org/content/applications-area-review-team).

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

Document: draft-arkko-townsley-coexistence-04
Reviewer: S. Moonesamy
Review Date: September 28, 2010
IETF Last Call Date: September 13, 2010
IESG Telechat Date: Unknown

Summary:

This draft is almost ready for publication as a RFC but has a few 
issues that should be fixed before publication.  Please refer to the 
comment about the intended status.  The Introduction Section does not 
reflect the text in the Abstract Section which mentions that the 
document is being published to reflect the thinking at the time (2008).

Major Issues:

None

Minor Issues:

According to the Abstract Section:

   "This document was originally created as input to the Montreal co-
    existence interim meeting in October 2008, which led to the
    rechartering of the Behave and Softwire working groups to take on new
    IPv4 and IPv6 coexistence work.  This document is published as a
    historical record of the thinking at the time."

The Introduction Section should be updated to reflect what the 
document seeks to represent, i.e. the thinking in 2008.

In the Security Considerations Section:

   "It is important to note that some of the solutions may have impacts
    on how IPsec or DNS Security can work through translation devices."

I suggest adding application protocols to that as the solutions may 
have an impact on them.

Nits:

The intended status of this I-D is Informational.  The Abstract 
Section mentions that:

   "This document is published as a historical record of the thinking 
at the time."

In Section 2.1, please expand "GW" on first use.  In Section 2.1.2, 
please expand "ALGs" on first use.

Regards,
S. Moonesamy


From James.H.Manger@team.telstra.com  Tue Sep 28 17:23:04 2010
Return-Path: <James.H.Manger@team.telstra.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8F5773A6BF1 for <apps-discuss@core3.amsl.com>; Tue, 28 Sep 2010 17:23:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.443
X-Spam-Level: 
X-Spam-Status: No, score=-0.443 tagged_above=-999 required=5 tests=[AWL=0.457,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, HTML_MESSAGE=0.001, RELAY_IS_203=0.994]
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 fO0Dqh3q7fgB for <apps-discuss@core3.amsl.com>; Tue, 28 Sep 2010 17:23:01 -0700 (PDT)
Received: from ipxavo.tcif.telstra.com.au (ipxavo.tcif.telstra.com.au [203.35.135.200]) by core3.amsl.com (Postfix) with ESMTP id 1C6CA3A6BE1 for <apps-discuss@ietf.org>; Tue, 28 Sep 2010 17:23:00 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.57,250,1283695200"; d="scan'208,217";a="12634469"
Received: from unknown (HELO ipcdvi.tcif.telstra.com.au) ([10.97.217.212]) by ipoavi.tcif.telstra.com.au with ESMTP; 29 Sep 2010 10:23:42 +1000
X-IronPort-AV: E=McAfee;i="5400,1158,6120"; a="9546840"
Received: from wsmsg3707.srv.dir.telstra.com ([172.49.40.81]) by ipcdvi.tcif.telstra.com.au with ESMTP; 29 Sep 2010 10:23:42 +1000
Received: from WSMSG3153V.srv.dir.telstra.com ([172.49.40.159]) by wsmsg3707.srv.dir.telstra.com ([172.49.40.81]) with mapi; Wed, 29 Sep 2010 10:23:41 +1000
From: "Manger, James H" <James.H.Manger@team.telstra.com>
To: "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Date: Wed, 29 Sep 2010 10:23:39 +1000
Thread-Topic: [apps-discuss] Title of docs in apps-review comments
Thread-Index: ActfR78A919if47BTaiNVGH8hZ1m3QAHcGyg
Message-ID: <255B9BB34FB7D647A506DC292726F6E1126C4376B8@WSMSG3153V.srv.dir.telstra.com>
References: <90C41DD21FB7C64BB94121FBBC2E72343D460DB7CB@P3PW5EX1MB01.EX1.SECURESERVER.NET>
In-Reply-To: <90C41DD21FB7C64BB94121FBBC2E72343D460DB7CB@P3PW5EX1MB01.EX1.SECURESERVER.NET>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-AU
Content-Type: multipart/alternative; boundary="_000_255B9BB34FB7D647A506DC292726F6E1126C4376B8WSMSG3153Vsrv_"
MIME-Version: 1.0
Subject: [apps-discuss]  Title of docs in apps-review comments
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Sep 2010 00:23:04 -0000

--_000_255B9BB34FB7D647A506DC292726F6E1126C4376B8WSMSG3153Vsrv_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

The app-reviews appearing on this list look like a useful step in the IETF =
process.

Could the *title* of the draft being reviewed please be included in the rev=
iew emails (ie added to the template http://www.apps.ietf.org/content/apps-=
review-template). The reviews currently only list the file name of the draf=
t, which doesn't give enough context given the broad range of topics in the=
 Apps area.



Instead of just:

  Document: draft-arkko-townsley-coexistence-04



Include:

  Document: draft-arkko-townsley-coexistence-04

  Title: IPv4 Run-Out and IPv4-IPv6 Co-Existence Scenarios



Thanks



--

James Manger


--_000_255B9BB34FB7D647A506DC292726F6E1126C4376B8WSMSG3153Vsrv_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	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:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle21
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
-->
</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=3D"EN-AU" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">The app-reviews appear=
ing on this list look like a useful step in the IETF process.<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Could the *<b>title</b=
>* of the draft being reviewed please be included in the review emails (ie =
added to the template
<a href=3D"http://www.apps.ietf.org/content/apps-review-template">http://ww=
w.apps.ietf.org/content/apps-review-template</a>). The reviews currently on=
ly list the file name of the draft, which doesn&#8217;t give enough context=
 given the broad range of topics in the
 Apps area.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Instead of just:<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp; Document: draft=
-arkko-townsley-coexistence-04<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Include:<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp; Document: draft=
-arkko-townsley-coexistence-04<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp; Title: IPv4 Run=
-Out and IPv4-IPv6 Co-Existence Scenarios<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thanks<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">--<o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">James Manger<o:p></o:p=
></span></p>
</div>
</div>
</body>
</html>

--_000_255B9BB34FB7D647A506DC292726F6E1126C4376B8WSMSG3153Vsrv_--

From sm@elandsys.com  Tue Sep 28 19:10:47 2010
Return-Path: <sm@elandsys.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 16D123A6E5F for <apps-discuss@core3.amsl.com>; Tue, 28 Sep 2010 19:10:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.465
X-Spam-Level: 
X-Spam-Status: No, score=-102.465 tagged_above=-999 required=5 tests=[AWL=0.134, 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 VTxEKjLSeF0g for <apps-discuss@core3.amsl.com>; Tue, 28 Sep 2010 19:10:40 -0700 (PDT)
Received: from mail.elandsys.com (mail.elandsys.com [208.69.177.125]) by core3.amsl.com (Postfix) with ESMTP id E0B223A6C02 for <apps-discuss@ietf.org>; Tue, 28 Sep 2010 19:10:34 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([41.136.238.102]) (authenticated bits=0) by mail.elandsys.com (8.13.8/8.13.8) with ESMTP id o8T2B9Mq019758; Tue, 28 Sep 2010 19:11:15 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=elandsys.com; s=mail; t=1285726277; bh=bO+e8EXEt1KsElAn5ZgxSoX2ed8=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=EI+CQfFDEYsIiWX2XwpwhI8GMofJnp4XydSSTYYcfDRaxdsByhzZYw0UPs/JMXFgj AuqfzQRWMCMXnAEZ5yVftmdaTaw7ZEfOx1FEsGVGnZmHXZJ7QQMw9I3aAFHTt5FMl/ mLjYIkRQgZTRLnYQYqYEIw+XC21mizLhJRm5zvzc=
Message-Id: <6.2.5.6.2.20100928185109.0a44a498@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 28 Sep 2010 19:10:46 -0700
To: "Manger, James H" <James.H.Manger@team.telstra.com>
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <255B9BB34FB7D647A506DC292726F6E1126C4376B8@WSMSG3153V.srv. dir.telstra.com>
References: <90C41DD21FB7C64BB94121FBBC2E72343D460DB7CB@P3PW5EX1MB01.EX1.SECURESERVER.NET> <255B9BB34FB7D647A506DC292726F6E1126C4376B8@WSMSG3153V.srv.dir.telstra.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: apps-discuss@ietf.org
Subject: Re: [apps-discuss] Title of docs in apps-review comments
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Sep 2010 02:10:47 -0000

Hi James,
At 17:23 28-09-10, Manger, James H wrote:
>Could the *title* of the draft being reviewed please be included in 
>the review emails (ie added to the template 
><http://www.apps.ietf.org/content/apps-review-template>http://www.apps.ietf.org/content/apps-review-template). 
>The reviews currently only list the file name of the draft, which 
>doesn't give enough context given the broad range of topics in the Apps area.

Thanks for the feedback.  The title will be added to the template.

Some of the Internet-Drafts that are reviewed by the Apps Area Review 
Team are from outside the Applications Area.

Regards,
S. Moonesamy 


From ietfdbh@comcast.net  Tue Sep 28 19:21:28 2010
Return-Path: <ietfdbh@comcast.net>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 751573A6AD8 for <apps-discuss@core3.amsl.com>; Tue, 28 Sep 2010 19:21:28 -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.299, 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 16qUCcSSIXdk for <apps-discuss@core3.amsl.com>; Tue, 28 Sep 2010 19:21:24 -0700 (PDT)
Received: from qmta12.westchester.pa.mail.comcast.net (qmta12.westchester.pa.mail.comcast.net [76.96.59.227]) by core3.amsl.com (Postfix) with ESMTP id 525E23A6A21 for <apps-discuss@ietf.org>; Tue, 28 Sep 2010 19:21:24 -0700 (PDT)
Received: from omta17.westchester.pa.mail.comcast.net ([76.96.62.89]) by qmta12.westchester.pa.mail.comcast.net with comcast id CS2Q1f0071vXlb85CSN7JS; Wed, 29 Sep 2010 02:22:07 +0000
Received: from 23FX1C1 ([67.189.235.106]) by omta17.westchester.pa.mail.comcast.net with comcast id CSN61f0012JQnJT3dSN6qC; Wed, 29 Sep 2010 02:22:07 +0000
From: "David Harrington" <ietfdbh@comcast.net>
To: <apps-discuss@ietf.org>
References: <90C41DD21FB7C64BB94121FBBC2E72343D460DB7CB@P3PW5EX1MB01.EX1.SECURESERVER.NET> <255B9BB34FB7D647A506DC292726F6E1126C4376B8@WSMSG3153V.srv.dir.telstra.com>
Date: Tue, 28 Sep 2010 22:21:53 -0400
Message-ID: <569811D7D7E54DB4A80BBEA9FB81302A@23FX1C1>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0EE0_01CB5F5B.8EC997B0"
X-Mailer: Microsoft Office Outlook 11
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5994
Thread-index: ActfR78A919if47BTaiNVGH8hZ1m3QAHcGygAAXVdYA=
In-Reply-To: <255B9BB34FB7D647A506DC292726F6E1126C4376B8@WSMSG3153V.srv.dir.telstra.com>
Subject: Re: [apps-discuss] Title of docs in apps-review comments
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Sep 2010 02:21:28 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0EE0_01CB5F5B.8EC997B0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi,
 
I just looked at the apps-review template.
C'mon, I know you work on web stuff, but you can't have prettier
review templates than the rest of the areas! <pout> ;-)
 
David Harrington
Director, IETF Transport Area
ietfdbh@comcast.net (preferred for ietf)
dbharrington@huaweisymantec.com
+1 603 828 1401 (cell) 


  _____  

From: apps-discuss-bounces@ietf.org
[mailto:apps-discuss-bounces@ietf.org] On Behalf Of Manger, James H
Sent: Tuesday, September 28, 2010 8:24 PM
To: apps-discuss@ietf.org
Subject: [apps-discuss] Title of docs in apps-review comments



The app-reviews appearing on this list look like a useful step in the
IETF process.

Could the *title* of the draft being reviewed please be included in
the review emails (ie added to the template
http://www.apps.ietf.org/content/apps-review-template). The reviews
currently only list the file name of the draft, which doesn't give
enough context given the broad range of topics in the Apps area.

 

Instead of just:

  Document: draft-arkko-townsley-coexistence-04

 

Include:

  Document: draft-arkko-townsley-coexistence-04

  Title: IPv4 Run-Out and IPv4-IPv6 Co-Existence Scenarios

 

Thanks

 

--

James Manger


------=_NextPart_000_0EE0_01CB5F5B.8EC997B0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:m =3D=20
"http://schemas.microsoft.com/office/2004/12/omml"><HEAD>
<META content=3D"text/html; charset=3Dus-ascii" =
http-equiv=3DContent-Type>
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18939">
<STYLE>@font-face {
	font-family: Calibri;
}
@page WordSection1 {size: 612.0pt 792.0pt; margin: 72.0pt 72.0pt 72.0pt =
72.0pt; }
P.MsoNormal {
	MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: =
11pt
}
LI.MsoNormal {
	MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: =
11pt
}
DIV.MsoNormal {
	MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: =
11pt
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
P.MsoPlainText {
	MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: =
11pt; mso-style-priority: 99; mso-style-link: "Plain Text Char"
}
LI.MsoPlainText {
	MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: =
11pt; mso-style-priority: 99; mso-style-link: "Plain Text Char"
}
DIV.MsoPlainText {
	MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: =
11pt; mso-style-priority: 99; mso-style-link: "Plain Text Char"
}
P.MsoListParagraph {
	MARGIN: 0cm 0cm 0pt 36pt; FONT-FAMILY: "Calibri","sans-serif"; =
FONT-SIZE: 11pt; mso-style-priority: 34
}
LI.MsoListParagraph {
	MARGIN: 0cm 0cm 0pt 36pt; FONT-FAMILY: "Calibri","sans-serif"; =
FONT-SIZE: 11pt; mso-style-priority: 34
}
DIV.MsoListParagraph {
	MARGIN: 0cm 0cm 0pt 36pt; FONT-FAMILY: "Calibri","sans-serif"; =
FONT-SIZE: 11pt; mso-style-priority: 34
}
SPAN.PlainTextChar {
	FONT-FAMILY: "Calibri","sans-serif"; mso-style-priority: 99; =
mso-style-link: "Plain Text"; mso-style-name: "Plain Text Char"
}
SPAN.EmailStyle20 {
	FONT-FAMILY: "Calibri","sans-serif"; COLOR: windowtext; mso-style-type: =
personal
}
SPAN.EmailStyle21 {
	FONT-FAMILY: "Calibri","sans-serif"; COLOR: #1f497d; mso-style-type: =
personal-reply
}
.MsoChpDefault {
	FONT-SIZE: 10pt; mso-style-type: export-only
}
DIV.WordSection1 {
	page: WordSection1
}
</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-AU link=3Dblue vLink=3Dpurple>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D009092002-29092010><FONT =
color=3D#0000ff=20
size=3D2 face=3DArial>Hi,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D009092002-29092010><FONT =
color=3D#0000ff=20
size=3D2 face=3DArial></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D009092002-29092010><FONT =
color=3D#0000ff=20
size=3D2 face=3DArial>I just looked at the apps-review =
template.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D009092002-29092010><FONT =
color=3D#0000ff=20
size=3D2 face=3DArial>C'mon, I know you work on web stuff, but you can't =
have=20
prettier review templates than the rest of the areas! &lt;pout&gt;=20
;-)</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D009092002-29092010><FONT =
color=3D#0000ff=20
size=3D2 face=3DArial><FONT size=3D2></FONT></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D009092002-29092010><FONT =
color=3D#0000ff=20
size=3D2 face=3DArial><FONT size=3D2>David Harrington<BR>Director, IETF =
Transport=20
Area<BR>ietfdbh@comcast.net (preferred for=20
ietf)<BR>dbharrington@huaweisymantec.com<BR>+1 603 828 1401 =
(cell)</FONT>=20
</DIV></FONT></SPAN><BR>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #0000ff 2px solid; PADDING-LEFT: 5px; MARGIN-LEFT: =
5px; MARGIN-RIGHT: 0px"=20
dir=3Dltr>
  <DIV dir=3Dltr lang=3Den-us class=3DOutlookMessageHeader align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT size=3D2 face=3DTahoma><B>From:</B> =
apps-discuss-bounces@ietf.org=20
  [mailto:apps-discuss-bounces@ietf.org] <B>On Behalf Of </B>Manger, =
James=20
  H<BR><B>Sent:</B> Tuesday, September 28, 2010 8:24 PM<BR><B>To:</B>=20
  apps-discuss@ietf.org<BR><B>Subject:</B> [apps-discuss] Title of docs =
in=20
  apps-review comments<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV class=3DWordSection1>
  <P class=3DMsoNormal><SPAN style=3D"COLOR: #1f497d">The app-reviews =
appearing on=20
  this list look like a useful step in the IETF =
process.<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"COLOR: #1f497d">Could the =
*<B>title</B>* of=20
  the draft being reviewed please be included in the review emails (ie =
added to=20
  the template <A=20
  =
href=3D"http://www.apps.ietf.org/content/apps-review-template">http://www=
.apps.ietf.org/content/apps-review-template</A>).=20
  The reviews currently only list the file name of the draft, which =
doesn&#8217;t give=20
  enough context given the broad range of topics in the Apps=20
  area.<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"COLOR: =
#1f497d"><o:p>&nbsp;</o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"COLOR: #1f497d">Instead of=20
  just:<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"COLOR: #1f497d">&nbsp; Document:=20
  draft-arkko-townsley-coexistence-04<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"COLOR: =
#1f497d"><o:p>&nbsp;</o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"COLOR: =
#1f497d">Include:<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"COLOR: #1f497d">&nbsp; Document:=20
  draft-arkko-townsley-coexistence-04<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"COLOR: #1f497d">&nbsp; Title: IPv4 =
Run-Out and=20
  IPv4-IPv6 Co-Existence Scenarios<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"COLOR: =
#1f497d"><o:p>&nbsp;</o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"COLOR: =
#1f497d">Thanks<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"COLOR: =
#1f497d"><o:p>&nbsp;</o:p></SPAN></P>
  <DIV>
  <P class=3DMsoNormal><SPAN style=3D"COLOR: =
#1f497d">--<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"COLOR: #1f497d">James=20
  Manger<o:p></o:p></SPAN></P></DIV></DIV></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0EE0_01CB5F5B.8EC997B0--


From haibinsong.cn@gmail.com  Tue Sep 28 20:13:34 2010
Return-Path: <haibinsong.cn@gmail.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BCB673A6DC4; Tue, 28 Sep 2010 20:13:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jZAX4Ka1RZld; Tue, 28 Sep 2010 20:13:32 -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 082843A6BFC; Tue, 28 Sep 2010 20:13:31 -0700 (PDT)
Received: by qyk2 with SMTP id 2so571966qyk.10 for <multiple recipients>; Tue, 28 Sep 2010 20:14:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date :message-id:mime-version:content-type:x-mailer:thread-index :content-language; bh=wKrzGlkYTIb+SnMB5V/n/cssPhW5qAjsZoYG4wXmL1s=; b=S9Oo3A+Cf5Nv/65oXBS5CekfOYl4E3hVYJ2MdPI02kBjy6Dr0jIY/WYFl5GOp5/C2w fB+D1VSoF6CbKPqhcw//qk9WyTlIsZPHC4Gow5KNaGyvvt3e4d6aAKAU3foj6XR2F9ck yzcPJAkCtCsmiuNrhFdRUSTad6KggvJ5NEoyw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:message-id:mime-version:content-type:x-mailer :thread-index:content-language; b=poDfFQ1GB0G0pZmAlm/6WinE4q+oXVPjo48lVc7dJXXq1u7gnT9dySEvTBdhQT2h6w 6dQlHNXV+3IP/vt8c8aXeO3lNOVMKgjWFvNSJ6H15mNqTGtX/M9GP3TJb1z9k3w5N/H/ hHsfzKiU21nG9u6PheuLaCoeEigHJR0kGxQJQ=
Received: by 10.224.6.145 with SMTP id 17mr663524qaz.220.1285730054151; Tue, 28 Sep 2010 20:14:14 -0700 (PDT)
Received: from jys0449578 (dhcp128036148210.central.yale.edu [128.36.148.210]) by mx.google.com with ESMTPS id t24sm8876359qcs.11.2010.09.28.20.14.12 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 28 Sep 2010 20:14:13 -0700 (PDT)
From: "Haibin Song" <haibinsong.cn@gmail.com>
To: <alto@ietf.org>, <ppsp@ietf.org>, <ledbat@ietf.org>, <apps-discuss@ietf.org>, <p2prg@irtf.org>
Date: Tue, 28 Sep 2010 23:14:11 -0400
Message-ID: <4ca2af05.9882e50a.33c3.4fa5@mx.google.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_007D_01CB5F62.DCBA9440"
X-Mailer: Microsoft Office Outlook 12.0
Thread-index: ActeuL5+1OVFyZX7SrGjYCY2j7swIgAyrQxgAAAxzyA=
Content-language: zh-cn
Subject: [apps-discuss] The International Industrial and Academic Symposium on DECADE and ALTO
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Sep 2010 03:13:34 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_007D_01CB5F62.DCBA9440
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

(sorry for the cross-post, wanted to send to all the appropriate working
groups)

 

I am sending this email to call for participation to the symposium after
IETF Beijing meeting. It is used to promote the design discussion and
sharing industrial and academic information about DECADE and ALTO. It will
not be an official IETF meeting.

 

 

----------------------------------------------------------------------------
----------------------------------------------------------------------------
----------------------------------------------------------------------------
------------

 

                                  The International Industrial and Academic
Symposium on DECADE and ALTO

 

 

The International Industrial and Academic Symposium on DECADE (DECoupled
Application Data Enroute) and ALTO (Application Layer Traffic Optimization)
will present industrial and academic trends and solutions on DECADE and
ALTO, both of which intend to improve the network efficiency.

 

The upstream network links of home users are often relatively small; and
bandwidth-greedy applications such as file sharing and real-time streaming
can quickly saturate the links when uploading content. To address that
problem, DECADE's advocates propose a mechanism whereby users can store
content they are sharing in the network-ahead of the last-mile bottleneck.
The specific objective of DECADE is to specify a protocol for fine-grained
control of such network storage. The protocol is intended to be integrated
in P2P applications, thereby enabling them to store, retrieve, and manage
data remotely as well as to define policies for sharing such data with other
peers and to control the utilization of resources like bandwidth and number
of connections. Although DECADE originated from P2P requirements, it can
also be used for other types of content distribution.

 

P2P applications establish overlays on top of the Internet infrastructure
with little or no knowledge of the underlying network topology. That lack of
information leads peers to make suboptimal choices. For example, it is
common for a peer who needs to obtain information from another peer to
choose randomly, possibly picking one located on the other side of the
planet. Such random selection may ignore many peers who are topologically
closer and that therefore likely would provide better performance. ALTO
solutions intend to enable network operators, Internet service providers,
and others with network topology information to share it with P2P
applications, thereby enabling those applications to improve the peer
selection process. Sharing this information is expected to benefit both end
users and network operators, resulting in better application performance and
more rational use of network resources.

 

Recently, a trend has emerged to combine DECADE and ALTO technologies for
content distribution. Among other topics, this symposium will explore how
these technologies can be combined to improve network efficiency.

 

All of you are welcome to this meeting! Everyone is encouraged to request a
slot for your presentation. We also plan to invite industrial and academic
experts on related areas to give presentations.  The topics include but are
not limited to:

 

(1)     ISPs' considerations/recent actions;

(2)     Vendors' considerations/recent actions;

(3)     Applications' needs;

(4)     Business models;

(5)     General solution;

(6)     Key technical aspects

 

 

The presentation requests and presentation slides should be sent to the
organizers of this meeting before corresponding cut-off dates.

 

If you are interested in attending, please send an email to the organizers
as soon as possible so they may plan meeting space and lunch accordingly.

 

Name                        Email

 

Haibin Song                 melodysong@huawei.com

David Bryan                 dbryan@ethernot.org

 

 

Important dates and Information

===============

 

Time                           15 to 16  November 2010 (next Monday and
Tuesday after IETF 79 meeting)

Location                        Nanjing, China

Meeting Venue                   Hotel information will be available soon

Cut-off date for slot request         25 October 2010

Preliminary agenda                1 November  2010

Final agenda                     8 November 2010

 

 

Travel Information

 

(1) The air flight from Beijing to Nanjing will take about 1 hour and 40
minutes

(2) The high speed train between Shanghai and Nanjing will take about 1 hour
and 18 minutes(non-stop train) or about 2 hours (several stops).

(3) There are also international flights to some Asia Pacific and Europe
countries from Nanjing

 


------=_NextPart_000_007D_01CB5F62.DCBA9440
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:x=3D"urn:schemas-microsoft-com:office:excel" =
xmlns:p=3D"urn:schemas-microsoft-com:office:powerpoint" =
xmlns:a=3D"urn:schemas-microsoft-com:office:access" =
xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" =
xmlns:s=3D"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" =
xmlns:rs=3D"urn:schemas-microsoft-com:rowset" xmlns:z=3D"#RowsetSchema" =
xmlns:b=3D"urn:schemas-microsoft-com:office:publisher" =
xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadsheet" =
xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" =
xmlns:odc=3D"urn:schemas-microsoft-com:office:odc" =
xmlns:oa=3D"urn:schemas-microsoft-com:office:activation" =
xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" =
xmlns:rtc=3D"http://microsoft.com/officenet/conferencing" =
xmlns:D=3D"DAV:" xmlns:Repl=3D"http://schemas.microsoft.com/repl/" =
xmlns:mt=3D"http://schemas.microsoft.com/sharepoint/soap/meetings/" =
xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2003/xml" =
xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" =
xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" =
xmlns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/directory/" =
xmlns:ds=3D"http://www.w3.org/2000/09/xmldsig#" =
xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint/dsp" =
xmlns:udc=3D"http://schemas.microsoft.com/data/udc" =
xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" =
xmlns:sub=3D"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/"=
 xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#" =
xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" =
xmlns:sps=3D"http://schemas.microsoft.com/sharepoint/soap/" =
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" =
xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/soap" =
xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" =
xmlns:udcp2p=3D"http://schemas.microsoft.com/data/udc/parttopart" =
xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/" =
xmlns:dsss=3D"http://schemas.microsoft.com/office/2006/digsig-setup" =
xmlns:dssi=3D"http://schemas.microsoft.com/office/2006/digsig" =
xmlns:mdssi=3D"http://schemas.openxmlformats.org/package/2006/digital-sig=
nature" =
xmlns:mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2006=
" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns:mrels=3D"http://schemas.openxmlformats.org/package/2006/relationshi=
ps" xmlns:spwp=3D"http://microsoft.com/sharepoint/webpartpages" =
xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/2006/types"=
 =
xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/2006/messag=
es" =
xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/=
" =
xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortalServer/Pub=
lishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" =
xmlns:st=3D"&#1;" 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:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@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:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	font-size:10.5pt;
	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:"\7EAF\6587\672C Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
span.Char
	{mso-style-name:"\7EAF\6587\672C Char";
	mso-style-priority:99;
	mso-style-link:\7EAF\6587\672C;
	font-family:"Calibri","sans-serif";}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle21
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
	{page:Section1;}
-->
</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=3DZH-CN link=3Dblue vlink=3Dpurple =
style=3D'text-justify-trim:punctuation'>

<div class=3DSection1>

<p class=3DMsoPlainText><span lang=3DEN-US>(sorry for the cross-post, =
wanted to
send to all the appropriate working groups)<o:p></o:p></span></p>

<p class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoPlainText><span lang=3DEN-US>I am sending this email to =
call for
participation to the symposium after IETF Beijing meeting. It is used to
promote the design discussion and sharing industrial and academic =
information
about DECADE and ALTO. It will not be an official IETF =
meeting.<o:p></o:p></span></p>

<p class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoPlainText><span =
lang=3DEN-US>------------------------------------------------------------=
-------------------------------------------------------------------------=
-------------------------------------------------------------------------=
----------------------------------<o:p></o:p></span></p>

<p class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoPlainText><span =
lang=3DEN-US>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
The International Industrial and Academic Symposium on DECADE and =
ALTO<o:p></o:p></span></p>

<p class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoPlainText><span lang=3DEN-US>The International Industrial =
and Academic
Symposium on DECADE (DECoupled Application Data Enroute) and ALTO =
(Application
Layer Traffic Optimization) will present industrial and academic trends =
and
solutions on DECADE and ALTO, both of which intend to improve the =
network
efficiency.<o:p></o:p></span></p>

<p class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoPlainText><span lang=3DEN-US>The upstream network links of =
home users
are often relatively small; and bandwidth-greedy applications such as =
file
sharing and real-time streaming can quickly saturate the links when =
uploading
content. To address that problem, DECADE's advocates propose a mechanism
whereby users can store content they are sharing in the network-ahead of =
the
last-mile bottleneck. The specific objective of DECADE is to specify a =
protocol
for fine-grained control of such network storage. The protocol is =
intended to
be integrated in P2P applications, thereby enabling them to store, =
retrieve,
and manage data remotely as well as to define policies for sharing such =
data
with other peers and to control the utilization of resources like =
bandwidth and
number of connections. Although DECADE originated from P2P requirements, =
it can
also be used for other types of content =
distribution.<o:p></o:p></span></p>

<p class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoPlainText><span lang=3DEN-US>P2P applications establish =
overlays on
top of the Internet infrastructure with little or no knowledge of the
underlying network topology. That lack of information leads peers to =
make
suboptimal choices. For example, it is common for a peer who needs to =
obtain
information from another peer to choose randomly, possibly picking one =
located
on the other side of the planet. Such random selection may ignore many =
peers
who are topologically closer and that therefore likely would provide =
better
performance. ALTO solutions intend to enable network operators, Internet
service providers, and others with network topology information to share =
it
with P2P applications, thereby enabling those applications to improve =
the peer
selection process. Sharing this information is expected to benefit both =
end
users and network operators, resulting in better application performance =
and
more rational use of network resources.<o:p></o:p></span></p>

<p class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoPlainText><span lang=3DEN-US>Recently, a trend has emerged =
to combine
DECADE and ALTO technologies for content distribution. Among other =
topics, this
symposium will explore how these technologies can be combined to improve
network efficiency.<o:p></o:p></span></p>

<p class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoPlainText><span lang=3DEN-US>All of you are welcome to =
this meeting!
Everyone is encouraged to request a slot for your presentation. We also =
plan to
invite industrial and academic experts on related areas to give
presentations.&nbsp; The topics include but are not limited =
to:<o:p></o:p></span></p>

<p class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoPlainText><span lang=3DEN-US>(1)&nbsp;&nbsp;&nbsp;&nbsp; =
ISPs'
considerations/recent actions;<o:p></o:p></span></p>

<p class=3DMsoPlainText><span lang=3DEN-US>(2)&nbsp;&nbsp;&nbsp;&nbsp; =
Vendors' considerations/recent
actions;<o:p></o:p></span></p>

<p class=3DMsoPlainText><span lang=3DEN-US>(3)&nbsp;&nbsp;&nbsp;&nbsp;
Applications' needs;<o:p></o:p></span></p>

<p class=3DMsoPlainText><span lang=3DEN-US>(4)&nbsp;&nbsp;&nbsp;&nbsp; =
Business
models;<o:p></o:p></span></p>

<p class=3DMsoPlainText><span lang=3DEN-US>(5)&nbsp;&nbsp;&nbsp;&nbsp; =
General
solution;<o:p></o:p></span></p>

<p class=3DMsoPlainText><span lang=3DEN-US>(6)&nbsp;&nbsp;&nbsp;&nbsp; =
Key
technical aspects<o:p></o:p></span></p>

<p class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoPlainText><span lang=3DEN-US>The presentation requests and
presentation slides should be sent to the organizers of this meeting =
before
corresponding cut-off dates.<o:p></o:p></span></p>

<p class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoPlainText><span lang=3DEN-US>If you are interested in =
attending,
please send an email to the organizers as soon as possible so they may =
plan
meeting space and lunch accordingly.<o:p></o:p></span></p>

<p class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoPlainText><span =
lang=3DEN-US>Name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;Email<o:p></o:p></span></p>

<p class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoPlainText><span lang=3DEN-US>Haibin
Song&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;
<a =
href=3D"mailto:melodysong@huawei.com">melodysong@huawei.com</a><o:p></o:p=
></span></p>

<p class=3DMsoPlainText><span lang=3DEN-US>David
Bryan&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;
<a =
href=3D"mailto:dbryan@ethernot.org">dbryan@ethernot.org</a><o:p></o:p></s=
pan></p>

<p class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoPlainText><span lang=3DEN-US>Important dates and =
Information<o:p></o:p></span></p>

<p class=3DMsoPlainText><span =
lang=3DEN-US>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<o:p></o:p></sp=
an></p>

<p class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoPlainText><span lang=3DEN-US>Time
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;15
to 16&nbsp; November 2010 (next Monday and Tuesday after IETF 79 =
meeting)<o:p></o:p></span></p>

<p class=3DMsoPlainText><span =
lang=3DEN-US>Location&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;
Nanjing, China<o:p></o:p></span></p>

<p class=3DMsoPlainText><span lang=3DEN-US>Meeting
Venue&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Hotel information will be available soon<o:p></o:p></span></p>

<p class=3DMsoPlainText><span lang=3DEN-US>Cut-off date for slot
request&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 25 October =
2010<o:p></o:p></span></p>

<p class=3DMsoPlainText><span lang=3DEN-US>Preliminary =
agenda&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;
1 November&nbsp; 2010<o:p></o:p></span></p>

<p class=3DMsoPlainText><span lang=3DEN-US>Final
agenda&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
8 November 2010<o:p></o:p></span></p>

<p class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoPlainText><span lang=3DEN-US>Travel =
Information<o:p></o:p></span></p>

<p class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoPlainText><span lang=3DEN-US>(1) The air flight from =
Beijing to
Nanjing will take about 1 hour and 40 minutes<o:p></o:p></span></p>

<p class=3DMsoPlainText><span lang=3DEN-US>(2) The high speed train =
between
Shanghai and Nanjing will take about 1 hour and 18 minutes(non-stop =
train) or
about 2 hours (several stops).<o:p></o:p></span></p>

<p class=3DMsoPlainText><span lang=3DEN-US>(3) There are also =
international flights
to some Asia Pacific and Europe countries from =
Nanjing<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p>

</div>

</body>

</html>

------=_NextPart_000_007D_01CB5F62.DCBA9440--


From richih.mailinglist@gmail.com  Tue Sep 28 20:55:57 2010
Return-Path: <richih.mailinglist@gmail.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0C1633A6BB6 for <apps-discuss@core3.amsl.com>; Tue, 28 Sep 2010 20:55:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.475
X-Spam-Level: 
X-Spam-Status: No, score=-2.475 tagged_above=-999 required=5 tests=[AWL=0.124,  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 tLWq+VVEn2Gy for <apps-discuss@core3.amsl.com>; Tue, 28 Sep 2010 20:55:56 -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 66A273A6B5B for <apps-discuss@ietf.org>; Tue, 28 Sep 2010 20:55:53 -0700 (PDT)
Received: by iwn3 with SMTP id 3so592245iwn.31 for <apps-discuss@ietf.org>; Tue, 28 Sep 2010 20:56:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:from:date :message-id:subject:to:content-type; bh=D0eipKYiqAXbhnttcwVnMz40XaIWnx8qA+SlPWRyGHQ=; b=Tx/KoC4JvkdFvV0ViaISQGNXpBr2CwXGVxA2CMMNH4JpVvjOWisfBVJTq+eocop5Og bQO4g1Tm9ktJunKcDQfr3+C03ldl5AelFMrWg6d39N+dV4KXkHEVS6MS+VQMxb4rN1EF dhzaJcgvR6OQDkY3Ug/77E+32wpgl4Y37fdFY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=uYjluyWPofnUpMEWyDiQnvcSonQ/PT6kJf/KeOZKppvN81S/AMYO0/59SFHr7OBSlU o05mC2XoiJCByUyc5Gh5ENZhjIgKaHXTzuycmpPG7wqExP02SWtgX9c61HmlYj4DV6C0 Vwjthu4R+7cdsHQviDbl5NeyyiKa3EEzjgx34=
Received: by 10.231.190.75 with SMTP id dh11mr1005892ibb.189.1285732595481; Tue, 28 Sep 2010 20:56:35 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.231.156.16 with HTTP; Tue, 28 Sep 2010 20:56:14 -0700 (PDT)
From: Richard Hartmann <richih.mailinglist@gmail.com>
Date: Wed, 29 Sep 2010 05:56:14 +0200
Message-ID: <AANLkTi=yx8yRHwUgjj3uqPq1q21-9awxq8FujmcrwcAa@mail.gmail.com>
To: apps-discuss@ietf.org
Content-Type: text/plain; charset=UTF-8
Subject: Re: [apps-discuss] draft-hartmann-default-port-for-irc-via-tls-ssl
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Sep 2010 03:55:57 -0000

Hi all,

first of all, thanks to Peter for forwarding this before I got around to
do much in ways of announcing.

I am now susbcribed to this list so I will see all comments regarding
this I-D.

There have been some minor corrections, a stable link to the newest
version can be found at [1].

Finally, it has been suggested that I "upgrade" this I-D from
Individual. If there is a consensus that I should do this, I'll go ahead.
If not, I won't. I lack experience in this regard and depend on
feedback in such matters. I don't want to make any mistakes.

I am looking forward to any and all feedback.


Thanks,
Richard

[1] http://datatracker.ietf.org/doc/draft-hartmann-default-port-for-irc-via-tls-ssl/

From sm@resistor.net  Tue Sep 28 22:38:36 2010
Return-Path: <sm@resistor.net>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A15323A6E29 for <apps-discuss@core3.amsl.com>; Tue, 28 Sep 2010 22:38:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.608
X-Spam-Level: 
X-Spam-Status: No, score=-102.608 tagged_above=-999 required=5 tests=[AWL=-0.009, 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 ae0Fccz9YsIU for <apps-discuss@core3.amsl.com>; Tue, 28 Sep 2010 22:38:34 -0700 (PDT)
Received: from ns1.qubic.net (ns1.qubic.net [208.69.177.116]) by core3.amsl.com (Postfix) with ESMTP id 1B2C13A6E16 for <discuss@apps.ietf.org>; Tue, 28 Sep 2010 22:38:34 -0700 (PDT)
Received: from SUBMAN.resistor.net ([10.0.0.1]) (authenticated bits=0) by ns1.qubic.net (8.14.5.Alpha0/8.14.5.Alpha0) with ESMTP id o8T5d2Za026036 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 28 Sep 2010 22:39:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1285738755; x=1285825155; bh=3q4BIrqREyvZklu8VfwY9lR8uZWRDKjx+QR/f8JRunE=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=KKImPUrkabYmGJlLcb4E0Lc+dUB3sGFHH5qGSyBp2DTCffxRMePb8XGWD69HTShlW M7BvuMhgDJkLHhHQ/arY1OrN7L76T8t2HITh6PmKzooLFolQ5HXXX9O3KUVMayLXyi 5Fqt0gs5ZsiNglWS7YwR/hkDMAbvebPQ5MmOWkK0=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1285738755; x=1285825155; bh=3q4BIrqREyvZklu8VfwY9lR8uZWRDKjx+QR/f8JRunE=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=QwO4py254T7Yoaw3uAdR/e96lXDqM9FaeO+R5LpacB41aoYLfpN+BcIF0mhUG2CRM LKsChWW6PelWV6HSBd9Dv3uq6J1bNHZemWmjWNPARDm/Yvhq+90WP8qnRsoJv54Aze 6Lt7dX75/ETZKwydF/dLYRANfRO5XYtpK5CiIm6s=
DomainKey-Signature: a=rsa-sha1; s=mail; d=resistor.net; c=simple; q=dns; b=MP96BOT7sLTzURVDQZjKTe3ABEMfLv82PyWSDSO61Q1Kjwuk0YEUMQVCZOb1qrRQt oOoQrHVanVY0e1pIxb43Sao2J3afWKTodmjG6TzByDaYLKCvjxDjJGRi/BMN6vDk2iS dZHYXCu8JPVw4Q5Dv9vk0Gu46Ua6cU15hOA/GXs=
Message-Id: <6.2.5.6.2.20100928222414.0abb3710@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 28 Sep 2010 22:36:46 -0700
To: Mark Nottingham <mnot@mnot.net>
From: SM <sm@resistor.net>
In-Reply-To: <D92B699E-32AA-4CD8-94B8-469296A4D48B@mnot.net>
References: <D92B699E-32AA-4CD8-94B8-469296A4D48B@mnot.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: Apps Discuss <discuss@apps.ietf.org>
Subject: Re: [apps-discuss] IANA hanges to draft-nottingham-http-link-header
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Sep 2010 05:38:36 -0000

Hi Mark,
At 21:25 22-09-10, Mark Nottingham wrote:
>3) Adding the following to the beginning of section 6.2, "Link 
>Relation Type Registry":
>
>    The underlying registry data (e.g., the XML file) must include
>    Simplified BSD License text as described in Section 4.e of the Trust
>    Legal Provisions (<http://trustee.ietf.org/license-info>).

Why are you specifying a license for the registry?

Section 6.2.1 sets a hard limit for approving or denying 
registration.   There draft defines an appeal process.  That is 
usual.  Can't you leave these procedures to RFC 5226?

Regards,
-sm 


From mnot@mnot.net  Wed Sep 29 00:51:29 2010
Return-Path: <mnot@mnot.net>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D639B3A6E16 for <apps-discuss@core3.amsl.com>; Wed, 29 Sep 2010 00:51:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.051
X-Spam-Level: 
X-Spam-Status: No, score=-105.051 tagged_above=-999 required=5 tests=[AWL=-2.452, 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 IM917Yzzz+Ku for <apps-discuss@core3.amsl.com>; Wed, 29 Sep 2010 00:51:28 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by core3.amsl.com (Postfix) with ESMTP id 82C6F3A6D80 for <discuss@apps.ietf.org>; Wed, 29 Sep 2010 00:51:28 -0700 (PDT)
Received: from chancetrain-lm.mnot.net (unknown [118.209.143.94]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 758EE509DB; Wed, 29 Sep 2010 03:52:04 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <6.2.5.6.2.20100928222414.0abb3710@resistor.net>
Date: Wed, 29 Sep 2010 17:52:01 +1000
Content-Transfer-Encoding: quoted-printable
Message-Id: <BA2C6FE1-3940-4B85-981C-3FACA0E6085A@mnot.net>
References: <D92B699E-32AA-4CD8-94B8-469296A4D48B@mnot.net> <6.2.5.6.2.20100928222414.0abb3710@resistor.net>
To: SM <sm@resistor.net>
X-Mailer: Apple Mail (2.1081)
Cc: Apps Discuss <discuss@apps.ietf.org>
Subject: Re: [apps-discuss] IANA hanges to draft-nottingham-http-link-header
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Sep 2010 07:51:29 -0000

On 29/09/2010, at 3:36 PM, SM wrote:

> Hi Mark,
> At 21:25 22-09-10, Mark Nottingham wrote:
>> 3) Adding the following to the beginning of section 6.2, "Link =
Relation Type Registry":
>>=20
>>   The underlying registry data (e.g., the XML file) must include
>>   Simplified BSD License text as described in Section 4.e of the =
Trust
>>   Legal Provisions (<http://trustee.ietf.org/license-info>).
>=20
> Why are you specifying a license for the registry?

Because there was concern -- especially from the HTML community -- about =
it, because implementations need to incorporate the registry data and =
remain "clean" from an Open Source perspective.

We've been discussing this with IANA and the IESG Chair for a while; =
stay tuned.


> Section 6.2.1 sets a hard limit for approving or denying registration. =
  There draft defines an appeal process.  That is usual.  Can't you =
leave these procedures to RFC 5226?


I'm not sure what you're saying here. This text hasn't changed from the =
1st LC.

Regards,


--
Mark Nottingham     http://www.mnot.net/


From ietfc@btconnect.com  Wed Sep 29 02:01:23 2010
Return-Path: <ietfc@btconnect.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8223C3A6C68; Wed, 29 Sep 2010 02:01:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.088
X-Spam-Level: 
X-Spam-Status: No, score=-2.088 tagged_above=-999 required=5 tests=[AWL=0.511,  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 bXBNLHLtTk5m; Wed, 29 Sep 2010 02:01:22 -0700 (PDT)
Received: from mail.btconnect.com (c2beaomr08.btconnect.com [213.123.26.186]) by core3.amsl.com (Postfix) with ESMTP id AAB2F3A6C83; Wed, 29 Sep 2010 02:01:21 -0700 (PDT)
Received: from host217-44-4-171.range217-44.btcentralplus.com (HELO pc6) ([217.44.4.171]) by c2beaomr08.btconnect.com with SMTP id ABK61060; Wed, 29 Sep 2010 10:02:01 +0100 (BST)
Message-ID: <003b01cb5fac$85b2eae0$4001a8c0@gateway.2wire.net>
From: "t.petch" <ietfc@btconnect.com>
To: <apps-discuss@ietf.org>
References: <4CA22665.1090008@stpeter.im>
Date: Wed, 29 Sep 2010 10:01:24 +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.0A0B0302.4CA30088.029F, actions=tag
X-Junkmail-Status: score=10/50, host=c2beaomr08.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0207.4CA3008B.015F,ss=1,fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=single engine
X-Junkmail-IWF: false
Cc: iesg <iesg@ietf.org>
Subject: Re: [apps-discuss] WG Review: Applications Area Working Group(APPSAWG)
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Sep 2010 09:01:23 -0000

I think that the order of the list of considerations is unfortunate, as it might
be read as implying precedence.  I think that
(5) There is no existing related Working Group that is willing to
> recharter to take on this work, and the document doesn't justify the
> formation of a new working group.
should come top of the list.

And the reference to URI I find unclear - I see that activity best performed on
 uri@w3.org

Otherwise, yes, let's give it a try for nine months.

Tom Petch

----- Original Message -----
From: "Peter Saint-Andre" <stpeter@stpeter.im>
To: <apps-discuss@ietf.org>
Sent: Tuesday, September 28, 2010 7:31 PM
Subject: [apps-discuss] Fwd: WG Review: Applications Area Working Group(APPSAWG)


> FYI.
>
> -------- Original Message --------
> Subject: WG Review: Applications Area Working Group (APPSAWG)
> Date: Tue, 28 Sep 2010 10:30:02 -0700 (PDT)
> From: IESG Secretary <iesg-secretary@ietf.org>
> Reply-To: iesg@ietf.org
> To: ietf-announce@ietf.org
>
> A new IETF working group has been proposed in the Applications Area.  The
> IESG has not made any determination as yet. The following draft charter
> was submitted, and is provided for informational purposes only. Please
> send your comments to the IESG mailing list (iesg@ietf.org) by Tuesday,
> October 5, 2010.
>
> Applications Area Working Group (APPSAWG)
> ------------------------------------------
> Current Status: Proposed Working Group
> Last updated: 2010-09-24
>
> Chair(s): TBD
>
> Applications Area Directors:
>  Alexey Melnikov <alexey.melnikov@isode.com>
>  Peter Saint-Andre <stpeter@stpeter.im>
>
> Applications Area Advisor:
>  Alexey Melnikov <alexey.melnikov@isode.com>
>
> Mailing Lists: TBD
>
> Description of Working Group:
>
> The Applications Area Directors sometimes receives proposals for the
> development of specifications dealing with application-related topics
> that are not in scope for an existing working group and do not justify
> the formation of a new working group.
>
> The Applications Area Working Group (APPSAWG) can serve as a forum for
> such work in the IETF.  The APPSAWG accepts work items in accordance
> with the  consensus of the Working Group and the best judgment of the
> Applications Area Directors, who are responsible for updating the
> working group milestones as needed.  The working group meets if there
> are active proposals that require intensive discussion.
>
> Work items that are appropriate for the APPSAWG mostly fall under the
> following topics:
>
> (A) Well-defined security issues that are relevant to multiple
> application technologies (e.g., draft-saintandre-tls-server-id-check).
>
> (B) Small-scale additions to the protocol stack for HTTP and other
> application technologies, mostly related to service discovery and
> meta-data (e.g., RFC 5785, draft-nottingham-http-link-header, and
> draft-hammer-hostmeta).
>
> (C) Selected other work items addressing topics that historically fall
> within the Applications Area, such as calendaring, date and time
> formats, HTTP, internationalization, language tags, MIME, URIs and XML.
>
> When considering whether to accept a proposed work item, the APPSAWG and
> the Applications Area Directors shall take into account the following
> factors, among others:
>
> (1) Whether the WG has consensus on the suitability, importance, and
> projected quality of the proposed work item.
>
> (2) Whether there is core team of WG participants with sufficient energy
> and expertise to advance the proposed work item according to the
> proposed schedule.
>
> (3) Whether there are enough WG participants who are willing to review
> the work produced by the document authors or editors.
>
> (4) Whether the Area Directors judge that wider input is needed before
> accepting the proposed work item (e.g., from the IESG, IAB, or another
> standards development organization).
>
> (5) There is no existing related Working Group that is willing to
> recharter to take on this work, and the document doesn't justify the
> formation of a new working group.
>
> In order to evaluate success of this WG, it is deliberately limited in
> its duration. The WG needs to close or be rechartered to remove this
> restriction before July 2011.
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss


From sm@resistor.net  Wed Sep 29 02:08:50 2010
Return-Path: <sm@resistor.net>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0206E3A6CA8 for <apps-discuss@core3.amsl.com>; Wed, 29 Sep 2010 02:08:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.608
X-Spam-Level: 
X-Spam-Status: No, score=-102.608 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 6EznEXOLaApO for <apps-discuss@core3.amsl.com>; Wed, 29 Sep 2010 02:08:47 -0700 (PDT)
Received: from ns1.qubic.net (ns1.qubic.net [208.69.177.116]) by core3.amsl.com (Postfix) with ESMTP id D578C3A6C7C for <discuss@apps.ietf.org>; Wed, 29 Sep 2010 02:08:47 -0700 (PDT)
Received: from SUBMAN.resistor.net ([10.0.0.1]) (authenticated bits=0) by ns1.qubic.net (8.14.5.Alpha0/8.14.5.Alpha0) with ESMTP id o8T99Ju9028189 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 29 Sep 2010 02:09:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1285751369; x=1285837769; bh=Zp3S9yIVBQxzGQD8CmWZaIUBPk+yoP4ZK2lZuLW1AFs=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=VhvxKpCNvDMXM7Tmg2VWA/bdHn071ID1J2Wq5PS78HfXw576rszYPRXkRw1hnHxX3 MEdzfnVPdMWngQrc4Oh5SdkPTktpwrfz3kptDxQobcBUA8EbaoJ9EqYXamvCRzYhau o5yySPRPdO9l0jm4wg06rBNJerZb1mvyz4g4gIsg=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1285751369; x=1285837769; bh=Zp3S9yIVBQxzGQD8CmWZaIUBPk+yoP4ZK2lZuLW1AFs=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=00t/8HfUki3V/ChzGvAyU1eah2AgK+AH/C7zWVNGG1epagJTG8iLfl9irVxZP4DAH r5Q3cIHWnmZbZC+aY3yVUtXW+GxFvVaplPUq9jOiCXc5A2bENQmw5h17lehLx+nzz/ 0a2hQp+t2wrK6VJySY4C3KfyZmarLjnXyJFtiWgA=
DomainKey-Signature: a=rsa-sha1; s=mail; d=resistor.net; c=simple; q=dns; b=B8HWffSTHTaSgnv9wW3c43fCMbBo49BFYbrY3LHG0zuh4Ji0GHeUU2LFjPohANH0+ nMDOIVhAZDkGdxL3YZhpZh3dkZNkjY+oGb7ImWE7p8rV0mvQbLNnkpxhgoTxwQhkfvi z77wuHsTb74IV18ENTzRnQ04ez9gfK5hYS76w6I=
Message-Id: <6.2.5.6.2.20100929014507.0c7500b0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 29 Sep 2010 01:48:00 -0700
To: Mark Nottingham <mnot@mnot.net>
From: SM <sm@resistor.net>
In-Reply-To: <BA2C6FE1-3940-4B85-981C-3FACA0E6085A@mnot.net>
References: <D92B699E-32AA-4CD8-94B8-469296A4D48B@mnot.net> <6.2.5.6.2.20100928222414.0abb3710@resistor.net> <BA2C6FE1-3940-4B85-981C-3FACA0E6085A@mnot.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: Apps Discuss <discuss@apps.ietf.org>
Subject: Re: [apps-discuss] IANA hanges to draft-nottingham-http-link-header
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Sep 2010 09:08:50 -0000

Hi Mark,
At 00:52 29-09-10, Mark Nottingham wrote:
>Because there was concern -- especially from the HTML community -- 
>about it, because implementations need to incorporate the registry 
>data and remain "clean" from an Open Source perspective.

That's similar to the discussion about RFCs in the IETF Stream.

>I'm not sure what you're saying here. This text hasn't changed from 
>the 1st LC.

As the draft has already gone through a Last Call, please ignore this comment.

Regards,
-sm 


From duerst@it.aoyama.ac.jp  Wed Sep 29 02:52:47 2010
Return-Path: <duerst@it.aoyama.ac.jp>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 824D53A6DA6 for <apps-discuss@core3.amsl.com>; Wed, 29 Sep 2010 02:52:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.636
X-Spam-Level: 
X-Spam-Status: No, score=-98.636 tagged_above=-999 required=5 tests=[AWL=-1.305, BAYES_20=-0.74, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265,  J_CHICKENPOX_34=0.6, MIME_8BIT_HEADER=0.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 JtyBzLEjvnnW for <apps-discuss@core3.amsl.com>; Wed, 29 Sep 2010 02:52:46 -0700 (PDT)
Received: from scintmta01.scbb.aoyama.ac.jp (scintmta01.scbb.aoyama.ac.jp [133.2.253.33]) by core3.amsl.com (Postfix) with ESMTP id A935D3A6B8A for <apps-discuss@ietf.org>; Wed, 29 Sep 2010 02:52:45 -0700 (PDT)
Received: from scmse02.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta01.scbb.aoyama.ac.jp (secret/secret) with SMTP id o8T9rNFi029804 for <apps-discuss@ietf.org>; Wed, 29 Sep 2010 18:53:23 +0900
Received: from (unknown [133.2.206.133]) by scmse02.scbb.aoyama.ac.jp with smtp id 5af2_51a1_659291ec_cbaf_11df_8c32_001d096c5782; Wed, 29 Sep 2010 18:53:22 +0900
Received: from [IPv6:::1] ([133.2.210.1]:43354) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S1457985> for <apps-discuss@ietf.org> from <duerst@it.aoyama.ac.jp>; Wed, 29 Sep 2010 18:53:21 +0900
Message-ID: <4CA30C90.6080505@it.aoyama.ac.jp>
Date: Wed, 29 Sep 2010 18:53:20 +0900
From: =?UTF-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: draft-ietf-geopriv-policy@tools.ietf.org
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: [apps-discuss] Apps-team review of	draft-ietf-geopriv-policy-21
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Sep 2010 09:52:47 -0000

Hello,

I have been selected as the Applications Area Review Team reviewer for 
this draft (for background on apps-review, please see 
<http://www.apps.ietf.org/content/applications-area-review-team>).

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

Document: draft-ietf-geopriv-policy-21
Title: Geolocation Policy: A Document Format for Expressing Privacy
        Preferences for Location Information
Reviewer: Martin Dürst
Review Date: 2010-09-26

Summary: No major issue; minor issues that may benefit from fixing

MAJOR ISSUES: None that I found. I have just read through the draft 
itself, but in no way tried to look at the long history of this draft, 
or the discusses in the datatracker, and I do in no way want to claim 
that I understand much of geopriv or the surrounding policy framework.

MINOR ISSUES (These are issues that would benefit from clarification, or 
that might be done in a somewhat better way for another spec in the 
future, unless somebody thinks they need to be escalated):

- The Copyright notice doesn't have a pre-November 10, 2008 exception
   clause. Given the age of the document, I'd have assumed it needs one,
   but it's up to the authors to know what works here.

- Section 2, Terminology: "Presentity or Target" and
   "Watcher or Location Recipient": Defining two parallel terms is
   confusing. Better define one term for use in the document, and mention
   as part of the definition that the other term is also used in some
   contexts.

- Section 4 says that a <location-condition> element evaluates to TRUE
   if any of its child elements are true, i.e., *a logical OR*.
   It would be very helpful if the explanation in terms of logical ANDs
   or ORs would be added to the other places where such logical
   operations take place.

- Section 4: "the location profile that *is* included as child
   element*s*": Singular/plural mismatch

- Section 4: lt;location>: conversion error from XML?

- Section 4: using the xml:lang to describe the language of attribute
   values is not exactly forbidden, but also not recommended, ond not
   future-proof (think about adding another attribute that might need
   different language information). Best practice is to change any
   attributes that contain natural-language content into elements.

- Section 4: Better add a reference to BCP 47 for language tags.

- Section 4: "If an extension is not understood by the entity
   evaluating the rules then this rule evaluates to FALSE.":
   Does this apply to the unknown extension element itself, or
   to the element that contains this extension element? This should
   be clarified. Also, "The <location-condition> and the <location>
   elements provide extension points." should be clarified by saying
   how these extension points are provided (e.g. via some attribute
   values, new attributes, contained elements, or whatever).

- Section 4.1: "if .. is *within* the described location.": as locations
   can be described e.g. by polygons,..., it should say either
   *fully within* or *partially within* or some such.

- Section 4.1: "If the geodetic
   location of the Target is unknown then the <location> element
   containing the information for the geodetic location profile
   evaluates to FALSE.": Does that mean that it is impossible to
   express the fact that I want 'unknown' locations to be transferred
   through? (This would allow the distinction between "I'm currently
   at a location I don't want to tell you" and "no information
   available", which in some cases may be something that the
   originator of the information wants to reveal.)

- Section 4.2: "The child element evaluates to TRUE if
   the two values are identical based on a *bit-by-bit* comparison.":
   XML doesn't transport bits, only Unicode codepoints. This should
   say "based on a *codepoint-by-codepoint comparison*".

- Section 4.2: "i.e., geocode the location": For all I'm aware,
   geocoding refers to the translation from civic location (such
   as addresses,...) to geodetic location, not the other way around
   as implied here.

- Section 6.2: "seconds are added to the current *date*": How do I add
   e.g. 5 seconds to a date such as 2010-09-29? Shouldn't this say
   "seconds are added to the current *time*"? (the fact that the Unix
   date command gives date and time, whereas the time command does
   something else altogether is irrelevant here :-)

- Section 6.2: "then the value MUST be set to the current date":
   If a date is really only a date, then this would mean that expiry
   would depend highly on the time within the day, and therefore the
   timezone. If it is a date-time, then it would mean immediate
   expiry, which could mean that there is no chance to forward this
   data to anybody assuming that forwarding takes some non-zero
   amount of time. Is this really what's intended?

- Section 6.3: "The value provided with the <set-note-well> element 
contains a
    privacy statement as a human readable text string and an 'xml:lang'
    attribute *denotes* the language of the human readable text.":
    denotes -> denoting?

- Section 6.3: If different parties involved understand different
   lanugages, what's the language to choose for the <note-well>?

- Section 6.5.1: The split into country/region/city/building/full
   may work very well for the US, but to what extent has it been
   checked that this split makes sense for other locations?

- Section 7.1: Given that address data is compared literally,
   the choice of example exposes a basic problem: How can e.g.
   <A3>Munich</A3> be matched with <A3>München</A3>,...? Is there
   some convention that the data and rules have to be in English
   (that would be very limiting)? Is there a way to write rules
   that match both Munich and München, in the logically expected
   way? Please explain.

- Section 7.4: There is a long example with three namespaces.
   In general, it is totally unnecessary to create a separate
   namepace for every minor extension and addition. For example,
   something like
   <gp:provide-location><lp:provide-geo>
   with two separate namespaces seems totally over-engineered.
   Better to make sure elements from extensions don't overlap,
   and to the extent they don't overlap, put them in the same
   namespace. This will make stuff shorter and easier to read.

- Section 10.7: "will look for all documents within http://.../foo":
   The HTTP protocol doesn't provide a way to enumerate all documents
   within a certain URI (and the URI doesn't terminate with a slash,
   so it's not even a directory). If this is XCAP-specific functionality,
   then please slightly rewrite to make it easier to understand for
   outsiders.

- Section 11.3: "Profile names are XML tokens": The XML spec talks about
   Nmtokens (name tokens). That's the closest to "tokens" that I was able
   to find. It should be clarified, also in the respect that the "are"
   should be replaced by something that makes clear that this is a
   syntax restriction, not something on a semantic level.

- Section 12: "to understand UTF-8 and UTF-16 encodings": reword,
   e.g. to "to understand UTF-8 and UTF-16" or to "to understand the
   UTF-8 and UTF-16 character encodings".

- Section 13: "a discussion of generic security threats": make clear in
   which respect these are 'generic'

- Section 13: "For example, when a transformation...": incomplete
   sentence.

- Section 13: "a random number to is added to": remove first 'to'

- Section 13, 4th paragraph: This would be much easier to understand
   with an example or two.

- Section 13: "Users might create policies that are non-sensical.":
   What does that mean? How is software supposed to perform consistency
   checks if the only thing we know is that we want to guard against
   'non-sensical'?

- [ifip07]: change to [ardanga07] for consistency?

- Appendix A: Why are there email addresses for some of the people
   listed here? So that we can complain to them (rather than the
   authors?) about errors in the document? Also, an 'and' is missing
   before the last person.

Regards,    Martin.

-- 
#-# Martin J. Dürst, Professor, Aoyama Gakuin University
#-# http://www.sw.it.aoyama.ac.jp   mailto:duerst@it.aoyama.ac.jp

From jari.arkko@piuha.net  Wed Sep 29 03:03:54 2010
Return-Path: <jari.arkko@piuha.net>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9A3DE3A6EB5; Wed, 29 Sep 2010 03:03:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.442
X-Spam-Level: 
X-Spam-Status: No, score=-102.442 tagged_above=-999 required=5 tests=[AWL=0.157, 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 pR00WiavbJnD; Wed, 29 Sep 2010 03:03:53 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id 095F03A6E9B; Wed, 29 Sep 2010 03:03:53 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 9F0BF2CC3C; Wed, 29 Sep 2010 13:04:35 +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 3gqzwbYiJGc5; Wed, 29 Sep 2010 13:04:34 +0300 (EEST)
Received: from [IPv6:::1] (unknown [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 86BCD2CC30; Wed, 29 Sep 2010 13:04:34 +0300 (EEST)
Message-ID: <4CA30F32.8080000@piuha.net>
Date: Wed, 29 Sep 2010 13:04:34 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.24 (X11/20100411)
MIME-Version: 1.0
To: S Moonesamy <sm+ietf@elandsys.com>
References: <6.2.5.6.2.20100928130147.0cb0c870@elandnews.com>
In-Reply-To: <6.2.5.6.2.20100928130147.0cb0c870@elandnews.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Wed, 29 Sep 2010 08:02:12 -0700
Cc: Mark Townsley <townsley@cisco.com>, iesg@ietf.org, apps-discuss@ietf.org
Subject: Re: [apps-discuss] Apps-team review of draft-arkko-townsley-coexistence-04
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Sep 2010 10:03:54 -0000

Thanks for your comments. We will take your suggestions into account in 
a new version. The change to the introduction section had already been 
done due to some earlier comments. (But only in local copy, not 
submitted yet.)

Jari

S Moonesamy kirjoitti:
> Hello,
>
> I have been selected as the Applications Area Review Team reviewer for 
> this draft (for background on apps-review, please see 
> http://www.apps.ietf.org/content/applications-area-review-team).
>
> Please resolve these comments along with any other Last Call comments 
> you may receive. Please wait for direction from your document shepherd 
> or AD before posting a new version of the draft.
>
> Document: draft-arkko-townsley-coexistence-04
> Reviewer: S. Moonesamy
> Review Date: September 28, 2010
> IETF Last Call Date: September 13, 2010
> IESG Telechat Date: Unknown
>
> Summary:
>
> This draft is almost ready for publication as a RFC but has a few 
> issues that should be fixed before publication.  Please refer to the 
> comment about the intended status.  The Introduction Section does not 
> reflect the text in the Abstract Section which mentions that the 
> document is being published to reflect the thinking at the time (2008).
>
> Major Issues:
>
> None
>
> Minor Issues:
>
> According to the Abstract Section:
>
>   "This document was originally created as input to the Montreal co-
>    existence interim meeting in October 2008, which led to the
>    rechartering of the Behave and Softwire working groups to take on new
>    IPv4 and IPv6 coexistence work.  This document is published as a
>    historical record of the thinking at the time."
>
> The Introduction Section should be updated to reflect what the 
> document seeks to represent, i.e. the thinking in 2008.
>
> In the Security Considerations Section:
>
>   "It is important to note that some of the solutions may have impacts
>    on how IPsec or DNS Security can work through translation devices."
>
> I suggest adding application protocols to that as the solutions may 
> have an impact on them.
>
> Nits:
>
> The intended status of this I-D is Informational.  The Abstract 
> Section mentions that:
>
>   "This document is published as a historical record of the thinking 
> at the time."
>
> In Section 2.1, please expand "GW" on first use.  In Section 2.1.2, 
> please expand "ALGs" on first use.
>
> Regards,
> S. Moonesamy
>
>


From ted.ietf@gmail.com  Wed Sep 29 09:40:23 2010
Return-Path: <ted.ietf@gmail.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 381C43A6EEE; Wed, 29 Sep 2010 09:40:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.73
X-Spam-Level: 
X-Spam-Status: No, score=-1.73 tagged_above=-999 required=5 tests=[AWL=0.269,  BAYES_00=-2.599, J_CHICKENPOX_15=0.6]
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 Nma7UWaokp7g; Wed, 29 Sep 2010 09:40:19 -0700 (PDT)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by core3.amsl.com (Postfix) with ESMTP id 89EAA3A6EF2; Wed, 29 Sep 2010 09:40:17 -0700 (PDT)
Received: by qyk31 with SMTP id 31so1336795qyk.10 for <multiple recipients>; Wed, 29 Sep 2010 09:40:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=xiv29PGOyZOLXhHLnApGf89KYPaMabalr7vukX2VmUM=; b=qNjRYupTWa0e04TKGD2RpaFCBBItAEe1h6GxqA/u3uKjoOYXYvAQRqc8rKFzp8J2SA wHvSGt4Guk1+A5j/JoOarOkEtC0TwPZk4F4siKh1UFfmaoKjGNr0uDpf/0mO6N+e97lx IMC36QFBbyd0Gi7oUtfXquaRs1XNuE6Z1eUuk=
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=Arxm28aMquWhbmkjWPBciVWJBsJBTyYGHT8L1MDrFwCEKMyN7lmE/Up8HhhWmmLIzw VqqjaBM+z7f7gkJY0r63xOnf7RDG8Fwy4rcCDkk4AUhJ0hroTeD2QBO28+Tz/AMzcymL Yxw0x3kAuwsIEdD701a47RzybeRhnWpTu6a0o=
MIME-Version: 1.0
Received: by 10.224.45.195 with SMTP id g3mr1433627qaf.56.1285778451614; Wed, 29 Sep 2010 09:40:51 -0700 (PDT)
Received: by 10.229.249.208 with HTTP; Wed, 29 Sep 2010 09:40:51 -0700 (PDT)
In-Reply-To: <003b01cb5fac$85b2eae0$4001a8c0@gateway.2wire.net>
References: <4CA22665.1090008@stpeter.im> <003b01cb5fac$85b2eae0$4001a8c0@gateway.2wire.net>
Date: Wed, 29 Sep 2010 09:40:51 -0700
Message-ID: <AANLkTingsAq7sWXMLmX0RFiXLHO_r_qXofjRbzJto7_U@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
To: "t.petch" <ietfc@btconnect.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: iesg <iesg@ietf.org>, apps-discuss@ietf.org
Subject: Re: [apps-discuss] WG Review: Applications Area Working Group(APPSAWG)
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Sep 2010 16:40:23 -0000

On Wed, Sep 29, 2010 at 1:01 AM, t.petch <ietfc@btconnect.com> wrote:
> I think that the order of the list of considerations is unfortunate, as i=
t might
> be read as implying precedence. =A0I think that
> (5) There is no existing related Working Group that is willing to
>> recharter to take on this work, and the document doesn't justify the
>> formation of a new working group.
> should come top of the list.
>
> And the reference to URI I find unclear - I see that activity best perfor=
med on
> =A0uri@w3.org

Hi Tom,

I think you're right that uri@w3.org would be the right place to
discuss something
about the evolution of URIs.  The IRI working group is the right place
to discuss the
internationalization issues there, and uri-review@ietf.org the right
place to propose
a new scheme.  But when I saw "URIs and XML", I assumed that this working
group would cover questions of how to apply them in a specific
context, rather than
taking on work to change them.  If it did run across something that
needed a major
change, it would likely be moved off into a different (or new) group.

Does that match others' expectations?

regards,

Ted

>
> Otherwise, yes, let's give it a try for nine months.
>
> Tom Petch
>
> ----- Original Message -----
> From: "Peter Saint-Andre" <stpeter@stpeter.im>
> To: <apps-discuss@ietf.org>
> Sent: Tuesday, September 28, 2010 7:31 PM
> Subject: [apps-discuss] Fwd: WG Review: Applications Area Working Group(A=
PPSAWG)
>
>
>> FYI.
>>
>> -------- Original Message --------
>> Subject: WG Review: Applications Area Working Group (APPSAWG)
>> Date: Tue, 28 Sep 2010 10:30:02 -0700 (PDT)
>> From: IESG Secretary <iesg-secretary@ietf.org>
>> Reply-To: iesg@ietf.org
>> To: ietf-announce@ietf.org
>>
>> A new IETF working group has been proposed in the Applications Area. =A0=
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,
>> October 5, 2010.
>>
>> Applications Area Working Group (APPSAWG)
>> ------------------------------------------
>> Current Status: Proposed Working Group
>> Last updated: 2010-09-24
>>
>> Chair(s): TBD
>>
>> Applications Area Directors:
>> =A0Alexey Melnikov <alexey.melnikov@isode.com>
>> =A0Peter Saint-Andre <stpeter@stpeter.im>
>>
>> Applications Area Advisor:
>> =A0Alexey Melnikov <alexey.melnikov@isode.com>
>>
>> Mailing Lists: TBD
>>
>> Description of Working Group:
>>
>> The Applications Area Directors sometimes receives proposals for the
>> development of specifications dealing with application-related topics
>> that are not in scope for an existing working group and do not justify
>> the formation of a new working group.
>>
>> The Applications Area Working Group (APPSAWG) can serve as a forum for
>> such work in the IETF. =A0The APPSAWG accepts work items in accordance
>> with the =A0consensus of the Working Group and the best judgment of the
>> Applications Area Directors, who are responsible for updating the
>> working group milestones as needed. =A0The working group meets if there
>> are active proposals that require intensive discussion.
>>
>> Work items that are appropriate for the APPSAWG mostly fall under the
>> following topics:
>>
>> (A) Well-defined security issues that are relevant to multiple
>> application technologies (e.g., draft-saintandre-tls-server-id-check).
>>
>> (B) Small-scale additions to the protocol stack for HTTP and other
>> application technologies, mostly related to service discovery and
>> meta-data (e.g., RFC 5785, draft-nottingham-http-link-header, and
>> draft-hammer-hostmeta).
>>
>> (C) Selected other work items addressing topics that historically fall
>> within the Applications Area, such as calendaring, date and time
>> formats, HTTP, internationalization, language tags, MIME, URIs and XML.
>>
>> When considering whether to accept a proposed work item, the APPSAWG and
>> the Applications Area Directors shall take into account the following
>> factors, among others:
>>
>> (1) Whether the WG has consensus on the suitability, importance, and
>> projected quality of the proposed work item.
>>
>> (2) Whether there is core team of WG participants with sufficient energy
>> and expertise to advance the proposed work item according to the
>> proposed schedule.
>>
>> (3) Whether there are enough WG participants who are willing to review
>> the work produced by the document authors or editors.
>>
>> (4) Whether the Area Directors judge that wider input is needed before
>> accepting the proposed work item (e.g., from the IESG, IAB, or another
>> standards development organization).
>>
>> (5) There is no existing related Working Group that is willing to
>> recharter to take on this work, and the document doesn't justify the
>> formation of a new working group.
>>
>> In order to evaluate success of this WG, it is deliberately limited in
>> its duration. The WG needs to close or be rechartered to remove this
>> restriction before July 2011.
>> _______________________________________________
>> apps-discuss mailing list
>> apps-discuss@ietf.org
>> https://www.ietf.org/mailman/listinfo/apps-discuss
>
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss
>

From A.Hoenes@TR-Sys.de  Wed Sep 29 12:57:06 2010
Return-Path: <A.Hoenes@TR-Sys.de>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CE0853A6CB9 for <apps-discuss@core3.amsl.com>; Wed, 29 Sep 2010 12:57:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.051
X-Spam-Level: 
X-Spam-Status: No, score=-98.051 tagged_above=-999 required=5 tests=[AWL=0.698, BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, HELO_EQ_DE=0.35, MIME_8BIT_HEADER=0.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 KLSBIsGahsSZ for <apps-discuss@core3.amsl.com>; Wed, 29 Sep 2010 12:57:06 -0700 (PDT)
Received: from TR-Sys.de (gateway.tr-sys.de [213.178.172.147]) by core3.amsl.com (Postfix) with ESMTP id 0E32D3A6DB3 for <apps-discuss@ietf.org>; Wed, 29 Sep 2010 12:56:08 -0700 (PDT)
Received: from ZEUS.TR-Sys.de by w. with ESMTP ($Revision: 1.37.109.26 $/16.3.2) id AA249709836; Wed, 29 Sep 2010 21:50:36 +0200
Received: (from ah@localhost) by z.TR-Sys.de (8.9.3 (PHNE_25183)/8.7.3) id VAA12840; Wed, 29 Sep 2010 21:49:34 +0200 (MESZ)
From: Alfred =?hp-roman8?B?SM5uZXM=?= <ah@TR-Sys.de>
Message-Id: <201009291949.VAA12840@TR-Sys.de>
To: apps-discuss@ietf.org
Date: Wed, 29 Sep 2010 21:49:34 +0200 (MESZ)
X-Mailer: ELM [$Revision: 1.17.214.3 $]
Mime-Version: 1.0
Content-Type: text/plain; charset=hp-roman8
Content-Transfer-Encoding: 8bit
Cc: iesg@ietf.com
Subject: Re: [apps-discuss] WG Review: Applications Area Working Group(APPSAWG)
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Sep 2010 19:57:06 -0000

At Wed, 29 Sep 2010 10:01:24 +0200, Tom Petch wrote:

> I think that the order of the list of considerations is
> unfortunate, as it might be read as implying precedence.
> I think that
>
> (5) There is no existing related Working Group that is willing to
>     recharter to take on this work, and the document doesn't justify
>     the formation of a new working group.
>
> should come top of the list.

The draft charter says in the leading clause of that list:

| When considering whether to accept a proposed work item, the APPSAWG
| and the Applications Area Directors shall take into account the
| following factors, among others:

This clearly means the list presents a conjunction (all conditions
must be met), and it it non-exhaustive.
"AND" is commutative and associative.  So the order doesn't matter.
Thus, the APPSAWG chairs and the APP ADs have to consider all items.

It'll be a strategic puzzle in each case to choose the order of checks
that is likely to minimize the work (if the sublime expectation is
failure) -- similarly as when a compiler or interpreter has to perform
some guesswork when it has to serialize a conjunctive expression,
based on some expectation on which term might lead to a negative answer
most likely, and the amount of work to determine the truth value of
each conjunctive term.  :-)


> ...
>
> Otherwise, yes, let's give it a try for nine months.

+1    (As already expressed in Maastricht.)


At Wed, 29 Sep 2010 09:40:51 -0700, Ted Hardie wrote,
regarding the point (dropped above) on URI matter:

>       ...  If it did run across something that needed a major
> change, it would likely be moved off into a different (or new) group.
>
> Does that match others' expectations?

Yes!   (At least mine.)


Kind regards,
  Alfred HÎnes.

-- 

+------------------------+--------------------------------------------+
| TR-Sys Alfred Hoenes   |  Alfred Hoenes   Dipl.-Math., Dipl.-Phys.  |
| Gerlinger Strasse 12   |  Phone: (+49)7156/9635-0, Fax: -18         |
| D-71254  Ditzingen     |  E-Mail:  ah@TR-Sys.de                     |
+------------------------+--------------------------------------------+


From barryleiba.mailing.lists@gmail.com  Thu Sep 30 11:41:01 2010
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 500123A6E4E for <apps-discuss@core3.amsl.com>; Thu, 30 Sep 2010 11:41:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.457
X-Spam-Level: 
X-Spam-Status: No, score=-101.457 tagged_above=-999 required=5 tests=[AWL=-0.080, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_15=0.6, 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 NokyAOo7BzG9 for <apps-discuss@core3.amsl.com>; Thu, 30 Sep 2010 11:41:00 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by core3.amsl.com (Postfix) with ESMTP id 3D9D13A6E5D for <apps-discuss@ietf.org>; Thu, 30 Sep 2010 11:41:00 -0700 (PDT)
Received: by ywk9 with SMTP id 9so923427ywk.31 for <apps-discuss@ietf.org>; Thu, 30 Sep 2010 11:41:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:content-type:content-transfer-encoding; bh=OydW4yZ5hGQLH04HZ6QJz/RoCgL682zcTmoxw5fCk+U=; b=flXu4pAKDgPdjKlqeyBc0erb7KkhzvqTRXFVJ77vIJbp3e4Qlf2szLc/rAaETKZ935 kL+boK+peAoH0mGVvXvfAt450yq/BjBeqZ085b/KDxRJyyFBzy8jSMRO2gHvynATS01B JNWf+i3wIeAYVcL0RgkldLOJ3EaFFFzuj8SzA=
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 :content-transfer-encoding; b=KpuY0oWvkb1Pr/58HicGq4WZe5METuD9LBj0RuLgppziJNpdYvAafTn6zLKnX6OUYm MkMI+v8MqoNglf0flWNS6AgrWZWDJWXRAel5ej5aqgekz2dbdpz9S3sWASaj/aBTMdJZ CzMSuL0AThJlWtsV/QhbhZMa+vN0DAdWHSHrk=
MIME-Version: 1.0
Received: by 10.42.7.133 with SMTP id e5mr5192312ice.9.1285872104018; Thu, 30 Sep 2010 11:41:44 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.42.3.75 with HTTP; Thu, 30 Sep 2010 11:41:43 -0700 (PDT)
In-Reply-To: <201009291949.VAA12840@TR-Sys.de>
References: <201009291949.VAA12840@TR-Sys.de>
Date: Thu, 30 Sep 2010 14:41:43 -0400
X-Google-Sender-Auth: WuQelXYEBvxaVAuzfNdiDkhsIU0
Message-ID: <AANLkTi=vCeV8MdtRajSfEiUhxuP7bov5XyvTKzhqn92g@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: apps-discuss@ietf.org, iesg@ietf.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [apps-discuss] WG Review: Applications Area Working Group(APPSAWG)
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Sep 2010 18:41:01 -0000

On Wed, Sep 29, 2010 at 12:40 PM, Ted Hardie <ted.ietf@gmail.com> wrote:
> On Wed, Sep 29, 2010 at 1:01 AM, t.petch <ietfc@btconnect.com> wrote:
>> And the reference to URI I find unclear - I see that activity best perfo=
rmed on
>> =A0uri@w3.org
...
> But when I saw "URIs and XML", I assumed that this working
> group would cover questions of how to apply them in a specific
> context, rather than taking on work to change them. =A0If it did run
> across something that needed a major
> change, it would likely be moved off into a different (or new) group.
>
> Does that match others' expectations?

Yes, it does.

On Wed, Sep 29, 2010 at 3:49 PM, Alfred H=CEnes <ah@tr-sys.de> wrote:
> At Wed, 29 Sep 2010 10:01:24 +0200, Tom Petch wrote:
>> I think that the order of the list of considerations is
>> unfortunate, as it might be read as implying precedence.
...
> This clearly means the list presents a conjunction (all conditions
> must be met), and it it non-exhaustive.
> "AND" is commutative and associative. =A0So the order doesn't matter.
> Thus, the APPSAWG chairs and the APP ADs have to consider all items.

Still, it makes sense to put the primary concerns at the top.  It
might also make sense to use an unordered list (with "*") instead of
an ordered one (with numbers), just to be clear that it's neither
explicitly ordered nor exhaustive.

Barry
