Re: [apps-discuss] WGLC: draft-ietf-appsawg-about-uri-scheme-03.txt
"t.petch" <ietfc@btconnect.com> Tue, 20 March 2012 10:42 UTC
Return-Path: <ietfc@btconnect.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D041A21F8658 for <apps-discuss@ietfa.amsl.com>; Tue, 20 Mar 2012 03:42:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_32=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XZE7GDfSAb5b for <apps-discuss@ietfa.amsl.com>; Tue, 20 Mar 2012 03:42:54 -0700 (PDT)
Received: from mail.btconnect.com (c2bthomr13.btconnect.com [213.123.20.131]) by ietfa.amsl.com (Postfix) with ESMTP id B416A21F8655 for <apps-discuss@ietf.org>; Tue, 20 Mar 2012 03:42:53 -0700 (PDT)
Received: from host86-162-135-195.range86-162.btcentralplus.com (HELO pc6) ([86.162.135.195]) by c2bthomr13.btconnect.com with SMTP id GTK16895; Tue, 20 Mar 2012 10:42:34 +0000 (GMT)
Message-ID: <02f601cd067d$a49ddc20$4001a8c0@gateway.2wire.net>
From: "t.petch" <ietfc@btconnect.com>
To: Jiankang YAO <yaojk@cnnic.cn>, apps-discuss@ietf.org
References: <503575970.11554@cnnic.cn> <4A10020DB6464A0BBA535BF75D21A9D9@LENOVO47E041CF>
Date: Tue, 20 Mar 2012 10:41:27 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0303.4F685F18.00DB, actions=tag
X-Junkmail-Premium-Raw: score=9/50, refid=2.7.2:2012.3.20.101515:17:9.975, ip=86.162.135.195, rules=__HAS_MSGID, __OUTLOOK_MSGID_1, __SANE_MSGID, __TO_MALFORMED_2, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __MIME_VERSION, __CT, CT_TP_8859_1, __CT_TEXT_PLAIN, __CTE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __HAS_X_MAILER, USER_AGENT_OE, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, __ANY_URI, CN_TLD, __URI_NO_PATH, BODY_SIZE_1700_1799, BODYTEXTP_SIZE_3000_LESS, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, HTML_00_01, HTML_00_10, BODY_SIZE_5000_LESS, RDNS_SUSP_GENERIC, __OUTLOOK_MUA, RDNS_SUSP, BODY_SIZE_2000_LESS, BODY_SIZE_7000_LESS
X-Junkmail-Status: score=10/50, host=c2bthomr13.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0209.4F685F21.013C, ss=1, re=0.000, fgs=0, ip=0.0.0.0, so=2011-07-25 19:15:43, dmn=2011-05-27 18:58:46, mode=multiengine
X-Junkmail-IWF: false
Cc: appsawg-chairs@tools.ietf.org
Subject: Re: [apps-discuss] WGLC: draft-ietf-appsawg-about-uri-scheme-03.txt
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 20 Mar 2012 10:42:55 -0000
The I-D points out the impossibility of specifying how to handle the many different tokens that a browser may encounte and then goes on to tell us what Opera does. I am uncomfortable with a Standards Track document telling us about the behaviour of one and only one product, with, the text being in the body of the I-D, an implication that this text has Normative status (earlier versions of this I-D also included Mozilla Firefox). Nothing wrong with the web browser mentioned but I think that having just the one example is inappropriate; other examples should be mentioned (and they all could be in an Informative appendix). I note too that this has been 'quiet long-lasting'; an interesting combination. Tom Petch ----- Original Message ----- From: "Jiankang YAO" <yaojk@cnnic.cn> To: <apps-discuss@ietf.org> Cc: <appsawg-chairs@tools.ietf.org> Sent: Tuesday, March 06, 2012 2:00 AM Subject: [apps-discuss] WGLC: draft-ietf-appsawg-about-uri-scheme-03.txt > Dear colleagues, > > This message starts a two-week WGLC on the draft > draft-ietf-appsawg-about-uri-scheme-03.txt. > > Please help to review this draft. If you support publication, please state as > much on the list. If you are opposed to publication, please state > that on the list as well. It is more/only helpful if you give your reasons for > your position as part of your statement. > > Pls send your comments to apps-discuss@ietf.org or appsawg-chairs@tools.ietf.org or editors. > > The WGLC will end on March 20, 2012 at 1:00 UTC. > > > > Best regards, > Jiankang Yao(as a co-chair of APPSAWG) > > > > _______________________________________________ > apps-discuss mailing list > apps-discuss@ietf.org > https://www.ietf.org/mailman/listinfo/apps-discuss > >
- [apps-discuss] WGLC: draft-ietf-appsawg-about-uri… Jiankang YAO
- Re: [apps-discuss] WGLC: draft-ietf-appsawg-about… t.petch
- Re: [apps-discuss] WGLC: draft-ietf-appsawg-about… Murray S. Kucherawy
- Re: [apps-discuss] WGLC: draft-ietf-appsawg-about… Barry Leiba
- [apps-discuss] Use of RFC 2119, Re: WGLC: draft-i… Julian Reschke
- Re: [apps-discuss] WGLC: draft-ietf-appsawg-about… Murray S. Kucherawy
- Re: [apps-discuss] WGLC: draft-ietf-appsawg-about… Mykyta Yevstifeyev
- Re: [apps-discuss] WGLC: draft-ietf-appsawg-about… Mykyta Yevstifeyev
- Re: [apps-discuss] Use of RFC 2119, Re: WGLC: dra… Barry Leiba
- Re: [apps-discuss] Use of RFC 2119, Re: WGLC: dra… Julian Reschke
- Re: [apps-discuss] Use of RFC 2119, Re: WGLC: dra… Mykyta Yevstifeyev
- Re: [apps-discuss] WGLC: draft-ietf-appsawg-about… Alexey Melnikov
- Re: [apps-discuss] Use of RFC 2119, Re: WGLC: dra… Larry Masinter
- Re: [apps-discuss] Use of RFC 2119, Re: WGLC: dra… Barry Leiba
- Re: [apps-discuss] Use of RFC 2119, Re: WGLC: dra… Alexey Melnikov
- Re: [apps-discuss] Use of RFC 2119, Re: WGLC: dra… Barry Leiba
- Re: [apps-discuss] Use of RFC 2119, Re: WGLC: dra… Ned Freed