Re: [hybi] hybi-09 refs

Ian Fette (イアンフェッティ) <ifette@google.com> Sat, 18 June 2011 22:44 UTC

Return-Path: <ifette@google.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CBBC21F856A for <hybi@ietfa.amsl.com>; Sat, 18 Jun 2011 15:44:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.843
X-Spam-Level:
X-Spam-Status: No, score=-104.843 tagged_above=-999 required=5 tests=[AWL=-0.833, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4, SARE_HTML_USL_OBFU=1.666, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GdMFqKuzYqt7 for <hybi@ietfa.amsl.com>; Sat, 18 Jun 2011 15:44:45 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.67]) by ietfa.amsl.com (Postfix) with ESMTP id 2048D21F856B for <hybi@ietf.org>; Sat, 18 Jun 2011 15:44:44 -0700 (PDT)
Received: from wpaz33.hot.corp.google.com (wpaz33.hot.corp.google.com [172.24.198.97]) by smtp-out.google.com with ESMTP id p5IMih7N014656 for <hybi@ietf.org>; Sat, 18 Jun 2011 15:44:43 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1308437083; bh=099r6PSeVQx1Slx1P1Djs4Ju3jE=; h=MIME-Version:Reply-To:In-Reply-To:References:Date:Message-ID: Subject:From:To:Cc:Content-Type; b=uwmrT33AIPBJ9HwMVs2eC1Lolx+bj+dgUZ8vpGtfhJduOrZlpmH6x3r5mtlOD7KDe 4Jfz+LKlnwx3EOv6xN9LA==
Received: from iyl8 (iyl8.prod.google.com [10.241.51.200]) by wpaz33.hot.corp.google.com with ESMTP id p5IMifE3030017 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <hybi@ietf.org>; Sat, 18 Jun 2011 15:44:42 -0700
Received: by iyl8 with SMTP id 8so3859598iyl.0 for <hybi@ietf.org>; Sat, 18 Jun 2011 15:44:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:mime-version:reply-to:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=aek7qx2AQxLRCZRneFjADCyKmEhbIZqZFBTjmVRignY=; b=ABw3UmEPsSw9fNcPgY4H8IQvjj9ZVL2CcQWZWQFuuuPGA2ldLURH+jwg55m7ZSuu1b ljX1ogRcSjjkAsnltEKw==
DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; b=K+qQdEGo8v7RZ+++qRnkSCFxPK6qkLjk9RvIYpLeTTtUdfWT4ECGZ0Q4wkHZP0Mcv1 fk3+o9ygNIueEGBvW61Q==
MIME-Version: 1.0
Received: by 10.231.60.73 with SMTP id o9mr3461715ibh.33.1308437081530; Sat, 18 Jun 2011 15:44:41 -0700 (PDT)
Received: by 10.231.33.8 with HTTP; Sat, 18 Jun 2011 15:44:41 -0700 (PDT)
In-Reply-To: <4DFC7A25.3060403@gmx.de>
References: <4DFC7A25.3060403@gmx.de>
Date: Sat, 18 Jun 2011 15:44:41 -0700
Message-ID: <BANLkTin93iRWq8eXf4y7XUfs1Vub+6DeKw@mail.gmail.com>
From: "Ian Fette (イアンフェッティ)" <ifette@google.com>
To: Julian Reschke <julian.reschke@gmx.de>
Content-Type: multipart/alternative; boundary="0015176f0d2874a08a04a6043f01"
X-System-Of-Record: true
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] hybi-09 refs
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ifette@google.com
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hybi>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 18 Jun 2011 22:44:46 -0000

Julian, for the REC-wsc-ui, I used what came from
http://xml.resource.org/public/rfc/bibxml4/ - specifically
http://xml.resource.org/public/rfc/bibxml4/reference.W3C.REC-wsc-ui-20100812.xml

I'm not entirely familiar with the formats and conventions, but if something
is amiss, perhaps you can get the maintainer of that database to make
necessary changes there so that others benefit as well?


On Sat, Jun 18, 2011 at 3:12 AM, Julian Reschke <julian.reschke@gmx.de>wrote:

> Reference check yields:
>
> Normative References:
> ANSI.X3-4.1986: not checked
> FIPS.180-2.2002: not checked
> RFC1951: [INFORMATIONAL] ok
> RFC2119: [BEST CURRENT PRACTICE] (-> BCP0014) ok
> RFC2616: [DRAFT STANDARD] ok
> RFC2817: [PROPOSED STANDARD] ok
> RFC2818: [INFORMATIONAL] ok
> RFC3490: [PROPOSED STANDARD] obsoleted by RFC5890 RFC5891
> RFC3548: [INFORMATIONAL] obsoleted by RFC4648
> RFC3629: [STANDARD] (-> STD0063) ok
> RFC3864: [BEST CURRENT PRACTICE] (-> BCP0090) ok
> RFC3986: [STANDARD] (-> STD0066) ok
> RFC3987: [PROPOSED STANDARD] ok
> RFC4086: [BEST CURRENT PRACTICE] (-> BCP0106) ok
> RFC4648: [PROPOSED STANDARD] ok
> RFC5226: [BEST CURRENT PRACTICE] (-> BCP0026) ok
> RFC5234: [STANDARD] (-> STD0068) ok
> RFC5246: [PROPOSED STANDARD] ok
> RFC6066: [PROPOSED STANDARD] ok
>
> Informative References:
> draft-ietf-httpstate-cookie-**20: Alternate version available: 23, later
> published as: RFC6265
> draft-ietf-websec-origin-00: [2010-12-30 ID-Exists] ok
> RFC1950: [INFORMATIONAL] ok
> RFC5321: [DRAFT STANDARD] ok
> RFC6202: [INFORMATIONAL] ok
> REC-wsc-ui-20100812: [REC] ok
> WSAPI: not checked
>
> Note:
>
> RFC3490: [PROPOSED STANDARD] obsoleted by RFC5890 RFC5891
> RFC3548: [INFORMATIONAL] obsoleted by RFC4648
> draft-ietf-httpstate-cookie-**20: Alternate version available: 23, later
> published as: RFC6265
> WSAPI: not checked
>
>
> The first three should be updated (with IDNA probably being tricky :-().
>
> The last one is
>
>   [WSAPI]    Hickson, I., "The Web Sockets API", August 2010,
>              <http://dev.w3.org/html5/**websockets/<http://dev.w3.org/html5/websockets/>
> >.
>
> and needs to be updated as well. To enable automated checking with <
> http://greenbytes.de/tech/**webdav/rfc2629xslt/**
> rfc2629xslt.html#checking-**references<http://greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html#checking-references>>,
> I'd make it:
>
> <reference anchor='WD-websockets'
>           target='http://www.w3.org/TR/**2011/WD-websockets-20110419/<http://www.w3.org/TR/2011/WD-websockets-20110419/>
> '>
>  <front>
>    <title>The WebSocket API</title>
>    <author fullname='Ian Hickson' surname='Hickson' initials='I.'/>
>    <date year='2011' month='April' day='19'/>
>  </front>
>  <seriesInfo name='W3C Working Draft' value='WD-websockets-20110419'**/>
>  <annotation>
>    Latest version available at
>    <eref target='http://www.w3.org/TR/**websockets/'/<http://www.w3.org/TR/websockets/'/>
> >.
>  </annotation>
> </reference>
>
> Pimping up the other W3C ref wouldn't hurt either:
>
> <reference anchor='REC-wsc-ui'
>           target='http://www.w3.org/TR/**2010/REC-wsc-ui-20100812/<http://www.w3.org/TR/2010/REC-wsc-ui-20100812/>
> '>
>  <front>
>    <title>Web Security Context: User Interface Guidelines</title>
>    <author fullname='Anil Saldhana' surname='Saldhana' initials='A.'/>
>    <author fullname='Thomas Roessler' surname='Roessler' initials='T.'/>
>    <date year='2010' month='August' day='12'/>
>  </front>
>  <seriesInfo name='W3C Recommendation' value='REC-wsc-ui-20100812'/>
>  <annotation>
>    Latest version available at
>    <eref target='http://www.w3.org/TR/**wsc-ui/'/<http://www.w3.org/TR/wsc-ui/'/>
> >.
>  </annotation>
> </reference>
>
> Best regards, Julian
> ______________________________**_________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/**listinfo/hybi<https://www.ietf.org/mailman/listinfo/hybi>
>