Re: [ietf-outcomes] Apps area

Dave CROCKER <dhc@dcrocker.net> Sat, 06 February 2010 18:23 UTC

Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf-outcomes@core3.amsl.com
Delivered-To: ietf-outcomes@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 723D328C127 for <ietf-outcomes@core3.amsl.com>; Sat, 6 Feb 2010 10:23:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.571
X-Spam-Level:
X-Spam-Status: No, score=-6.571 tagged_above=-999 required=5 tests=[AWL=0.028, 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 6YMs2-P2-PdF for <ietf-outcomes@core3.amsl.com>; Sat, 6 Feb 2010 10:23:03 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id 49C3128C125 for <ietf-outcomes@ietf.org>; Sat, 6 Feb 2010 10:23:03 -0800 (PST)
Received: from [192.168.1.43] (adsl-68-122-70-87.dsl.pltn13.pacbell.net [68.122.70.87]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id o16INriQ001661 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 6 Feb 2010 10:23:58 -0800
Message-ID: <4B6DB3B1.9080806@dcrocker.net>
Date: Sat, 06 Feb 2010 10:23:45 -0800
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.1.7) Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
To: Mark Nottingham <mnot@mnot.net>
References: <67F17703-EAFC-425B-BBFE-79ED2ED212AC@mnot.net>
In-Reply-To: <67F17703-EAFC-425B-BBFE-79ED2ED212AC@mnot.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV 0.92/10362/Fri Feb 5 23:14:06 2010 on sbh17.songbird.com
X-Virus-Status: Clean
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Sat, 06 Feb 2010 10:23:58 -0800 (PST)
Cc: ietf-outcomes@ietf.org
Subject: Re: [ietf-outcomes] Apps area
X-BeenThere: ietf-outcomes@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF Outcomes Wiki discussion list <ietf-outcomes.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-outcomes>, <mailto:ietf-outcomes-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-outcomes>
List-Post: <mailto:ietf-outcomes@ietf.org>
List-Help: <mailto:ietf-outcomes-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-outcomes>, <mailto:ietf-outcomes-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Feb 2010 18:23:04 -0000

On 2/4/2010 4:29 PM, Mark Nottingham wrote:
> A couple of thoughts on looking at the APPs area page:
>
>   - URI is listed as '+'; surely that's '++>' (considering that people are now building URI-based protocols?)

I have to admit to my having a contnuing confusion about URL vs. URI, which 
makes it difficult for me to see whether the massive adoption is for URLs or is 
in fact for URIs.


>   - HTTP is defined by RFC2616, not RFC2068
>
> Anyone mind if I fix these and fill in a few other bits (e.g., for Atom)? I'm assuming the usual wiki terms of engagement apply, but wanted to make sure...

fix away, please!

d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net