From nobody Sat Aug 1 04:37:31 2015 Return-Path: X-Original-To: apps-discuss@ietfa.amsl.com Delivered-To: apps-discuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2735A1A0338; Sat, 1 Aug 2015 04:37:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -7.011 X-Spam-Level: X-Spam-Status: No, score=-7.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uS6G2wGW1nyQ; Sat, 1 Aug 2015 04:37:24 -0700 (PDT) Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A21371A0107; Sat, 1 Aug 2015 04:37:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1438429046; x=1469965046; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=0Sai7NGQDaQULtjT4+sQ88murEXKZSUvaYMavnGoRLw=; b=QHioP9yRBZAiuJzpSj6yzF8SfzJWLQoj60mKo1OV+MeA/a+6/Z6GzQDw INMXx23MBndXPWS0OvAsg74jdgMTSGqLcOHufXFE6lGSwvBPtxI3K6ASF fL/1qa9bVE0rDwBlvgdL2+PhBXwX4VeJ3qlxA3c8JS/lOfgw8xg0O+1VC s=; X-IronPort-AV: E=McAfee;i="5700,7163,7879"; a="223624427" Received: from ironmsg04-r.qualcomm.com ([172.30.46.18]) by wolverine02.qualcomm.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 01 Aug 2015 04:37:25 -0700 X-IronPort-AV: E=Sophos;i="5.15,591,1432623600"; d="scan'208";a="1028460280" Received: from nasanexm01f.na.qualcomm.com ([10.85.0.32]) by Ironmsg04-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 01 Aug 2015 04:37:23 -0700 Received: from [10.64.160.186] (10.80.80.8) by NASANEXM01F.na.qualcomm.com (10.85.0.32) with Microsoft SMTP Server (TLS) id 15.0.1076.9; Sat, 1 Aug 2015 04:37:22 -0700 From: Pete Resnick To: Julian Reschke Date: Sat, 1 Aug 2015 06:37:19 -0500 Message-ID: In-Reply-To: <55BC61D3.4060600@gmx.de> References: <55BB50BF.1010805@gmx.de> <55BB6CB1.6010909@gmx.de> <55BC61D3.4060600@gmx.de> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 8bit X-Mailer: MailMate Trial (1.9.2r5107) X-Originating-IP: [10.80.80.8] X-ClientProxiedBy: NASANEXM01B.na.qualcomm.com (10.85.0.82) To NASANEXM01F.na.qualcomm.com (10.85.0.32) Archived-At: Cc: draft-ietf-httpbis-cice.all@ietf.org, Barry Leiba , IESG , Apps Discuss , HTTP Working Group Subject: Re: [apps-discuss] Appdir Review of draft-ietf-httpbis-cice-01 X-BeenThere: apps-discuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion of application-layer protocols List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Aug 2015 11:37:26 -0000 On 1 Aug 2015, at 1:06, Julian Reschke wrote: > On 2015-08-01 03:59, Barry Leiba wrote: >> ... >> Right. The best way to handle this particular situation isn't to >> make >> this "update" 7231, but to add this to [RFC7231] in the reference >> field for status code 415 in the registry. >> >> On the other hand, let me probe Pete's point a bit: >> Someone reads 7231 and sees the definition for 415. That someone >> doesn't read this, perhaps because she doesn't know about it. She >> also doesn't look at the registry entry, and thus doesn't see the >> reference, because, after all, it's clear that 7231 defines 415, so >> why would one need to look at the registry entry for 415? >> ... > > That is true. But would that person actually *find* the document > updating RFC 7231 in the first place? It's not like we're changing the > RFC 7231, we'd just be changing the RFC database. > > (And yes, if the user would read 7231 through tools.ietf.com or > greenbytes.de, that information would actually appear on the RFC; but > how good does this scale once we have 10 documents "updating" 7231?) And if they read it on datatracker.ietf.org. Or if they use the rfc-editor.org info pages. Eventually, I’d hope that this new RFC format work that’s being done leads to the ability to point to a particular section that has been updated, maybe even highlighting the appropriate section in the file if you view it in HTML format. But leaving a general marker now would be a nice thing. >> In a case such as that, "updates" could be useful. I'm ambivalent >> about whether we should do that, though -- we are trying to avoid >> using "updates" for optional extensions. > > Agreed. In this case, though, it is clear that this document wants to change base behavior. We no longer want it to be purely OPTIONAL to use 415; we want it to be a SHOULD, and used in a particular way. The world doesn’t end either way, but I think “updates” is correct in this case. pr -- Pete Resnick Qualcomm Technologies, Inc. - +1 (858)651-4478 From nobody Mon Aug 3 18:44:07 2015 Return-Path: X-Original-To: apps-discuss@ietfa.amsl.com Delivered-To: apps-discuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 554811A8865 for ; Mon, 3 Aug 2015 18:44:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.312 X-Spam-Level: X-Spam-Status: No, score=-2.312 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1BiC_ay0rUcD for ; Mon, 3 Aug 2015 18:44:05 -0700 (PDT) Received: from cm03fe.IST.Berkeley.EDU (cm03fe.IST.Berkeley.EDU [169.229.218.144]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D52821A8863 for ; Mon, 3 Aug 2015 18:44:05 -0700 (PDT) Received: from 108-67-65-66.lightspeed.sntcca.sbcglobal.net ([108.67.65.66] helo=[192.168.1.76]) by cm03fe.ist.berkeley.edu with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.76) (auth plain:dret@berkeley.edu) (envelope-from ) id 1ZMRGt-00063y-Cj for apps-discuss@ietf.org; Mon, 03 Aug 2015 18:44:05 -0700 Message-ID: <55C018E1.8080405@berkeley.edu> Date: Mon, 03 Aug 2015 18:44:01 -0700 From: Erik Wilde User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: "apps-discuss@ietf.org application-layer protocols" Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Archived-At: Subject: [apps-discuss] Sunset HTTP header field X-BeenThere: apps-discuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion of application-layer protocols List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Aug 2015 01:44:07 -0000 hello. a little while ago there was a brief thread on apps-discuss regarding how to expose information about "URI lifetime" in an HTTP response: https://www.ietf.org/mail-archive/web/apps-discuss/current/msg14343.html it took me a little while to write something up, but i have just published a first draft proposing a "Sunset" HTTP header field, that serves that purpose: https://tools.ietf.org/html/draft-wilde-sunset-header-00 it is as simple as possible right now (a simple timestamp advertising when a resource might become unavailable). i'd be very interested in some feedback about what else might be needed, and of course in people finding this useful and maybe implementing it in their services. thanks a lot and cheers, dret. -- erik wilde | mailto:dret@berkeley.edu - tel:+1-510-2061079 | | UC Berkeley - School of Information (ISchool) | | http://dret.net/netdret http://twitter.com/dret | From nobody Mon Aug 3 18:55:13 2015 Return-Path: X-Original-To: apps-discuss@ietfa.amsl.com Delivered-To: apps-discuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B5F51B3186 for ; Mon, 3 Aug 2015 18:55:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TNdTKjyDTQ4W for ; Mon, 3 Aug 2015 18:55:10 -0700 (PDT) Received: from mail-ob0-x230.google.com (mail-ob0-x230.google.com [IPv6:2607:f8b0:4003:c01::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1910D1B31A3 for ; Mon, 3 Aug 2015 18:55:08 -0700 (PDT) Received: by obbop1 with SMTP id op1so112956405obb.2 for ; Mon, 03 Aug 2015 18:55:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=JACJ/23KHe2HjCSZaRQQ3rezCLHOOjTJf/+apHCdn/8=; b=EyumplJ7IAKyWbCk8SkXd0n3Ufwgg/jO2XspkXeB+CfiouQWCZwY4yy9ce/+H5W1fr gxoT4l8Qyg4R/F6Rg+MEbN0MelqhqER5mYBIRfWuLaNYE2v1H2i0ormFbHlDGjlcNkR6 qtwJOL1nua1dc2+8IsCf+jph1jBOK67y6f1WKGq7mEHxsyC8hGoWB2PfYCXJ3yapyGP1 dseLz+BJFs6KSuJcaB5MBd+itQxRKFYgG1TSthXqLmtKf90QQa8+DemY4w8JcYANy7s0 noynbjjtBhuItFxymVkCQoNXTpv4eAPAJsRmmw+VGXjd6L3uklJVb+x1T7JzjueVHN2t TsnQ== X-Received: by 10.60.92.37 with SMTP id cj5mr922673oeb.30.1438653307474; Mon, 03 Aug 2015 18:55:07 -0700 (PDT) MIME-Version: 1.0 Received: by 10.182.37.65 with HTTP; Mon, 3 Aug 2015 18:54:48 -0700 (PDT) In-Reply-To: <55C018E1.8080405@berkeley.edu> References: <55C018E1.8080405@berkeley.edu> From: James M Snell Date: Mon, 3 Aug 2015 18:54:48 -0700 Message-ID: To: Erik Wilde Content-Type: text/plain; charset=UTF-8 Archived-At: Cc: "apps-discuss@ietf.org application-layer protocols" Subject: Re: [apps-discuss] Sunset HTTP header field X-BeenThere: apps-discuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion of application-layer protocols List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Aug 2015 01:55:11 -0000 This is certainly interesting, but I'm not quite sure it goes far enough. In general, when a particular API is being deprecated, there is generally some form of replacement or alternative that developers are being pushed towards, and potentially some form of notice that should be displayed. Considering that, a Link header might be an interesting possible approach: Link: ; rel="sunset"; title="This API will be sunset on 2015-12-12"; sunset=2015-12-12 - James On Mon, Aug 3, 2015 at 6:44 PM, Erik Wilde wrote: > hello. > > a little while ago there was a brief thread on apps-discuss regarding how to > expose information about "URI lifetime" in an HTTP response: > > https://www.ietf.org/mail-archive/web/apps-discuss/current/msg14343.html > > it took me a little while to write something up, but i have just published a > first draft proposing a "Sunset" HTTP header field, that serves that > purpose: > > https://tools.ietf.org/html/draft-wilde-sunset-header-00 > > it is as simple as possible right now (a simple timestamp advertising when a > resource might become unavailable). i'd be very interested in some feedback > about what else might be needed, and of course in people finding this useful > and maybe implementing it in their services. > > thanks a lot and cheers, > > dret. > > -- > erik wilde | mailto:dret@berkeley.edu - tel:+1-510-2061079 | > | UC Berkeley - School of Information (ISchool) | > | http://dret.net/netdret http://twitter.com/dret | > > _______________________________________________ > apps-discuss mailing list > apps-discuss@ietf.org > https://www.ietf.org/mailman/listinfo/apps-discuss From nobody Mon Aug 3 19:06:16 2015 Return-Path: X-Original-To: apps-discuss@ietfa.amsl.com Delivered-To: apps-discuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0345A1B3324 for ; Mon, 3 Aug 2015 19:06:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.211 X-Spam-Level: X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6_RD6VDOT0K4 for ; Mon, 3 Aug 2015 19:06:13 -0700 (PDT) Received: from cm03fe.IST.Berkeley.EDU (cm03fe.IST.Berkeley.EDU [169.229.218.144]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7CA151B3327 for ; Mon, 3 Aug 2015 19:06:11 -0700 (PDT) Received: from 108-67-65-66.lightspeed.sntcca.sbcglobal.net ([108.67.65.66] helo=[192.168.1.76]) by cm03fe.ist.berkeley.edu with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.76) (auth plain:dret@berkeley.edu) (envelope-from ) id 1ZMRcI-0004qZ-Be; Mon, 03 Aug 2015 19:06:11 -0700 Message-ID: <55C01E0F.8080806@berkeley.edu> Date: Mon, 03 Aug 2015 19:06:07 -0700 From: Erik Wilde User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: "apps-discuss@ietf.org application-layer protocols" References: <55C018E1.8080405@berkeley.edu> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Archived-At: Subject: Re: [apps-discuss] Sunset HTTP header field X-BeenThere: apps-discuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion of application-layer protocols List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Aug 2015 02:06:15 -0000 hello james. thanks a lot for your feedback! On 2015-08-03 18:54 , James M Snell wrote: > This is certainly interesting, but I'm not quite sure it goes far > enough. In general, when a particular API is being deprecated, there > is generally some form of replacement or alternative that developers > are being pushed towards, and potentially some form of notice that > should be displayed. yes, those may be things that people want to advertise in well-known ways. i had listed both aspects as open issues: https://tools.ietf.org/html/draft-wilde-sunset-header-00#section-8 my idea was to add optional qualifiers to the timestamp if people seem to want these features, but that's of course just one way of doing it. > Considering that, a Link header might be an interesting possible approach: > Link: ; rel="sunset"; title="This API will > be sunset on 2015-12-12"; sunset=2015-12-12 i was considering the link relation type design option, but then concluded that at its core, the sunset timestamp is mostly a "unary link" and thus does not fit the link model very well. but i agree that pretty much anything can be modeled as links, and then it would fit into the link header as shown in your example. thanks again and cheers, dret. -- erik wilde | mailto:dret@berkeley.edu - tel:+1-510-2061079 | | UC Berkeley - School of Information (ISchool) | | http://dret.net/netdret http://twitter.com/dret | From nobody Wed Aug 5 00:56:11 2015 Return-Path: X-Original-To: apps-discuss@ietfa.amsl.com Delivered-To: apps-discuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 91CF81B2D4C for ; Wed, 5 Aug 2015 00:56:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.61 X-Spam-Level: X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sP4iduTlpWKu for ; Wed, 5 Aug 2015 00:56:06 -0700 (PDT) Received: from cnnic.cn (smtp13.cnnic.cn [218.241.118.13]) by ietfa.amsl.com (Postfix) with ESMTP id 8B89B1B2D45 for ; Wed, 5 Aug 2015 00:56:05 -0700 (PDT) Received: from CNNIC-PC (unknown [218.241.103.180]) by ocmail02.zx.nicx.cn (Coremail) with SMTP id AQAAf0ApMZWQwcFVBXixBw--.7461S2; Wed, 05 Aug 2015 15:56:00 +0800 (CST) Date: Wed, 5 Aug 2015 15:55:49 +0800 From: "qinxiaowei@cnnic.cn" To: apps-discuss X-Priority: 3 X-Has-Attach: no X-Mailer: Foxmail 7, 2, 5, 136[cn] Mime-Version: 1.0 Message-ID: <201508051555488864783@cnnic.cn> Content-Type: multipart/alternative; boundary="----=_001_NextPart003865136435_=----" X-CM-TRANSID: AQAAf0ApMZWQwcFVBXixBw--.7461S2 X-Coremail-Antispam: 1UD129KBjvJXoW7Cr43CFy5JFW8WFW5ArW3Awb_yoW5JrWfpa y8XrZ5Jas7Aw4Ikrs2qwnYqFy5u3WrW3yIgF9rtr1Yy3s8tF1Ygw1xKw4fWrW7urWUWFWq qr40va1avw15trJanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUUQFb7Iv0xC_Zr1lb4IE77IF4wAFF20E14v26r1j6r4UM7CY07I2 0VC2zVCF04k26cxKx2IYs7xG6rWj6s0DM7CIcVAFz4kK6r1j6r18M28lY4IEw2IIxxk0rw A2F7IY1VAKz4vEj48ve4kI8wA2z4x0Y4vE2Ix0cI8IcVAFwI0_Xr0_Ar1l84ACjcxK6xII jxv20xvEc7CjxVAFwI0_Cr0_Gr1UM28EF7xvwVC2z280aVAFwI0_GcCE3s1l84ACjcxK6I 8E87Iv6xkF7I0E14v26rxl6s0DM2AIxVAIcxkEcVAq07x20xvEncxIr21l5I8CrVCF0I0E 4I0vr24l5I8CrVC2j2CEjI02ccxYII8I67AEr4CY67k08wAqx4xG6I8I3I0E8cIF7480aV AKz4kxMcIj6xIIjxv20xvE14v26r1j6r18McIj6I8E87Iv67AKxVWUJVW8JwAm72CE4IkC 6x0Yz7v_Jr0_Gr1lF7xvr2IYc2Ij64vIr41lFcxC0VAYjxAxZF0Ew4CEw7xC0wACY4xI67 k04243AVC20s07MxkIecxEwVAFwVW8CwCF04k20xvY0x0EwIxGrwCFx2IqxVCFs4IE7xkE bVWUJVW8JwC20s026c02F40E14v26r106r1rMI8I3I0E7480Y4vE14v26r106r1rMI8E67 AF67kF1VAFwI0_Jr0_JrylIxkGc2Ij64vIr41lIxAIcVC0I7IYx2IY67AKxVWUJVWUCwCI 42IY6xIIjxv20xvEc7CjxVAFwI0_Jr0_Gr1lIxAIcVCF04k26cxKx2IYs7xG6rW3Jr0E3s 1lIxAIcVC2z280aVAFwI0_Jr0_Gr1lIxAIcVC2z280aVCY1x0267AKxVWUJVW8JwCE64xv F2IEb7IF0Fy7YxBIdaVFxhVjvjDU0xZFpf9x07jwwIDUUUUU= X-CM-SenderInfo: xtlq5x5drzvxw6fq0xffof0/ Archived-At: Subject: [apps-discuss] New Version Notification for draft-qin-appsawg-uatn-ut-00.txt X-BeenThere: apps-discuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion of application-layer protocols List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Aug 2015 07:56:08 -0000 This is a multi-part message in MIME format. ------=_001_NextPart003865136435_=---- Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: base64 RGVhciBhbGwsDQogICBJIHByb3Bvc2VkIGFuIGFwcHJvYWNoIHRvIHVwbG9hZCBhY2NlbGVyYXRp b24gdHJhbnNwb3J0IG5ldHdvcmsgZm9yIHVwc3RyZWFtIHRyYWZmaWNzLCBhbmQgdGhlIGRyYWZ0 IHdhcyBzdWJtaXR0ZWQuIA0KQW55IGNvbW1lbnRzIGFyZSB3ZWxjb21lLg0KDQpSZWdhcmRzLA0K DQpYaWFvd2VpIFFpbg0KDQoNCg0KIA0KRnJvbTogaW50ZXJuZXQtZHJhZnRzDQpEYXRlOiAyMDE1 LTA4LTA1IDE1OjUwDQpUbzogWGlhb0RvbmcgTGVlOyBYaWFvd2VpIFFpbjsgWGlhb2RvbmcgTGVl OyBYaWFvd2VpIFFpbjsgTmluZyBLb25nOyBOaW5nIEtvbmcNClN1YmplY3Q6IE5ldyBWZXJzaW9u IE5vdGlmaWNhdGlvbiBmb3IgZHJhZnQtcWluLWFwcHNhd2ctdWF0bi11dC0wMC50eHQNCiANCkEg bmV3IHZlcnNpb24gb2YgSS1ELCBkcmFmdC1xaW4tYXBwc2F3Zy11YXRuLXV0LTAwLnR4dA0KaGFz IGJlZW4gc3VjY2Vzc2Z1bGx5IHN1Ym1pdHRlZCBieSBYaWFvd2VpIFFpbiBhbmQgcG9zdGVkIHRv IHRoZQ0KSUVURiByZXBvc2l0b3J5Lg0KIA0KTmFtZTogZHJhZnQtcWluLWFwcHNhd2ctdWF0bi11 dA0KUmV2aXNpb246IDAwDQpUaXRsZTogVXBsb2FkIEFjY2VsZXJhdGlvbiBUcmFuc3BvcnQgTmV0 d29yayBmb3IgVXBzdHJlYW0gVHJhZmZpY3MgDQpEb2N1bWVudCBkYXRlOiAyMDE1LTA4LTA1DQpH cm91cDogSW5kaXZpZHVhbCBTdWJtaXNzaW9uDQpQYWdlczogMTUNClVSTDogICAgICAgICAgICBo dHRwczovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQtcWluLWFwcHNhd2ctdWF0 bi11dC0wMC50eHQNClN0YXR1czogICAgICAgICBodHRwczovL2RhdGF0cmFja2VyLmlldGYub3Jn L2RvYy9kcmFmdC1xaW4tYXBwc2F3Zy11YXRuLXV0Lw0KSHRtbGl6ZWQ6ICAgICAgIGh0dHBzOi8v dG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1xaW4tYXBwc2F3Zy11YXRuLXV0LTAwDQogDQogDQpB YnN0cmFjdDoNCiAgIE1vdmluZyBkYXRhIGNlbnRlciBjbG9zZXIgdG8gZW5kIHVzZXJzIGNhbiBw cm92aWRlIG51bWVyb3VzIGJlbmVmaXRzDQogICBmb3IgcHJlLXVwbG9hZGVkIGNvbnRlbnQ6IGxv d2VyIGxhdGVuY3ksIGluY3JlYXNlZCByb2J1c3RuZXNzIG9mDQogICBkZWxpdmVyeSwgYW5kIGlt cHJvdmVkIHF1YWxpdHkgb2YgdXNlciBleHBlcmllbmNlLiAgRm9yIHRoZXNlDQogICByZWFzb25z LCBtYW55IE9ubGluZSBTdG9yYWdlIFNlcnZpY2UgUHJvdmlkZXJzKE9TU1BzKSxQaG90b3MgU2hh cmluZw0KICAgU2VydmljZSBQcm92aWRlcnMgKFBTU1BzKSwgYW5kIFZpZGVvcyBTaGFyaW5nIFNl cnZpY2UNCiAgIFByb3ZpZGVycyhWU1NQcyksIGV0Yy4sIGFyZSBzY2FsaW5nIHVwIHRoZWlyIGlu ZnJhc3RydWN0dXJlLCBhbmQgbWFueQ0KICAgYWJvdmUgVXBsb2FkIFNlcnZpY2UgUHJvdmlkZXJz KFVTUHMpYXJlIGFsc28gZGVwbG95aW5nIHRoZWlyIG93bg0KICAgY2xvdWQgcGxhdGZvcm1zIHRv IGltcHJvdmUgZGF0YSB1cGxvYWQgcmF0ZS4gIEl0IGlzIGdlbmVyYWxseQ0KICAgZGVzaXJhYmxl IHRoYXQgYSBnaXZlbiBjb250ZW50IGl0ZW0gZ2VuZXJhdGVkIGJ5IGVuZCB1c2VycyBjYW4gYmUN CiAgIHF1aWNrbHkgYW5kIHJvYnVzdGx5IGRlbGl2ZXJlZCB0byB0aGUgZGVzdGluYXRpb24gcmVn YXJkbGVzcyBvZiB0aGF0DQogICBlbmQgdXNlcidzIGxvY2F0aW9uIG9yIGF0dGFjaG1lbnQgbmV0 d29yay4gIFRoaXMgaXMgdGhlIG1vdGl2YXRpb24NCiAgIGZvciBkZXBsb3lpbmcgVXBsb2FkIEFj Y2VsZXJhdGlvbiBUcmFuc3BvcnQgTmV0d29yayhVQVROKSBzbyBpdCBjYW4NCiAgIHByb3Bvc2Ug YW4gb3BlbiBjb250ZW50IGRlbGl2ZXJ5IGluZnJhc3RydWN0dXJlIGZvciB0aGUgZW5kLXRvLWVu ZA0KICAgZGVsaXZlcnkgb2YgY29udGVudCBmcm9tIGVuZCB1c2VycyB0byB0aGUgZGVzdGluYXRp b24oZGF0YSBjZW50ZXIgb3INCiAgIGFub3RoZXIgZW5kIHVzZXIsIGV0Yy4pLiAgSG93ZXZlciwg bm8gc3RhbmRhcmRzIG9yIG9wZW4NCiAgIHNwZWNpZmljYXRpb25zIGN1cnJlbnRseSBleGlzdCB0 byBmYWNpbGl0YXRlIHN1Y2ggYW4gdXBsb2FkDQogICBhY2NlbGVyYXRpb24gbWVjaGFuaXNtLg0K IA0KICAgVGhlIGdvYWwgb2YgdGhpcyBkb2N1bWVudCBpcyB0byBleHBsYWluIHRoZSBwcm9wb3Nl ZCBVQVROIGluIGRldGFpbA0KICAgZm9yIHByb3ZpZGluZyBwdWJsaWMgdXBsb2FkIGFjY2VsZXJh dGlvbiBzZXJ2aWNlIGFuZCBpbnRlcmNvbm5lY3QNCiAgIGV4aXN0aW5nIHVwbG9hZCBhY2NlbGVy YXRpb24gc3lzdGVtcyBhcyBhbiBvcGVuIGNvbnRlbnQgZGVsaXZlcnkNCiAgIGluZnJhc3RydWN0 dXIuDQogDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgDQogDQogDQpQbGVhc2Ugbm90ZSB0aGF0 IGl0IG1heSB0YWtlIGEgY291cGxlIG9mIG1pbnV0ZXMgZnJvbSB0aGUgdGltZSBvZiBzdWJtaXNz aW9uDQp1bnRpbCB0aGUgaHRtbGl6ZWQgdmVyc2lvbiBhbmQgZGlmZiBhcmUgYXZhaWxhYmxlIGF0 IHRvb2xzLmlldGYub3JnLg0KIA0KVGhlIElFVEYgU2VjcmV0YXJpYXQNCiANCg== ------=_001_NextPart003865136435_=---- Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable =0A
Dear al= l,
   I proposed an approach to upload accel= eration transport network for upstream traffics, and the = draft was submitted. 
Any comments are welcome.

Regards,

Xiaowei= Qin
=0A

=0A
=
=0A
 
Subject: New Version Notification fo= r draft-qin-appsawg-uatn-ut-00.txt
 
= =0A
A new version of I-D, draft-qin-appsawg-uatn-ut-00.txt
=0Ahas been successfully submitted by Xiaowei Qin and posted to the
= =0A
IETF repository.
=0A
 
=0A
Name: draft-qin= -appsawg-uatn-ut
=0A
Revision: 00
=0A
Title: Upload Acc= eleration Transport Network for Upstream Traffics
=0A
Document d= ate: 2015-08-05
=0A
Group: Individual Submission
=0A
Pa= ges: 15
=0A
URL:        =     https://www.ietf.org/internet-drafts/draft-qin-appsawg-= uatn-ut-00.txt
=0A
Status:      &nb= sp;  https://datatracker.ietf.org/doc/draft-qin-appsawg-uatn-ut/=0A
Htmlized:       https://tools.ietf.= org/html/draft-qin-appsawg-uatn-ut-00
=0A
 
=0A
&nb= sp;
=0A
Abstract:
=0A
   Moving data center cl= oser to end users can provide numerous benefits
=0A
   = for pre-uploaded content: lower latency, increased robustness of
=0A<= div>   delivery, and improved quality of user experience.  = For these
=0A
   reasons, many Online Storage Service P= roviders(OSSPs),Photos Sharing
=0A
   Service Providers= (PSSPs), and Videos Sharing Service
=0A
   Providers(V= SSPs), etc., are scaling up their infrastructure, and many
=0A
&n= bsp;  above Upload Service Providers(USPs)are also deploying their ow= n
=0A
   cloud platforms to improve data upload rate.&n= bsp; It is generally
=0A
   desirable that a given cont= ent item generated by end users can be
=0A
   quickly a= nd robustly delivered to the destination regardless of that
=0A
&= nbsp;  end user's location or attachment network.  This is the m= otivation
=0A
   for deploying Upload Acceleration Tran= sport Network(UATN) so it can
=0A
   propose an open co= ntent delivery infrastructure for the end-to-end
=0A
  = delivery of content from end users to the destination(data center or=0A
   another end user, etc.).  However, no standards= or open
=0A
   specifications currently exist to facil= itate such an upload
=0A
   acceleration mechanism.=0A
 
=0A
   The goal of this document is to= explain the proposed UATN in detail
=0A
   for providi= ng public upload acceleration service and interconnect
=0A
 =   existing upload acceleration systems as an open content delivery=0A
   infrastructur.
=0A
 
=0A
&n= bsp;           &nbs= p;            =             &n= bsp;           &nbs= p;            =             &n= bsp;      
=0A
 
=0A 
=0A
Please note that it may take a couple of minutes from= the time of submission
=0A
until the htmlized version and diff a= re available at tools.ietf.org.
=0A
 
=0A
The IETF = Secretariat
=0A
 
=0A
=0A ------=_001_NextPart003865136435_=------ From nobody Wed Aug 5 15:14:31 2015 Return-Path: X-Original-To: apps-discuss@ietfa.amsl.com Delivered-To: apps-discuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C1CF1ACD96 for ; Wed, 5 Aug 2015 15:14:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.611 X-Spam-Level: X-Spam-Status: No, score=-5.611 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4wnCLdCxoWeQ for ; Wed, 5 Aug 2015 15:14:28 -0700 (PDT) Received: from ausc60pc101.us.dell.com (ausc60pc101.us.dell.com [143.166.85.206]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 50AFD1ACD65 for ; Wed, 5 Aug 2015 15:14:28 -0700 (PDT) DomainKey-Signature: s=smtpout; d=dell.com; c=nofws; q=dns; h=X-LoopCount0:X-IronPort-AV:From:To:Date:Subject: Thread-Topic:Thread-Index:Message-ID:Accept-Language: Content-Language:X-MS-Has-Attach:X-MS-TNEF-Correlator: acceptlanguage:Content-Type:Content-Transfer-Encoding: MIME-Version; b=OmvnjquTcbmdRvlojTgYAh3aZFem+iXyHPlKoGV95a2OyL81etnsUysO uVVIix5uQNEblhOeNGNKa/0gmAnfozGZQyomP8tflPpmimVN6N1OuKB4r fmFakiyYAa1n2JILlXQwqLkkRhmb2hUtpLM75xUNg/Lv4+eVp78p6+bpB Q=; DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dell.com; i=@dell.com; q=dns/txt; s=smtpout; t=1438812868; x=1470348868; h=from:to:date:subject:message-id: content-transfer-encoding:mime-version; bh=R0bt83YWo9nVuM3P6gteuQ0F3V6n7QL2NB1+/J5WItQ=; b=KszyiXf7djN6GxHE3+iRw92Hun4GPLLJC+i/Uf47lbnf4Z/rXHEnLTMp VyWU7hlFwDAN5nGTBLG49u5D0GsdcSyV4LSDWUWxerA2n+wywmq3TUJpM lvhz8ELLCa+A5a+uiaBqasNrbBD01LpoTR/7mSsQuWxHwo4Ht8Gu65axX Q=; X-LoopCount0: from 10.175.216.249 X-IronPort-AV: E=Sophos;i="5.15,620,1432616400"; d="scan'208";a="822399002" From: To: Date: Wed, 5 Aug 2015 17:12:10 -0500 Thread-Topic: VNC URI Scheme update and next steps? Thread-Index: AdDPy17/0OlVHCkvS3yF4DzAd+UEog== Message-ID: <2D58682309E75147BB3B286C815CAC7E2AC7011556@AUSX7MCPS308.AMER.DELL.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 Archived-At: Subject: [apps-discuss] VNC URI Scheme update and next steps? X-BeenThere: apps-discuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion of application-layer protocols List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Aug 2015 22:14:30 -0000 Hi all, I've submitted an updated VNC scheme document: http://www.ietf.org/id/draft-warden-appsawg-vnc-scheme-04.txt=20 This submission separates the traditional VNC security types from connectio= n channel types (like SSH). I have done my best to address all comments rec= eived to date. I believe it has the working code and rough consensus needed= to proceed through the RFC process.=20 Are any of the IETF personnel on this list willing to serve as a document s= hepherd or help in issuing a call for adoption? Regards, David Warden Dell Enterprise Solutions Group From nobody Thu Aug 13 04:58:28 2015 Return-Path: X-Original-To: apps-discuss@ietfa.amsl.com Delivered-To: apps-discuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 264FF1A1A27; Thu, 13 Aug 2015 04:58:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.6 X-Spam-Level: X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rcRo-dnKN8eG; Thu, 13 Aug 2015 04:58:22 -0700 (PDT) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4A3841A1A06; Thu, 13 Aug 2015 04:58:22 -0700 (PDT) Received: from [192.168.2.177] ([84.187.47.186]) by mail.gmx.com (mrgmx003) with ESMTPSA (Nemesis) id 0MRoRF-1ZFFEP43EP-00SzgB; Thu, 13 Aug 2015 13:57:45 +0200 To: Barry Leiba References: <55BB50BF.1010805@gmx.de> <55BB6CB1.6010909@gmx.de> From: Julian Reschke Message-ID: <55CC8637.2040306@gmx.de> Date: Thu, 13 Aug 2015 13:57:43 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:I4CFVXpVnqsM/hax+2fA455EPRbF7LdgvIW5SiUbaKw87lB5+KQ vr/psLJEAnAZqkU3c2Ob2v9eo9BNAIGPLh4Vi96MpeWJg5WqjQK+O2VYw2U3zGIQmK0v3JY AmR8TmZhwAWxck0liI8NE9yBEGGXN85RLG8dy/gfd647bRpGxwAFtswdN1WOYX6wKBO55se fVxNS8XbairC2j+zdXYVg== X-UI-Out-Filterresults: notjunk:1;V01:K0:Yu4Q4SVuP2U=:EH8Ga0YdotB+d+fh8E4YcJ oyCbC65jy5B+IdCNLcAdTNYZNE6u+oDtJjquigxFhldbF9g2+iVa+eJ+7kJZo2h9COLNCt/Ac ZJodwChMVzrS8DzOA6JVu7H6eLNISUNeYs0TVzznGylUEqCrBZ0xDtHE7OfHDVjm+0QLs1goj 0D5zu1xQN2To08tpPDrPZ9X/lUcmPrvE7HGoWxLyhKBS9dGG67vZw7sslk6X/M4u5bS9RRDvf v1pr73CCAgkF5IQgzIM8CW/0hNPYsNDm70Ll4yrCz+vVa9mKR/GmcdSO9kqY3101uHpsc0rfa X2tIsOyMYcDYPbBaOFiVJWtYFkXZ8F7MfnxT1RFVPsNtGv/fGjWH9L0KsuZLygygU9luN3mCF wNNVjwRvbtKAW8/AgdCfl7VUGbHxlLaKuM/xQV0vsEK/nH2+nOzfc5Ye/EXRTYSFL6ZB++7LT qlXfD1BPm0nqFl4fwGZuGstq1KWPvNpaVoAUi8RyQIMcXSIlxm0wQp8TB2BQdRFYC+4+lvKs7 5uDslI48ghxVfBqP11bmkrAViID+ynLnE2EMNcredkdAfO3X6s6ojxzvt+idsDkr/C/4wV4SK jlsJWMq/h008fFIe3FzVHo+KunjcQ128hWvD6msdhdQ6Ou/4o7uJAUw/3wddJ7PXhmsdgrfQY hV+TPAJ3iWYcx5TunVS/+XMpIF05L1MeTOJoFb3d+BGTAnv1gUeN7QCGFu9bik9Oyw9oU6wvq ulyb2d4wllNtEiFfPhSsLmgU80NBQY5NBBS1ZA== Archived-At: Cc: draft-ietf-httpbis-cice.all@ietf.org, Pete Resnick , IESG , Apps Discuss , HTTP Working Group Subject: Re: [apps-discuss] Appdir Review of draft-ietf-httpbis-cice-01 X-BeenThere: apps-discuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion of application-layer protocols List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Aug 2015 11:58:24 -0000 On 2015-08-01 03:59, Barry Leiba wrote: > ... > Right. The best way to handle this particular situation isn't to make > this "update" 7231, but to add this to [RFC7231] in the reference > field for status code 415 in the registry. > ... That's what I'm going to do; it best matches the intent of the document the WG agreed to > On the other hand, let me probe Pete's point a bit: > Someone reads 7231 and sees the definition for 415. That someone > doesn't read this, perhaps because she doesn't know about it. She > also doesn't look at the registry entry, and thus doesn't see the > reference, because, after all, it's clear that 7231 defines 415, so > why would one need to look at the registry entry for 415? > > In a case such as that, "updates" could be useful. I'm ambivalent > about whether we should do that, though -- we are trying to avoid > using "updates" for optional extensions. Right. We would just end up with a huge collection of "updates". Best regards, Julian From nobody Fri Aug 14 03:40:09 2015 Return-Path: X-Original-To: apps-discuss@ietfa.amsl.com Delivered-To: apps-discuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CBD31A0032 for ; Fri, 14 Aug 2015 03:40:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.011 X-Spam-Level: X-Spam-Status: No, score=-2.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7FG-teSDxDov for ; Fri, 14 Aug 2015 03:40:07 -0700 (PDT) Received: from statler.isode.com (statler.isode.com [217.34.220.151]) by ietfa.amsl.com (Postfix) with ESMTP id 085F31A0030 for ; Fri, 14 Aug 2015 03:40:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1439548805; d=isode.com; s=selector; i=@isode.com; bh=DMG9IIwrTD8oBzrePvU0As9OXETWLzT2q1VX177wuBo=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=ne8ZZlDAi7cwIJos01Pg4G/0H5AUlDMXa4zJHBHElDPBf0xSZg66zRAgsp1thR0Get1zQn GaqynjoMU8vSujh6PCWImJqOBVmAEWXj5B29Uq2YKqqYSMsaPeJrnSZOE7g8CrVMeZwEPc QMh6LtnAbYs3xhaGEfQEpo6ZOHuyOUY=; Received: from [172.20.1.215] (dhcp-215.isode.net [172.20.1.215]) by statler.isode.com (submission channel) via TCP with ESMTPSA id ; Fri, 14 Aug 2015 11:40:05 +0100 Message-ID: <55CDC569.7060100@isode.com> Date: Fri, 14 Aug 2015 11:39:37 +0100 From: Alexey Melnikov User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 To: IETF Apps Discuss MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Archived-At: Subject: [apps-discuss] Prague APPSAWG/ART area meeting minutes X-BeenThere: apps-discuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion of application-layer protocols List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Aug 2015 10:40:08 -0000 I've lightly edited Pete Resnick's great jabber minutes: https://www.ietf.org/proceedings/93/minutes/minutes-93-appsawg Let me know if there are any corrections/clarifications. From nobody Thu Aug 20 15:34:34 2015 Return-Path: X-Original-To: apps-discuss@ietfa.amsl.com Delivered-To: apps-discuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54EC01B2C4B; Thu, 20 Aug 2015 15:34:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -99.612 X-Spam-Level: X-Spam-Status: No, score=-99.612 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MANGLED_TOOL=2.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qI_4q5tCcAhw; Thu, 20 Aug 2015 15:34:31 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 50DE21B2C8B; Thu, 20 Aug 2015 15:34:28 -0700 (PDT) Received: by rfc-editor.org (Postfix, from userid 30) id 30DE4180207; Thu, 20 Aug 2015 15:34:00 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20150820223400.30DE4180207@rfc-editor.org> Date: Thu, 20 Aug 2015 15:34:00 -0700 (PDT) Archived-At: Cc: drafts-update-ref@iana.org, apps-discuss@ietf.org, rfc-editor@rfc-editor.org Subject: [apps-discuss] RFC 7601 on Message Header Field for Indicating Message Authentication Status X-BeenThere: apps-discuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion of application-layer protocols List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Aug 2015 22:34:32 -0000 A new Request for Comments is now available in online RFC libraries. RFC 7601 Title: Message Header Field for Indicating Message Authentication Status Author: M. Kucherawy Status: Standards Track Stream: IETF Date: August 2015 Mailbox: superuser@gmail.com Pages: 53 Characters: 120736 Obsoletes: RFC 7001, RFC 7410 I-D Tag: draft-ietf-appsawg-rfc7001bis-11.txt URL: https://www.rfc-editor.org/info/rfc7601 DOI: http://dx.doi.org/10.17487/RFC7601 This document specifies a message header field called Authentication- Results for use with electronic mail messages to indicate the results of message authentication efforts. Any receiver-side software, such as mail filters or Mail User Agents (MUAs), can use this header field to relay that information in a convenient and meaningful way to users or to make sorting and filtering decisions. This document is a product of the Applications Area Working Group Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: 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 Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/rfc.html Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC From nobody Tue Aug 25 17:45:58 2015 Return-Path: X-Original-To: apps-discuss@ietfa.amsl.com Delivered-To: apps-discuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7A781ACD97 for ; Tue, 25 Aug 2015 17:45:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 4.933 X-Spam-Level: **** X-Spam-Status: No, score=4.933 tagged_above=-999 required=5 tests=[BAYES_50=0.8, FH_RELAY_NODNS=1.451, FR_IMPORT_CSS=1.889, HTML_MESSAGE=0.001, RDNS_NONE=0.793, SPF_PASS=-0.001] autolearn=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 55ph5GBZsGJi for ; Tue, 25 Aug 2015 17:45:52 -0700 (PDT) Received: from mail.csnet1.cs.tsinghua.edu.cn (unknown [211.151.89.50]) by ietfa.amsl.com (Postfix) with ESMTP id 93F161ACD95 for ; Tue, 25 Aug 2015 17:45:50 -0700 (PDT) Received: from sunlh-pc (unknown [58.205.200.231]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.csnet1.cs.tsinghua.edu.cn (Tsinghua University (Postfix)) with ESMTPSA id 9BCC07108CF5; Wed, 26 Aug 2015 08:03:15 +0800 (CST) Date: Wed, 26 Aug 2015 08:45:49 +0800 From: "yong" To: "apps-discuss" X-Mailer: NetEase Flash Mail 2.3.1.12 X-Priority: 3 (Normal) MIME-Version: 1.0 Message-ID: <55DD0C3B.7040900@csnet1.cs.tsinghua.edu.cn> Content-Type: multipart/alternative; boundary="====003__MESSAGE__ID__54yg6f6h6y456345====" Archived-At: Cc: cuiyong Subject: [apps-discuss] Fwd: New Non-WG Mailing List: Storagesync -- Mechanisms to synchronize client file systems with Internet-based data storage services X-BeenThere: apps-discuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion of application-layer protocols List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Aug 2015 00:45:57 -0000 --====003__MESSAGE__ID__54yg6f6h6y456345==== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 SGkgYWxsLA0KDQpBIG5ldyBtYWlsaW5nIGxpc3QgaGFzIGJlZW4gZXN0YWJsaXNoZWQgZm9yIElu dGVybmV0IFN0b3JhZ2UgU3luYyAoSVNTKSB3b3JrLiBXZSd2ZSBtYWRlIGEgcmVsZXZhbnQgcHJl c2VudGF0aW9uIGFib3V0IHRoaXMgd29yayBpbiBQcmFndWUuIFdlIHN0aWxsIHN0YXJ0IHJlbGF0 ZWQgZGlzY3Vzc2lvbnMgKGUuZy4gcHJvYmxlbXMsIHNjb3BlIG9mIHdvcmsgYW5kIGV0Yy4pIG9u IGl0IHNvb24gYW5kIGFueSBpbnRlcmVzdGVkIHBlb3BsZSBhcmUgbW9yZSB0aGFuIHdlbGNvbWUg dG8gc3Vic2NyaWJlIGl0LiBGb2xsb3dpbmcgcGxlYXNlIGZpbmQgdGhlIGxpc3QgYWRkcmVzcyBh bmQgZGV0YWlsZWQgcHVycG9zZSBvZiB0aGUgbWFpbGluZyBsaXN0Lg0KDQpSZWdhcmRzLA0KWW9u ZyBDdWksDQoNClByb2Zlc3NvciwgVHNpbmdodWEgVW5pdmVyc2l0eSwgQmVpamluZywgQ2hpbmEN CkFzc29jaWF0ZSBFZGl0b3Igb24gSUVFRSBUUERTLCBJRUVFIFRDQw0KVVJMOiBodHRwOi8vd3d3 LjRvdmVyNi5lZHUuY24vY3VpeW9uZy9pbmRleC5odG1sDQoNCi0tLS0tLS0tLS0gRm9yd2FyZGVk IG1lc3NhZ2UgLS0tLS0tLS0tLQ0KRnJvbTogSUVURiBTZWNyZXRhcmlhdCA8aWV0Zi1zZWNyZXRh cmlhdEBpZXRmLm9yZz4NCkRhdGU6IDIwMTUtMDgtMjEgMDo1MSBHTVQrMDg6MDANClN1YmplY3Q6 IE5ldyBOb24tV0cgTWFpbGluZyBMaXN0OiBTdG9yYWdlc3luYyAtLSBNZWNoYW5pc21zIHRvIHN5 bmNocm9uaXplIGNsaWVudCBmaWxlIHN5c3RlbXMgd2l0aCBJbnRlcm5ldC1iYXNlZCBkYXRhIHN0 b3JhZ2Ugc2VydmljZXMNClRvOiBJRVRGIEFubm91bmNlbWVudCBMaXN0IDxpZXRmLWFubm91bmNl QGlldGYub3JnPg0KQ2M6IGN1aXlvbmdAdHNpbmdodWEuZWR1LmNuLCBTdG9yYWdlc3luY0BpZXRm Lm9yZw0KDQoNCkEgbmV3IElFVEYgbm9uLXdvcmtpbmcgZ3JvdXAgZW1haWwgbGlzdCBoYXMgYmVl biBjcmVhdGVkLg0KDQpMaXN0IGFkZHJlc3M6IHN0b3JhZ2VzeW5jQGlldGYub3JnDQpBcmNoaXZl OiBodHRwczovL21haWxhcmNoaXZlLmlldGYub3JnL2FyY2gvc2VhcmNoLz9lbWFpbF9saXN0PXN0 b3JhZ2VzeW5jDQpUbyBzdWJzY3JpYmU6IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlz dGluZm8vc3RvcmFnZXN5bmMNCg0KUHVycG9zZToNCg0KTmV0d29yay1iYXNlZCBzdG9yYWdlIHNl cnZpY2VzLCBzdWNoIGFzIGNsb3VkIHN0b3JhZ2UsIGF0dHJhY3QgaHVnZSBudW1iZXJzIG9mIHVz ZXJzIGFuZCBwcm9kdWNlIGEgc2lnbmlmaWNhbnQgc2hhcmUgb2YgSW50ZXJuZXQgdHJhZmZpYy4g QnV0IG1vc3QgZXhpc3RpbmcgbmV0d29yayBzdG9yYWdlIHNlcnZpY2VzIG1ha2UgdXNlIG9mIHBy b3ByaWV0YXJ5IHN5bmMgcHJvdG9jb2xzIHRvIGFjaGlldmUgZGF0YSBzeW5jaHJvbml6YXRpb24u IEFsbW9zdCBhbGwgb2YgdGhlbSBoYXZlIHByb3ZlZCBub3QgdG8gYmUgZWZmaWNpZW50IGVub3Vn aCBhbmQgc2hvdWxkIGJlIGltcHJvdmVkLiBUaGlzIG1haWxpbmcgbGlzdCBpcyBmb3IgZGlzY3Vz c2lvbiBvZiBwcm9ibGVtcyBjYXVzZWQgYnkgaW5lZmZpY2llbnQgcHJvcHJpZXRhcnkgc3luYyBw cm90b2NvbHMgYW5kIG9mIGFsdGVybmF0aXZlcyB0aGF0IGNhbiBiZSBtb3JlIGVmZmljaWVudCBh bmQgc3RhbmRhcmRpemVkLg0KDQpGb3IgYWRkaXRpb25hbCBpbmZvcm1hdGlvbiwgcGxlYXNlIGNv bnRhY3QgdGhlIGxpc3QgYWRtaW5pc3RyYXRvcnMu --====003__MESSAGE__ID__54yg6f6h6y456345==== Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: base64 PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv L0VOIj4NCjxIVE1MPjxIRUFEPg0KPFNUWUxFIHR5cGU9dGV4dC9jc3M+IDwhLS1AaW1wb3J0IHVy bChzY3JvbGxiYXIuY3NzKTsgLS0+PC9TVFlMRT4NCg0KPE1FVEEgY29udGVudD0idGV4dC9odG1s OyBjaGFyc2V0PXV0Zi04IiBodHRwLWVxdWl2PUNvbnRlbnQtVHlwZT4NCjxTVFlMRT4JCQlib2R5 e0ZPTlQtU0laRToxMnB0OyBGT05ULUZBTUlMWTrlrovkvZMsc2VyaWY7fQkJPC9TVFlMRT4NCg0K PE1FVEEgbmFtZT1HRU5FUkFUT1IgY29udGVudD0iTVNIVE1MIDExLjAwLjk2MDAuMTY0MTIiPjxC QVNFIA0KdGFyZ2V0PV9ibGFuaz48L0hFQUQ+DQo8Qk9EWSANCnN0eWxlPSJCT1JERVItTEVGVC1X SURUSDogMHB4OyBCT1JERVItUklHSFQtV0lEVEg6IDBweDsgQk9SREVSLUJPVFRPTS1XSURUSDog MHB4OyBNQVJHSU46IDEycHg7IExJTkUtSEVJR0hUOiAxLjM7IEJPUkRFUi1UT1AtV0lEVEg6IDBw eCIgDQptYXJnaW5oZWlnaHQ9IjAiIG1hcmdpbndpZHRoPSIwIj4NCjxESVY+PEZPTlQgc2l6ZT0y IGZhY2U9VmVyZGFuYT4NCjxESVYgZGlyPWx0cj5IaSBhbGwsDQo8RElWIGRpcj1sdHI+Jm5ic3A7 PC9ESVY+DQo8RElWIGRpcj1sdHI+QSBuZXcgbWFpbGluZyBsaXN0IGhhcyBiZWVuIGVzdGFibGlz aGVkIGZvciBJbnRlcm5ldCBTdG9yYWdlIFN5bmMgDQooSVNTKSB3b3JrLiBXZSd2ZSBtYWRlIGEg cmVsZXZhbnQgcHJlc2VudGF0aW9uIGFib3V0IHRoaXMgd29yayBpbiBQcmFndWUuIFdlIA0Kc3Rp bGwgc3RhcnQgcmVsYXRlZCBkaXNjdXNzaW9ucyAoZS5nLiBwcm9ibGVtcywgc2NvcGUgb2Ygd29y ayBhbmQgZXRjLikgb24gaXQgDQpzb29uIGFuZCBhbnkgaW50ZXJlc3RlZCBwZW9wbGUgYXJlIG1v cmUgdGhhbiB3ZWxjb21lIHRvIHN1YnNjcmliZSBpdC4gRm9sbG93aW5nIA0KcGxlYXNlIGZpbmQg dGhlIGxpc3QgYWRkcmVzcyBhbmQgZGV0YWlsZWQgcHVycG9zZSBvZiB0aGUgbWFpbGluZyBsaXN0 LjwvRElWPg0KPERJViBkaXI9bHRyPiZuYnNwOzwvRElWPg0KPERJViBkaXI9bHRyPlJlZ2FyZHMs PC9ESVY+DQo8RElWIGRpcj1sdHI+WW9uZyBDdWksPC9ESVY+DQo8RElWIGRpcj1sdHI+Jm5ic3A7 PC9ESVY+DQo8RElWIGRpcj1sdHI+DQo8RElWIGRpcj1sdHI+UHJvZmVzc29yLCBUc2luZ2h1YSBV bml2ZXJzaXR5LCBCZWlqaW5nLCBDaGluYTwvRElWPg0KPERJViBkaXI9bHRyPkFzc29jaWF0ZSBF ZGl0b3Igb24gSUVFRSBUUERTLCBJRUVFIFRDQzwvRElWPg0KPERJViBkaXI9bHRyPlVSTDogPEEg DQpocmVmPSJodHRwOi8vd3d3LjRvdmVyNi5lZHUuY24vY3VpeW9uZy9pbmRleC5odG1sIj5odHRw Oi8vd3d3LjRvdmVyNi5lZHUuY24vY3VpeW9uZy9pbmRleC5odG1sPC9BPjxCUj48L0RJVj48L0RJ Vj4NCjxESVYgY2xhc3M9Z21haWxfcXVvdGU+LS0tLS0tLS0tLSBGb3J3YXJkZWQgbWVzc2FnZSAt LS0tLS0tLS0tPEJSPkZyb206IDxCIA0KY2xhc3M9Z21haWxfc2VuZGVybmFtZT5JRVRGIFNlY3Jl dGFyaWF0PC9CPiA8U1BBTiBkaXI9bHRyPiZsdDs8QSANCmhyZWY9Im1haWx0bzppZXRmLXNlY3Jl dGFyaWF0QGlldGYub3JnIj5pZXRmLXNlY3JldGFyaWF0QGlldGYub3JnPC9BPiZndDs8L1NQQU4+ PEJSPkRhdGU6IA0KMjAxNS0wOC0yMSAwOjUxIEdNVCswODowMDxCUj5TdWJqZWN0OiBOZXcgTm9u LVdHIE1haWxpbmcgTGlzdDogU3RvcmFnZXN5bmMgLS0gDQpNZWNoYW5pc21zIHRvIHN5bmNocm9u aXplIGNsaWVudCBmaWxlIHN5c3RlbXMgd2l0aCBJbnRlcm5ldC1iYXNlZCBkYXRhIHN0b3JhZ2Ug DQpzZXJ2aWNlczxCUj5UbzogSUVURiBBbm5vdW5jZW1lbnQgTGlzdCAmbHQ7PEEgDQpocmVmPSJt YWlsdG86aWV0Zi1hbm5vdW5jZUBpZXRmLm9yZyI+aWV0Zi1hbm5vdW5jZUBpZXRmLm9yZzwvQT4m Z3Q7PEJSPkNjOiA8QSANCmhyZWY9Im1haWx0bzpjdWl5b25nQHRzaW5naHVhLmVkdS5jbiI+Y3Vp eW9uZ0B0c2luZ2h1YS5lZHUuY248L0E+LCA8QSANCmhyZWY9Im1haWx0bzpTdG9yYWdlc3luY0Bp ZXRmLm9yZyI+U3RvcmFnZXN5bmNAaWV0Zi5vcmc8L0E+PEJSPjxCUj48QlI+QSBuZXcgDQpJRVRG IG5vbi13b3JraW5nIGdyb3VwIGVtYWlsIGxpc3QgaGFzIGJlZW4gY3JlYXRlZC48QlI+PEJSPkxp c3QgYWRkcmVzczogPEEgDQpocmVmPSJtYWlsdG86c3RvcmFnZXN5bmNAaWV0Zi5vcmciPnN0b3Jh Z2VzeW5jQGlldGYub3JnPC9BPjxCUj5BcmNoaXZlOiA8QSANCmhyZWY9Imh0dHBzOi8vbWFpbGFy Y2hpdmUuaWV0Zi5vcmcvYXJjaC9zZWFyY2gvP2VtYWlsX2xpc3Q9c3RvcmFnZXN5bmMiIA0KcmVs PW5vcmVmZXJyZXIgDQp0YXJnZXQ9X2JsYW5rPmh0dHBzOi8vbWFpbGFyY2hpdmUuaWV0Zi5vcmcv YXJjaC9zZWFyY2gvP2VtYWlsX2xpc3Q9c3RvcmFnZXN5bmM8L0E+PEJSPlRvIA0Kc3Vic2NyaWJl OiA8QSBocmVmPSJodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3N0b3JhZ2Vz eW5jIiANCnJlbD1ub3JlZmVycmVyIA0KdGFyZ2V0PV9ibGFuaz5odHRwczovL3d3dy5pZXRmLm9y Zy9tYWlsbWFuL2xpc3RpbmZvL3N0b3JhZ2VzeW5jPC9BPjxCUj48QlI+UHVycG9zZTo8QlI+PEJS Pk5ldHdvcmstYmFzZWQgDQpzdG9yYWdlIHNlcnZpY2VzLCBzdWNoIGFzIGNsb3VkIHN0b3JhZ2Us IGF0dHJhY3QgaHVnZSBudW1iZXJzIG9mIHVzZXJzIGFuZCANCnByb2R1Y2UgYSBzaWduaWZpY2Fu dCBzaGFyZSBvZiBJbnRlcm5ldCB0cmFmZmljLiBCdXQgbW9zdCBleGlzdGluZyBuZXR3b3JrIA0K c3RvcmFnZSBzZXJ2aWNlcyBtYWtlIHVzZSBvZiBwcm9wcmlldGFyeSBzeW5jIHByb3RvY29scyB0 byBhY2hpZXZlIGRhdGEgDQpzeW5jaHJvbml6YXRpb24uIEFsbW9zdCBhbGwgb2YgdGhlbSBoYXZl IHByb3ZlZCBub3QgdG8gYmUgZWZmaWNpZW50IGVub3VnaCBhbmQgDQpzaG91bGQgYmUgaW1wcm92 ZWQuIFRoaXMgbWFpbGluZyBsaXN0IGlzIGZvciBkaXNjdXNzaW9uIG9mIHByb2JsZW1zIGNhdXNl ZCBieSANCmluZWZmaWNpZW50IHByb3ByaWV0YXJ5IHN5bmMgcHJvdG9jb2xzIGFuZCBvZiBhbHRl cm5hdGl2ZXMgdGhhdCBjYW4gYmUgbW9yZSANCmVmZmljaWVudCBhbmQgc3RhbmRhcmRpemVkLjxC Uj48QlI+Rm9yIGFkZGl0aW9uYWwgaW5mb3JtYXRpb24sIHBsZWFzZSBjb250YWN0IA0KdGhlIGxp c3QgYWRtaW5pc3RyYXRvcnMuPEJSPjxCUj48L0RJVj48QlI+PC9ESVY+PC9GT05UPjwvRElWPjwv Qk9EWT48L0hUTUw+ --====003__MESSAGE__ID__54yg6f6h6y456345====-- From nobody Wed Aug 26 15:44:50 2015 Return-Path: X-Original-To: apps-discuss@ietfa.amsl.com Delivered-To: apps-discuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD0211B341E; Wed, 26 Aug 2015 15:44:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zMZEpjiciqDF; Wed, 26 Aug 2015 15:44:47 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BDB51B34BA; Wed, 26 Aug 2015 15:44:42 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.4.1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20150826224442.10659.61205.idtracker@ietfa.amsl.com> Date: Wed, 26 Aug 2015 15:44:42 -0700 Archived-At: Cc: apps-discuss@ietf.org Subject: [apps-discuss] I-D Action: draft-ietf-appsawg-text-markdown-09.txt X-BeenThere: apps-discuss@ietf.org X-Mailman-Version: 2.1.15 List-Id: General discussion of application-layer protocols List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Aug 2015 22:44:49 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the ART Area General Applications Working Group Working Group of the IETF. Title : The text/markdown Media Type Author : Sean Leonard Filename : draft-ietf-appsawg-text-markdown-09.txt Pages : 14 Date : 2015-08-26 Abstract: This document registers the text/markdown media type for use with Markdown, a family of plain text formatting syntaxes that optionally can be converted to formal markup languages such as HTML. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-appsawg-text-markdown/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-appsawg-text-markdown-09 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-appsawg-text-markdown-09 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Wed Aug 26 15:45:54 2015 Return-Path: X-Original-To: apps-discuss@ietfa.amsl.com Delivered-To: apps-discuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F0AD51B34FD; Wed, 26 Aug 2015 15:45:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JNHFfPyPKkKA; Wed, 26 Aug 2015 15:45:51 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BF371B350F; Wed, 26 Aug 2015 15:45:46 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.4.1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20150826224546.9896.76701.idtracker@ietfa.amsl.com> Date: Wed, 26 Aug 2015 15:45:46 -0700 Archived-At: Cc: apps-discuss@ietf.org Subject: [apps-discuss] I-D Action: draft-ietf-appsawg-text-markdown-use-cases-03.txt X-BeenThere: apps-discuss@ietf.org X-Mailman-Version: 2.1.15 List-Id: General discussion of application-layer protocols List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Aug 2015 22:45:53 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the ART Area General Applications Working Group Working Group of the IETF. Title : Guidance on Markdown: Design Philosophies, Stability Strategies, and Select Registrations Author : Sean Leonard Filename : draft-ietf-appsawg-text-markdown-use-cases-03.txt Pages : 25 Date : 2015-08-26 Abstract: This document elaborates upon the text/markdown media type for use with Markdown, a family of plain text formatting syntaxes that optionally can be converted to formal markup languages such as HTML. Background information, local storage strategies, and additional syntax registrations are supplied. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-appsawg-text-markdown-use-cases/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-appsawg-text-markdown-use-cases-03 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-appsawg-text-markdown-use-cases-03 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Thu Aug 27 13:39:31 2015 Return-Path: X-Original-To: apps-discuss@ietfa.amsl.com Delivered-To: apps-discuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BF8A1A8762 for ; Thu, 27 Aug 2015 13:39:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.909 X-Spam-Level: X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UIiBSN512Asa for ; Thu, 27 Aug 2015 13:39:19 -0700 (PDT) Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 75D2B1A8733 for ; Thu, 27 Aug 2015 13:39:19 -0700 (PDT) Received: from unnumerable.local (pool-71-170-237-80.dllstx.fios.verizon.net [71.170.237.80]) (authenticated bits=0) by nostrum.com (8.15.2/8.14.9) with ESMTPSA id t7RKdI32031685 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=OK) for ; Thu, 27 Aug 2015 15:39:19 -0500 (CDT) (envelope-from rjsparks@nostrum.com) X-Authentication-Warning: raven.nostrum.com: Host pool-71-170-237-80.dllstx.fios.verizon.net [71.170.237.80] claimed to be unnumerable.local Message-ID: <55DF7571.7070108@nostrum.com> Date: Thu, 27 Aug 2015 15:39:13 -0500 From: Robert Sparks User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: IETF Apps Discuss References: <55DF7527.1020201@nostrum.com> In-Reply-To: <55DF7527.1020201@nostrum.com> X-Forwarded-Message-Id: <55DF7527.1020201@nostrum.com> Content-Type: multipart/alternative; boundary="------------060900040905040707010005" Archived-At: Subject: [apps-discuss] Fwd: Help test IMAP access to the IETF archives X-BeenThere: apps-discuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion of application-layer protocols List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Aug 2015 20:39:25 -0000 This is a multi-part message in MIME format. --------------060900040905040707010005 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit For those who are not watching IETF General: Please help get this word out. -------- Forwarded Message -------- Subject: Help test IMAP access to the IETF archives Date: Thu, 27 Aug 2015 15:37:59 -0500 From: Robert Sparks Reply-To: Robert Sparks To: ietf@ietf.org Folks - We have been testing IMAP access to the IETF archives for several days now, with volunteers from the tools-discuss and ietf chairs lists, and it's been going well. Thank you if you've been helping test already (and please continue to do so)! Now we need more testers. We'd like to get a simple measure of load, so we'd like to have as many folks as are willing accessing the test instance at the same time with various clients during the next week. It would be particularly helpful to have several people using the system next Thursday. If you're willing to take the time to do this, please drop me a note directly (I've set reply-to on this message) so I have a feel for how many people are participating. Instructions for accessing the test instance are below. Please report any issues you find directly to me. Do not open tickets with the secretariat. Be aware that there are known issues with the data on the test instance (some lists have blank or truncated messages) that have not yet been addressed - it would be good to report any more you find to me, but they won't get fixed immediately. Please use tools-discuss@ietf.org for general conversation. If you have feature requests, that's a good place to send them. One request we've had from a few testers so far is to provide an additional shared folder with a mailbox for each list that has only the "recent" messages from that list - perhaps the last 6 months. It would be good to hear from folks, after they've tried what's there now, whether that would be useful to spend development time on, or if that time would be better spent elsewhere. The test instance is getting mail with only a slight delay after it comes through the lists - you should see current traffic. Please resist the temptation to download the entire archive of every list. I've done it - it's huge (~28G when MailMate does it) and it it's a severe torture test for clients. Interrupt your client if it starts trying to do that to you. Caching a copy of this test instance will not be useful when we deploy the production instance. Instead, what would help us the most is to configure your client to access those lists you normally subscribe to, and to spend some time next week browsing and searching those lists and exploring a few lists that are new to you. You can find the details for where the test instance is listening, and rudimentary instructions for setting up a few clients, at . Please improve that page as you see the opportunity. Thanks in advance for any time you can give this. RjS --------------060900040905040707010005 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit For those who are not watching IETF General:

Please help get this word out.


-------- Forwarded Message --------
Subject: Help test IMAP access to the IETF archives
Date: Thu, 27 Aug 2015 15:37:59 -0500
From: Robert Sparks <rjsparks@nostrum.com>
Reply-To: Robert Sparks <rjsparks@nostrum.com>
To: ietf@ietf.org <ietf@ietf.org> 


Folks -

We have been testing IMAP access to the IETF archives for several days 
now, with volunteers from the tools-discuss and ietf chairs lists, and 
it's been going well. Thank you if you've been helping test already (and 
please continue to do so)!

Now we need more testers. We'd like to get a simple measure of load, so 
we'd like to have as many folks as are willing accessing the test 
instance at the same time with various clients during the next week. It 
would be particularly helpful to have several people using the system 
next Thursday.

If you're willing to take the time to do this, please drop me a note 
directly (I've set reply-to on this message) so I have a feel for how 
many people are participating.

Instructions for accessing the test instance are below.

Please report any issues you find directly to me. Do not open tickets 
with the secretariat. Be aware that there are known issues with the data 
on the test instance (some lists have blank or truncated messages) that 
have not yet been addressed - it would be good to report any more you 
find to me, but they won't get fixed immediately.

Please use tools-discuss@ietf.org for general conversation. If you have 
feature requests, that's a good place to send them. One request we've 
had from a few testers so far is to provide an additional shared folder 
with a mailbox for each list that has only the "recent" messages from 
that list - perhaps the last 6 months. It would be good to hear from 
folks, after they've tried what's there now, whether that would be 
useful to spend development time on, or if that time would be better 
spent elsewhere.

The test instance is getting mail with only a slight delay after it 
comes through the lists - you should see current traffic.

Please resist the temptation to download the entire archive of every 
list. I've done it - it's huge (~28G when MailMate does it) and it it's 
a severe torture test for clients. Interrupt your client if it starts 
trying to do that to you. Caching a copy of this test instance will not 
be useful when we deploy the production instance.

Instead, what would help us the most is to configure your client to 
access those lists you normally subscribe to, and to spend some time 
next week browsing and searching those lists and exploring a few lists 
that are new to you.

You can find the details for where the test instance is listening, and 
rudimentary instructions for setting up a few clients, at 
<http://trac.tools.ietf.org/group/tools/trac/wiki/ImapTesting>. Please 
improve that page as you see the opportunity.

Thanks in advance for any time you can give this.

RjS


--------------060900040905040707010005-- From nobody Sat Aug 29 02:42:12 2015 Return-Path: X-Original-To: apps-discuss@ietfa.amsl.com Delivered-To: apps-discuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52AC51AD06A for ; Sat, 29 Aug 2015 02:42:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.912 X-Spam-Level: X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tr1b5FgjoK2J for ; Sat, 29 Aug 2015 02:42:09 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id CE5AC1ACF60 for ; Sat, 29 Aug 2015 02:42:09 -0700 (PDT) Received: by rfc-editor.org (Postfix, from userid 30) id 9D27F180478; Sat, 29 Aug 2015 02:41:48 -0700 (PDT) To: pbryan@anode.ca, mnot@mnot.net, barryleiba@computer.org, superuser@gmail.com, alexey.melnikov@isode.com X-PHP-Originating-Script: 6000:errata_mail_lib.php From: RFC Errata System Message-Id: <20150829094148.9D27F180478@rfc-editor.org> Date: Sat, 29 Aug 2015 02:41:48 -0700 (PDT) Archived-At: Cc: hairmare@purplehaze.ch, apps-discuss@ietf.org, rfc-editor@rfc-editor.org Subject: [apps-discuss] [Editorial Errata Reported] RFC6902 (4460) X-BeenThere: apps-discuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion of application-layer protocols List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Aug 2015 09:42:11 -0000 The following errata report has been submitted for RFC6902, "JavaScript Object Notation (JSON) Patch". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=6902&eid=4460 -------------------------------------- Type: Editorial Reported by: Lucas Bickel Section: 4.1 Original Text ------------- However, the object itself or an array containing it does need to exist, and it remains an error for that not to be the case. For example, an "add" with a target location of "/a/b" starting with this document: { "a": { "foo": 1 } } is not an error, because "a" exists, and "b" will be added to its value. It is an error in this document: { "q": { "bar": 2 } } because "a" does not exist. Corrected Text -------------- However, the object itself or an array containing it does need to exist, and it remains an error for that not to be the case. For example, an "add" with a target location of "/a/b" starting with this document: { "a": { "foo": 1 } } is not an error, because "a" exists, and "b" will be added to its value. It is an error in this document: { "q": { "bar": 2 } } because "a" does not exist. Considering a target location of "/a/1" it should be not be an error in this document: { "a": [ "foo" ] } while the same "add" into this document will be an error: { "a": [ ] } because "/a/0" does not exist. Notes ----- Adding to an object has such a nice example that explains the error cases. I think adding to a sequential array should have one as well. To my understanding this is already pretty clear from RFC6901, I feel it will make the spec easier to implement if we have an example right here. Instructions: ------------- This erratum is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party (IESG) can log in to change the status and edit the report, if necessary. -------------------------------------- RFC6902 (draft-ietf-appsawg-json-patch-10) -------------------------------------- Title : JavaScript Object Notation (JSON) Patch Publication Date : April 2013 Author(s) : P. Bryan, Ed., M. Nottingham, Ed. Category : PROPOSED STANDARD Source : Applications Area Working Group APP Area : Applications Stream : IETF Verifying Party : IESG From nobody Sat Aug 29 06:53:00 2015 Return-Path: X-Original-To: apps-discuss@ietfa.amsl.com Delivered-To: apps-discuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CFB501AC3B9 for ; Sat, 29 Aug 2015 06:52:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.278 X-Spam-Level: X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OH8IhE9efbLF for ; Sat, 29 Aug 2015 06:52:57 -0700 (PDT) Received: from mail-vk0-x229.google.com (mail-vk0-x229.google.com [IPv6:2607:f8b0:400c:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 06FC51A88E9 for ; Sat, 29 Aug 2015 06:52:57 -0700 (PDT) Received: by vkhf67 with SMTP id f67so20892518vkh.1 for ; Sat, 29 Aug 2015 06:52:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=ahM0nLxjoi7evKwjDDtztZkNqhEqIRMqIH/3iBEYl7E=; b=of+Qc52dYWSc3Y7x1i4MdhzOw4RJK07B2xusY2ntzMzfE+JdeWtEFOmGJKNV+Kx+q2 4GtCNW+qYUTLWZEWMyAEN1RpABFUCpoGdgZ6qPrUpeJPxNbKCpPJrPjdTWltFr+f9M2A veeOkhOD+vsI0BppC72n5lxO06ddyFAji7JIMtLQfVa9eWlhyVOJuAUT+Eo1F3W4a8no b9GCL5UH8OIJQttDoeIeI+Zn4SEAQTdWGkTlbBNn4t4Nbp+CLNK2auDWWlx2Cfhb8Dy2 JFntU0N8YOpTvYAa+50zHS2QtCtCDYqB0kO96/Y7lY+2b/mF/NBUmRTZ51LI/Z+Tpj6B QBfg== MIME-Version: 1.0 X-Received: by 10.52.32.230 with SMTP id m6mr12374940vdi.80.1440856376223; Sat, 29 Aug 2015 06:52:56 -0700 (PDT) Sender: barryleiba@gmail.com Received: by 10.31.88.196 with HTTP; Sat, 29 Aug 2015 06:52:56 -0700 (PDT) In-Reply-To: <20150829094148.9D27F180478@rfc-editor.org> References: <20150829094148.9D27F180478@rfc-editor.org> Date: Sat, 29 Aug 2015 09:52:56 -0400 X-Google-Sender-Auth: znvwE1cwe6a5_-RhwtXPKBPw6Tg Message-ID: From: Barry Leiba To: RFC Errata System Content-Type: text/plain; charset=UTF-8 Archived-At: Cc: Apps Discuss , Mark Nottingham , hairmare@purplehaze.ch, Jamie Nelson Subject: Re: [apps-discuss] [Editorial Errata Reported] RFC6902 (4460) X-BeenThere: apps-discuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion of application-layer protocols List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Aug 2015 13:52:59 -0000 Thanks for the comment, Lucas. The errata report has been posted to the apps-discuss list, and I'm going to forward it to the json mailing list so it's recorded there for future reference. The errata system, though, isn't meant for suggestions, but for recording actual errors in the documents -- so I'm going to mark this "rejected" with a comment that the suggestion should be consider if a new version of the document is done. Barry, ART AD On Sat, Aug 29, 2015 at 5:41 AM, RFC Errata System wrote: > The following errata report has been submitted for RFC6902, > "JavaScript Object Notation (JSON) Patch". > > -------------------------------------- > You may review the report below and at: > http://www.rfc-editor.org/errata_search.php?rfc=6902&eid=4460 > > -------------------------------------- > Type: Editorial > Reported by: Lucas Bickel > > Section: 4.1 > > Original Text > ------------- > However, the object itself or an array containing it does need to > exist, and it remains an error for that not to be the case. For > example, an "add" with a target location of "/a/b" starting with this > document: > > { "a": { "foo": 1 } } > > is not an error, because "a" exists, and "b" will be added to its > value. It is an error in this document: > > { "q": { "bar": 2 } } > > because "a" does not exist. > > Corrected Text > -------------- > However, the object itself or an array containing it does need to > exist, and it remains an error for that not to be the case. For > example, an "add" with a target location of "/a/b" starting with this > document: > > { "a": { "foo": 1 } } > > is not an error, because "a" exists, and "b" will be added to its > value. It is an error in this document: > > { "q": { "bar": 2 } } > > because "a" does not exist. Considering a target location of "/a/1" > it should be not be an error in this document: > > { "a": [ "foo" ] } > > while the same "add" into this document will be an error: > > { "a": [ ] } > > because "/a/0" does not exist. > > > > > Notes > ----- > Adding to an object has such a nice example that explains the error cases. I think adding to a sequential array should have one as well. > > To my understanding this is already pretty clear from RFC6901, I feel it will make the spec easier to implement if we have an example right here. > > Instructions: > ------------- > This erratum is currently posted as "Reported". If necessary, please > use "Reply All" to discuss whether it should be verified or > rejected. When a decision is reached, the verifying party (IESG) > can log in to change the status and edit the report, if necessary. > > -------------------------------------- > RFC6902 (draft-ietf-appsawg-json-patch-10) > -------------------------------------- > Title : JavaScript Object Notation (JSON) Patch > Publication Date : April 2013 > Author(s) : P. Bryan, Ed., M. Nottingham, Ed. > Category : PROPOSED STANDARD > Source : Applications Area Working Group APP > Area : Applications > Stream : IETF > Verifying Party : IESG > From nobody Sat Aug 29 06:56:43 2015 Return-Path: X-Original-To: apps-discuss@ietfa.amsl.com Delivered-To: apps-discuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 95D431B32C1; Sat, 29 Aug 2015 06:56:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.912 X-Spam-Level: X-Spam-Status: No, score=-101.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VVl3AQs6bRjA; Sat, 29 Aug 2015 06:56:38 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 421FC1B32C0; Sat, 29 Aug 2015 06:56:38 -0700 (PDT) Received: by rfc-editor.org (Postfix, from userid 30) id 7F4D9181B3D; Sat, 29 Aug 2015 06:56:16 -0700 (PDT) To: hairmare@purplehaze.ch, pbryan@anode.ca, mnot@mnot.net X-PHP-Originating-Script: 1005:errata_mail_lib.php From: RFC Errata System Message-Id: <20150829135616.7F4D9181B3D@rfc-editor.org> Date: Sat, 29 Aug 2015 06:56:16 -0700 (PDT) Archived-At: Cc: barryleiba@computer.org, iesg@ietf.org, apps-discuss@ietf.org, rfc-editor@rfc-editor.org Subject: [apps-discuss] [Errata Rejected] RFC6902 (4460) X-BeenThere: apps-discuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion of application-layer protocols List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Aug 2015 13:56:39 -0000 The following errata report has been rejected for RFC6902, "JavaScript Object Notation (JSON) Patch". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=6902&eid=4460 -------------------------------------- Status: Rejected Type: Editorial Reported by: Lucas Bickel Date Reported: 2015-08-29 Rejected by: Barry Leiba (IESG) Section: 4.1 Original Text ------------- However, the object itself or an array containing it does need to exist, and it remains an error for that not to be the case. For example, an "add" with a target location of "/a/b" starting with this document: { "a": { "foo": 1 } } is not an error, because "a" exists, and "b" will be added to its value. It is an error in this document: { "q": { "bar": 2 } } because "a" does not exist. Corrected Text -------------- However, the object itself or an array containing it does need to exist, and it remains an error for that not to be the case. For example, an "add" with a target location of "/a/b" starting with this document: { "a": { "foo": 1 } } is not an error, because "a" exists, and "b" will be added to its value. It is an error in this document: { "q": { "bar": 2 } } because "a" does not exist. Considering a target location of "/a/1" it should be not be an error in this document: { "a": [ "foo" ] } while the same "add" into this document will be an error: { "a": [ ] } because "/a/0" does not exist. Notes ----- Adding to an object has such a nice example that explains the error cases. I think adding to a sequential array should have one as well. To my understanding this is already pretty clear from RFC6901, I feel it will make the spec easier to implement if we have an example right here. --VERIFIER NOTES-- Thanks for the comment, Lucas. This is, though, not a report of an error, so as an errata report it is rejected. It is a reasonable suggestion that we should consider if a new version of the document is done. The comment is recorded in the JSON mailing list archive. -------------------------------------- RFC6902 (draft-ietf-appsawg-json-patch-10) -------------------------------------- Title : JavaScript Object Notation (JSON) Patch Publication Date : April 2013 Author(s) : P. Bryan, Ed., M. Nottingham, Ed. Category : PROPOSED STANDARD Source : Applications Area Working Group APP Area : Applications Stream : IETF Verifying Party : IESG From nobody Mon Aug 31 00:40:49 2015 Return-Path: X-Original-To: apps-discuss@ietfa.amsl.com Delivered-To: apps-discuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C7DB1B3247; Mon, 31 Aug 2015 00:40:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kv4lfx67vkpi; Mon, 31 Aug 2015 00:40:45 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4332A1B3250; Mon, 31 Aug 2015 00:40:42 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.4.1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20150831074042.18679.3498.idtracker@ietfa.amsl.com> Date: Mon, 31 Aug 2015 00:40:42 -0700 Archived-At: Cc: apps-discuss@ietf.org Subject: [apps-discuss] I-D Action: draft-ietf-appsawg-text-markdown-10.txt X-BeenThere: apps-discuss@ietf.org X-Mailman-Version: 2.1.15 List-Id: General discussion of application-layer protocols List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Aug 2015 07:40:46 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the ART Area General Applications Working Group Working Group of the IETF. Title : The text/markdown Media Type Author : Sean Leonard Filename : draft-ietf-appsawg-text-markdown-10.txt Pages : 15 Date : 2015-08-31 Abstract: This document registers the text/markdown media type for use with Markdown, a family of plain text formatting syntaxes that optionally can be converted to formal markup languages such as HTML. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-appsawg-text-markdown/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-appsawg-text-markdown-10 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-appsawg-text-markdown-10 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Mon Aug 31 00:43:28 2015 Return-Path: X-Original-To: apps-discuss@ietfa.amsl.com Delivered-To: apps-discuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7FCF1B3311; Mon, 31 Aug 2015 00:43:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nVrjEJcY52Tv; Mon, 31 Aug 2015 00:43:25 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B349D1B32FF; Mon, 31 Aug 2015 00:43:23 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.4.1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20150831074323.5328.86446.idtracker@ietfa.amsl.com> Date: Mon, 31 Aug 2015 00:43:23 -0700 Archived-At: Cc: apps-discuss@ietf.org Subject: [apps-discuss] I-D Action: draft-ietf-appsawg-text-markdown-use-cases-04.txt X-BeenThere: apps-discuss@ietf.org X-Mailman-Version: 2.1.15 List-Id: General discussion of application-layer protocols List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Aug 2015 07:43:27 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the ART Area General Applications Working Group Working Group of the IETF. Title : Guidance on Markdown: Design Philosophies, Stability Strategies, and Select Registrations Author : Sean Leonard Filename : draft-ietf-appsawg-text-markdown-use-cases-04.txt Pages : 25 Date : 2015-08-31 Abstract: This document elaborates upon the text/markdown media type for use with Markdown, a family of plain text formatting syntaxes that optionally can be converted to formal markup languages such as HTML. Background information, local storage strategies, and additional syntax registrations are supplied. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-appsawg-text-markdown-use-cases/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-appsawg-text-markdown-use-cases-04 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-appsawg-text-markdown-use-cases-04 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Mon Aug 31 10:57:46 2015 Return-Path: X-Original-To: apps-discuss@ietfa.amsl.com Delivered-To: apps-discuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1764D1B2D7D; Mon, 31 Aug 2015 10:57:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AErW1t2vhmFu; Mon, 31 Aug 2015 10:57:40 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A2D571B2DDF; Mon, 31 Aug 2015 10:57:38 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.4.1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20150831175738.26607.50320.idtracker@ietfa.amsl.com> Date: Mon, 31 Aug 2015 10:57:38 -0700 Archived-At: Cc: apps-discuss@ietf.org Subject: [apps-discuss] I-D Action: draft-ietf-appsawg-text-markdown-use-cases-05.txt X-BeenThere: apps-discuss@ietf.org X-Mailman-Version: 2.1.15 List-Id: General discussion of application-layer protocols List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Aug 2015 17:57:42 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the ART Area General Applications Working Group Working Group of the IETF. Title : Guidance on Markdown: Design Philosophies, Stability Strategies, and Select Registrations Author : Sean Leonard Filename : draft-ietf-appsawg-text-markdown-use-cases-05.txt Pages : 25 Date : 2015-08-31 Abstract: This document elaborates upon the text/markdown media type for use with Markdown, a family of plain text formatting syntaxes that optionally can be converted to formal markup languages such as HTML. Background information, local storage strategies, and additional syntax registrations are supplied. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-appsawg-text-markdown-use-cases/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-appsawg-text-markdown-use-cases-05 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-appsawg-text-markdown-use-cases-05 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/