From owner-atom-syntax@mail.imc.org Wed Jul 2 14:15:41 2008 Return-Path: X-Original-To: ietfarch-atompub-archive@core3.amsl.com Delivered-To: ietfarch-atompub-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 25F4A3A6880 for ; Wed, 2 Jul 2008 14:15:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.999 X-Spam-Level: X-Spam-Status: No, score=-5.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_46=0.6, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7P3AYl5LA067 for ; Wed, 2 Jul 2008 14:15:40 -0700 (PDT) Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id A58EC3A6996 for ; Wed, 2 Jul 2008 14:15:36 -0700 (PDT) Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m62Kq7jc048932 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 2 Jul 2008 13:52:07 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id m62Kq7FO048931; Wed, 2 Jul 2008 13:52:07 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org) X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-atom-syntax@mail.imc.org using -f Received: from smtp-bedford.mitre.org (smtp-bedford.mitre.org [129.83.20.191]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m62Kq5TS048916; Wed, 2 Jul 2008 13:52:06 -0700 (MST) (envelope-from pauld@mitre.org) Received: from smtp-bedford.mitre.org (localhost.localdomain [127.0.0.1]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id m62Kq4H2008026; Wed, 2 Jul 2008 16:52:04 -0400 Received: from imcfe2.MITRE.ORG (imcfe2.mitre.org [129.83.29.4]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id m62Kq4Us008020; Wed, 2 Jul 2008 16:52:04 -0400 Received: from MM138572-PC.mitre.org ([172.31.18.115]) by imcfe2.MITRE.ORG with Microsoft SMTPSVC(6.0.3790.1830); Wed, 2 Jul 2008 16:52:04 -0400 X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Wed, 02 Jul 2008 16:51:24 -0400 To: www-ws-desc@w3.org, atom-protocol@imc.org, atom-syntax@imc.org From: Paul Denning Subject: Atom Category Document for WSDL? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Message-ID: X-OriginalArrivalTime: 02 Jul 2008 20:52:04.0291 (UTC) FILETIME=[7BA01930:01C8DC85] Sender: owner-atom-syntax@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: Given things like WSO2 Registry and Mule Galaxy, which provide Atom Publishing Protocol interfaces, it seems that it would be useful to have a "standard" atom:scheme and an associated Atom Category document. Compared to UDDI, Atom is generally considered more lightweight and ubiquitous. However, UDDI has some good aspects that perhaps should be modeled or imitated using Atom. For example, to register a WSDL document in UDDI [0], a tModel is created and some information gleened from the WSDL is used in the categoryBag. So, to find WSDL in UDDI, you search for tModels with a certain well-defined category in the categoryBag. [0] http://www.oasis-open.org/committees/uddi-spec/doc/tn/uddi-spec-tc-tn-wsdl-v2.htm Now that Atom Publishing Protocol (APP) is being used for publishing to a registry/repository, we should look at some conventions for the Atom category element to help users find WSDL and related SOA artifacts across (i.e., aggregation of) a set of heterogenous registry/repository feeds. That is, a large enterprise may have several registry/repositories, each with Atom feeds for WSDL, which I would like to aggregate into one composite feed for WSDL from across the enterprise. Finding the feeds for WSDL from among the many feeds that an enterprise may have should be easier. What I think this boils down to is a standard taxonomy (aka, value set, vocabulary) documented in an Atom Category Document [1]. [1] http://tools.ietf.org/html/rfc5023#section-7 For example, Obviously @scheme would benefit from an IRI defined by an established standards organization (W3C, OASIS, IETF, ...). Above I define only three terms, but others should be considered. The terms above would be used, respectively, to register/publish WSDL, WS-Policy, and BPEL. Therefore if the 'wsdlSpec' category were to appear in an Atom Entry or Feed Document, it would appear as: If a registry/repository wanted to offer a feed/collection of WSDL documents, then an Atom Service document might look like the following: Registry My Blog Entries WSDL application/wsdl+xml text/xml Has any of the above been considered? Paul From owner-atom-syntax@mail.imc.org Wed Jul 2 18:24:47 2008 Return-Path: X-Original-To: ietfarch-atompub-archive@core3.amsl.com Delivered-To: ietfarch-atompub-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A06AF3A686E for ; Wed, 2 Jul 2008 18:24:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.599 X-Spam-Level: X-Spam-Status: No, score=-4.599 tagged_above=-999 required=5 tests=[AWL=-2.000, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lLsmOnugq8nS for ; Wed, 2 Jul 2008 18:24:47 -0700 (PDT) Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id 6818A3A67F6 for ; Wed, 2 Jul 2008 18:24:46 -0700 (PDT) Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m631CZBY065458 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 2 Jul 2008 18:12:35 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id m631CZA8065457; Wed, 2 Jul 2008 18:12:35 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org) X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-atom-syntax@mail.imc.org using -f Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m631CXve065445 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 2 Jul 2008 18:12:34 -0700 (MST) (envelope-from mnot@mnot.net) Received: from [192.168.1.103] (unknown [124.108.98.217]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTP id 40E5AD05B8; Wed, 2 Jul 2008 21:12:31 -0400 (EDT) Cc: Atom Syntax , public-html@w3.org Message-Id: <30FBD88A-F46D-46A2-AFF5-65D5B3872486@mnot.net> From: Mark Nottingham To: HTTP Working Group Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Reply-To: HTTP Working Group Subject: Fwd: New Version Notification for draft-nottingham-http-link-header-02 Mime-Version: 1.0 (Apple Message framework v926) Date: Thu, 3 Jul 2008 11:12:28 +1000 References: <20080703010544.F1AB03A68A2@core3.amsl.com> X-Mailer: Apple Mail (2.926) Sender: owner-atom-syntax@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: Diff available here shortly (I hope): Cheers, Begin forwarded message: > From: IETF I-D Submission Tool > Date: 3 July 2008 11:05:44 AM > To: mnot@mnot.net > Subject: New Version Notification for draft-nottingham-http-link- > header-02 > > > A new version of I-D, draft-nottingham-http-link-header-02.txt has > been successfuly submitted by Mark Nottingham and posted to the IETF > repository. > > Filename: draft-nottingham-http-link-header > Revision: 02 > Title: HTTP Header Linking > Creation_date: 2008-07-03 > WG ID: Independent Submission > Number_of_pages: 13 > > Abstract: > This document clarifies the status of the Link HTTP header and > attempts to consolidate link relations in a single registry. > > > > The IETF Secretariat. > > -- Mark Nottingham http://www.mnot.net/ From owner-atom-syntax@mail.imc.org Wed Jul 2 22:22:17 2008 Return-Path: X-Original-To: ietfarch-atompub-archive@core3.amsl.com Delivered-To: ietfarch-atompub-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9E0A83A6A91 for ; Wed, 2 Jul 2008 22:22:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.881 X-Spam-Level: X-Spam-Status: No, score=-3.881 tagged_above=-999 required=5 tests=[AWL=-0.282, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g1DUu4pJfze1 for ; Wed, 2 Jul 2008 22:22:16 -0700 (PDT) Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id 286E73A68F1 for ; Wed, 2 Jul 2008 22:22:15 -0700 (PDT) Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m635A8S8080276 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 2 Jul 2008 22:10:08 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id m635A8mu080275; Wed, 2 Jul 2008 22:10:08 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org) X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-atom-syntax@mail.imc.org using -f Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m635A3PI080236 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for ; Wed, 2 Jul 2008 22:10:06 -0700 (MST) (envelope-from ga-atom-syntax@gmane.org) Received: from root by ciao.gmane.org with local (Exim 4.43) id 1KEH50-0007I5-Ck for atom-syntax@imc.org; Thu, 03 Jul 2008 05:10:02 +0000 Received: from hmbg-d9b88e39.pool.mediaways.net ([217.184.142.57]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 03 Jul 2008 05:10:02 +0000 Received: from hmdmhdfmhdjmzdtjmzdtzktdkztdjz by hmbg-d9b88e39.pool.mediaways.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 03 Jul 2008 05:10:02 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: atom-syntax@imc.org From: "Frank Ellermann" Subject: Re: New Version Notification for draft-nottingham-http-link-header-02 Date: Thu, 3 Jul 2008 05:11:33 +0200 Organization: Lines: 17 Message-ID: References: <20080703010544.F1AB03A68A2@core3.amsl.com> <30FBD88A-F46D-46A2-AFF5-65D5B3872486@mnot.net> Reply-To: "Frank Ellermann" Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: hmbg-d9b88e39.pool.mediaways.net X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1914 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1914 Cc: ietf-http-wg@w3.org Sender: owner-atom-syntax@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: Mark Nottingham wrote: =20 > Thanks. Looking at it, you fixed the base URI for registered relations, but you didn't tell IANA what they have to do. Maybe copy the blurb from... ...I'd like to get rid of it with a normative reference to your draft. If all goes well (of course it never does) rel=3D"search" can be the first user of your combined registry. Frank From c.schmitt@a-n-a.de Sat Jul 5 06:49:31 2008 Return-Path: X-Original-To: ietfarch-atompub-archive@core3.amsl.com Delivered-To: ietfarch-atompub-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A321A3A6869; Sat, 5 Jul 2008 06:49:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -60.384 X-Spam-Level: X-Spam-Status: No, score=-60.384 tagged_above=-999 required=5 tests=[BAYES_50=0.001, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, FS_REPLICA=0.994, FS_REPLICAWATCH=10.357, GB_ROLEX=5, HELO_DYNAMIC_IPADDR=2.426, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, REPLICA_WATCH=3.396, SARE_SPEC_REPLICA_OBFU=1.812, SARE_SPEC_ROLEX=1.666, SARE_SPEC_ROLEX_NOV5A=1.062, SARE_SPEC_ROLEX_REP=1.666, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qM-oFJ9cdXxO; Sat, 5 Jul 2008 06:49:30 -0700 (PDT) Received: from pc-59-1-104-200.cm.vtr.net (pc-59-1-104-200.cm.vtr.net [200.104.1.59]) by core3.amsl.com (Postfix) with SMTP id D7E2B3A6839; Sat, 5 Jul 2008 06:49:11 -0700 (PDT) X-Originating-IP: 6.44.168.84 by smtp.200.104.1.59; Sat, 05 Jul 2008 09:49:21 -0500 Message-ID: From: "Jose Mcgraw" Reply-To: "Jose Mcgraw" To: atompub-archive@megatron.ietf.org Subject: Famous replica watches rolex Cartier Bvlgari Date: Sat, 05 Jul 2008 09:49:21 -0500 Content-Type: text/plain; Content-Transfer-Encoding: 7Bit If the only thing standing between you and a luxurious Cartier watch is money, then today is your lucky day! Prestige Replicas, the world-famous replica watches dealer, is offering a 15% discount during these spring months for two or more watches, making their whole Cartier collection even more affordable. http://Laverneruhiro.blogspot.com/ As you are probably aware of, Prestige Replicas has one of the most extensive collections of Cartier replica watches in the whole wide web. Who cares if they are not legitimate? These replicas are of such high quality that not even a connoisseur would be able to distinguish them from an original Cartier. And with their online delivery guarantee you will be enjoying your new watch in just a couple of days! So, what are you waiting for? Visit Prestige Replicas today! http://Laverneruhiro.blogspot.com/ From owner-atom-syntax@mail.imc.org Thu Jul 10 11:21:41 2008 Return-Path: X-Original-To: ietfarch-atompub-archive@core3.amsl.com Delivered-To: ietfarch-atompub-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6ED123A67B6 for ; Thu, 10 Jul 2008 11:21:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.299 X-Spam-Level: X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BXrN651C-K7w for ; Thu, 10 Jul 2008 11:21:40 -0700 (PDT) Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id 195B43A6891 for ; Thu, 10 Jul 2008 11:21:36 -0700 (PDT) Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6AI8eqC016216 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 10 Jul 2008 11:08:40 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id m6AI8eFw016215; Thu, 10 Jul 2008 11:08:40 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org) X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-atom-syntax@mail.imc.org using -f Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.155]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6AI8cLA016182 for ; Thu, 10 Jul 2008 11:08:40 -0700 (MST) (envelope-from lindstream@gmail.com) Received: by fg-out-1718.google.com with SMTP id l26so1470322fgb.26 for ; Thu, 10 Jul 2008 11:08:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=jWDORg7RYZlKpBnTTEFly/1TDhVKRJl9+YdenmG9AXE=; b=cYI7fqlgpGbdapmLv6ZiCxN6EXN+QJ0rtEKlk4fu146exwkppaa5N0aW/5ryFLPwHa /aW+HT/kdeBn7hLibpt+7yQJunSmJLeZuGWgelipAwYvj1NeJ8GzrYGLllCYsKiC+Wmj z5JM5KZ0gx+4JxXmArhchiB7RGQljg2P+tv0A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=DkbNdUHi6ilUDvIjzN6hkBVs6RRT/TzZJJdK6WQ2SifuqBsCVJn5WxD2XYiVR323UH 5mM9+1SsQI3epaS9GvgfhKjvspUJSaScznt7jv0IjcMzRJsymNrR7g0s49qQr2l+40WL POLwVyFaYli515mkwn9NGeKcwwzxafIWj7CnE= Received: by 10.86.90.2 with SMTP id n2mr8890541fgb.51.1215713318081; Thu, 10 Jul 2008 11:08:38 -0700 (PDT) Received: by 10.86.9.19 with HTTP; Thu, 10 Jul 2008 11:08:38 -0700 (PDT) Message-ID: Date: Thu, 10 Jul 2008 20:08:38 +0200 From: "=?ISO-8859-1?Q?Niklas_Lindstr=F6m?=" To: atom-syntax@imc.org Subject: Checksums and Link Extensions MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Sender: owner-atom-syntax@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: Hi! I need to supply checksums in Atom entries for resources linked via content/@src or link/@href. I currently use the Link Extensions [1] attribute le:md5, which fits my need precisely. But is this I-D abandoned? Is it of interest to anyone else today, or should I go another route for this? If nothing comparable for signatures exists, how much work would it be to revitalise it (and perhaps add e.g. an le:sha1 for completeness)? (While it's also possible to send the Content-MD5 HTTP header for the actual resource, I would strongly prefer to have the checksums present in the entry itself. And since Atom entries work so well as "resource manifests", the extensions defined by this I-D look very natural to me.) I also wonder about the applicability of XML Digital Signatures [2] for this. I (primarily) need checksums for out-of-line references, and I haven't seen examples of using signatures (the Reference element with DigestMethod + DigestValue) in Atom for this specific case (that is, not signing the entry, only (some of) it's references). It also feels like an awful lot of XML for this quite simple use case. :) Does anyone have any advice for this practice? Best regards, Niklas Lindstr=F6m [1] =3D [2] =3D From owner-atom-syntax@mail.imc.org Thu Jul 10 14:19:14 2008 Return-Path: X-Original-To: ietfarch-atompub-archive@core3.amsl.com Delivered-To: ietfarch-atompub-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4EC973A6A85 for ; Thu, 10 Jul 2008 14:19:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.998 X-Spam-Level: X-Spam-Status: No, score=-5.998 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_21=0.6, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j5rLLJKnx55b for ; Thu, 10 Jul 2008 14:19:13 -0700 (PDT) Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id ECAB03A6A75 for ; Thu, 10 Jul 2008 14:19:12 -0700 (PDT) Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6AL61RP046010 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 10 Jul 2008 14:06:01 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id m6AL610q046009; Thu, 10 Jul 2008 14:06:01 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org) X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-atom-syntax@mail.imc.org using -f Received: from e34.co.us.ibm.com (e34.co.us.ibm.com [32.97.110.152]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6AL601n046002 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Thu, 10 Jul 2008 14:06:01 -0700 (MST) (envelope-from brunet@us.ibm.com) Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com [9.17.195.106]) by e34.co.us.ibm.com (8.13.8/8.13.8) with ESMTP id m6AL5xoR002674 for ; Thu, 10 Jul 2008 17:05:59 -0400 Received: from d03av01.boulder.ibm.com (d03av01.boulder.ibm.com [9.17.195.167]) by d03relay04.boulder.ibm.com (8.13.8/8.13.8/NCO v9.0) with ESMTP id m6AL5sAO095860 for ; Thu, 10 Jul 2008 15:05:59 -0600 Received: from d03av01.boulder.ibm.com (loopback [127.0.0.1]) by d03av01.boulder.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id m6AL5scm014117 for ; Thu, 10 Jul 2008 15:05:54 -0600 Received: from d03nm116.boulder.ibm.com (d03nm116.boulder.ibm.com [9.17.195.142]) by d03av01.boulder.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id m6AL5saa014109 for ; Thu, 10 Jul 2008 15:05:54 -0600 To: atom-syntax@imc.org MIME-Version: 1.0 Subject: link rel="search" X-Mailer: Lotus Notes Release 7.0 HF277 June 21, 2006 From: Pete Brunet Message-ID: Date: Thu, 10 Jul 2008 16:05:53 -0500 X-MIMETrack: Serialize by Router on D03NM116/03/M/IBM(Release 8.0.1|February 07, 2008) at 07/10/2008 15:05:54, Serialize complete at 07/10/2008 15:05:54 Content-Type: multipart/alternative; boundary="=_alternative 0073E49186257482_=" Sender: owner-atom-syntax@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: This is a multipart message in MIME format. --=_alternative 0073E49186257482_= Content-Type: text/plain; charset="US-ASCII" I see OpenSearch uses a link rel value of "search", but I don't see "search" in the RFC4287 spec 7.1 Registry of Link Relations This registry is maintained by IANA and initially contains five values: "alternate", "related", "self", "enclosure", and "via". New assignments are subject to IESG Approval What is the status of the "search" rel value? Example: Pete Brunet IBM Accessibility Architecture and Development 11501 Burnet Road, MS 9022E004, Austin, TX 78758 Voice: (512) 838-4594, Cell: (512) 689-4155 Ionosphere: WS4G --=_alternative 0073E49186257482_= Content-Type: text/html; charset="US-ASCII"
I see OpenSearch uses a link rel value of "search", but I don't see "search" in the RFC4287 spec

7.1 Registry of Link Relations
This registry is maintained by IANA and initially contains five values: "alternate", "related", "self", "enclosure", and "via". New assignments are subject to IESG Approval

What is the status of the "search" rel value?

Example:
   <link rel="search"
         href="http://example.com/opensearchdescription.xml"
         type="application/opensearchdescription+xml"
         title="Content Search" />

Pete Brunet
                                                                         
IBM Accessibility Architecture and Development
11501 Burnet Road, MS 9022E004, Austin, TX 78758
Voice: (512) 838-4594, Cell: (512) 689-4155
Ionosphere: WS4G
 --=_alternative 0073E49186257482_=-- From owner-atom-syntax@mail.imc.org Fri Jul 11 05:15:37 2008 Return-Path: X-Original-To: ietfarch-atompub-archive@core3.amsl.com Delivered-To: ietfarch-atompub-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 74FE03A69C2 for ; Fri, 11 Jul 2008 05:15:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.587 X-Spam-Level: X-Spam-Status: No, score=-0.587 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FAKE_REPLY_C=2.012] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sBV5TrVuacD4 for ; Fri, 11 Jul 2008 05:15:36 -0700 (PDT) Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id 2EBDB3A6875 for ; Fri, 11 Jul 2008 05:15:35 -0700 (PDT) Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6BC6LKQ014183 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 11 Jul 2008 05:06:21 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id m6BC6LhW014182; Fri, 11 Jul 2008 05:06:21 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org) X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-atom-syntax@mail.imc.org using -f Received: from harpo.laits.utexas.edu (harpo.laits.utexas.edu [128.83.27.7]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6BC6JBu014176 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 11 Jul 2008 05:06:20 -0700 (MST) (envelope-from pkeane@harpo.laits.utexas.edu) Received: from harpo.laits.utexas.edu (harpo.laits.utexas.edu [127.0.0.1]) by harpo.laits.utexas.edu (8.14.2/8.14.2) with ESMTP id m6BC6ISb007327 for ; Fri, 11 Jul 2008 07:06:18 -0500 Received: (from pkeane@localhost) by harpo.laits.utexas.edu (8.14.2/8.14.2/Submit) id m6BC6I4q007325 for atom-syntax@imc.org; Fri, 11 Jul 2008 07:06:18 -0500 Date: Fri, 11 Jul 2008 07:06:18 -0500 From: Peter Keane To: atom-syntax@imc.org Subject: Re: Checksums and Link Extensions Message-ID: <20080711120618.GB6246@harpo.laits.utexas.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.5.18 (2008-05-17) Sender: owner-atom-syntax@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: [to the list this time :-)] This & similar questions have come up numerous times here. I would, BTW, love to see something like the link extensions draft adopted. Meanwhile, there is: http://search.yahoo.com/mrss/ Which is pretty widely used. In a system I work on at UT Austin, we use Atom quite extensively for a digital asset management and presentation tool. By using the Media RSS extension we got (for free -- it was unintentional) very fancy slideshows with the PicLens Firefox Extension. It also specifies a way to state the MD5 checksum for the linked-to media items. --peter keane On Thu, Jul 10, 2008 at 08:08:38PM +0200, Niklas Lindström wrote: > > Hi! > > I need to supply checksums in Atom entries for resources linked via > content/@src or link/@href. I currently use the Link Extensions [1] > attribute le:md5, which fits my need precisely. > > But is this I-D abandoned? Is it of interest to anyone else today, or > should I go another route for this? If nothing comparable for > signatures exists, how much work would it be to revitalise it (and > perhaps add e.g. an le:sha1 for completeness)? > > (While it's also possible to send the Content-MD5 HTTP header for the > actual resource, I would strongly prefer to have the checksums present > in the entry itself. And since Atom entries work so well as "resource > manifests", the extensions defined by this I-D look very natural to > me.) > > I also wonder about the applicability of XML Digital Signatures [2] > for this. I (primarily) need checksums for out-of-line references, and > I haven't seen examples of using signatures (the Reference element > with DigestMethod + DigestValue) in Atom for this specific case (that > is, not signing the entry, only (some of) it's references). It also > feels like an awful lot of XML for this quite simple use case. :) > > Does anyone have any advice for this practice? > > Best regards, > Niklas Lindstr> > [1] = > [2] = ----- End forwarded message ----- From owner-atom-syntax@mail.imc.org Fri Jul 11 07:59:28 2008 Return-Path: X-Original-To: ietfarch-atompub-archive@core3.amsl.com Delivered-To: ietfarch-atompub-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 00D163A68A0 for ; Fri, 11 Jul 2008 07:59:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.299 X-Spam-Level: X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t7Gr9RQ29cQJ for ; Fri, 11 Jul 2008 07:59:27 -0700 (PDT) Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id B686E3A689A for ; Fri, 11 Jul 2008 07:59:26 -0700 (PDT) Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6BEnRFn033537 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 11 Jul 2008 07:49:28 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id m6BEnRxA033536; Fri, 11 Jul 2008 07:49:27 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org) X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-atom-syntax@mail.imc.org using -f Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.251]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6BEnQtn033529 for ; Fri, 11 Jul 2008 07:49:27 -0700 (MST) (envelope-from jasnell@gmail.com) Received: by an-out-0708.google.com with SMTP id c35so727363anc.44 for ; Fri, 11 Jul 2008 07:49:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=ucuCRiX4SAfiGD3/UJqRQ0W7Tn6Lb596EtWKK1uJLOA=; b=mlJFiqzMzvcA7RHjHVWh6E6QArKjnVfUAZFAYFAw6dbxJaMYDTc5LUXpQEmLVsqhnk RKoxam8gWFgLHv/WbhqM+YAcKmjfc3/EGHfbmxmNA4tiqvEWk+hAR/g6Zrpl0mCaPZg9 ZkBWqQ1xJDDjJQ/YFclBNeawOwAHjUuJZxEVk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=p7lFxcXKdZTRKeiggvda4SYrQrmh4B701LOGzewBoxbaK32SXcOi+KVTYI/1p3ps+W 59lE5EBUPcdEFuIEsluE/CMu3tFkhIZSBVpUBjTNTYVyoqiNzvGsxQ7f/L+a7GqT0MR+ uhwkDWiXud9iHf0kjeLUwkOet4fMlxtID4B5o= Received: by 10.100.197.7 with SMTP id u7mr5512774anf.27.1215787766148; Fri, 11 Jul 2008 07:49:26 -0700 (PDT) Received: from ?192.168.2.105? ( [98.224.93.96]) by mx.google.com with ESMTPS id d22sm685953and.2.2008.07.11.07.49.25 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 11 Jul 2008 07:49:25 -0700 (PDT) Message-ID: <48777318.9080407@gmail.com> Date: Fri, 11 Jul 2008 07:50:00 -0700 From: James M Snell User-Agent: Thunderbird 2.0.0.14 (X11/20080505) MIME-Version: 1.0 To: =?ISO-8859-1?Q?Niklas_Lindstr=F6m?= CC: atom-syntax@imc.org Subject: Re: Checksums and Link Extensions References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Sender: owner-atom-syntax@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: The draft was abandoned because of lack of community interest. I would have no problem resurrecting it if there is interest. - James Niklas Lindström wrote: > Hi! > > I need to supply checksums in Atom entries for resources linked via > content/@src or link/@href. I currently use the Link Extensions [1] > attribute le:md5, which fits my need precisely. > > But is this I-D abandoned? Is it of interest to anyone else today, or > should I go another route for this? If nothing comparable for > signatures exists, how much work would it be to revitalise it (and > perhaps add e.g. an le:sha1 for completeness)? > > (While it's also possible to send the Content-MD5 HTTP header for the > actual resource, I would strongly prefer to have the checksums present > in the entry itself. And since Atom entries work so well as "resource > manifests", the extensions defined by this I-D look very natural to > me.) > > I also wonder about the applicability of XML Digital Signatures [2] > for this. I (primarily) need checksums for out-of-line references, and > I haven't seen examples of using signatures (the Reference element > with DigestMethod + DigestValue) in Atom for this specific case (that > is, not signing the entry, only (some of) it's references). It also > feels like an awful lot of XML for this quite simple use case. :) > > Does anyone have any advice for this practice? > > Best regards, > Niklas Lindström > > [1] = > [2] = > > From owner-atom-syntax@mail.imc.org Fri Jul 11 09:00:22 2008 Return-Path: X-Original-To: ietfarch-atompub-archive@core3.amsl.com Delivered-To: ietfarch-atompub-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E642428C226 for ; Fri, 11 Jul 2008 09:00:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.299 X-Spam-Level: X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dMNqOEhfAu7y for ; Fri, 11 Jul 2008 09:00:22 -0700 (PDT) Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id 785E228C21A for ; Fri, 11 Jul 2008 09:00:21 -0700 (PDT) Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6BFpo6E040625 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 11 Jul 2008 08:51:50 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id m6BFpoaj040624; Fri, 11 Jul 2008 08:51:50 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org) X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-atom-syntax@mail.imc.org using -f Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.152]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6BFpmU5040617 for ; Fri, 11 Jul 2008 08:51:49 -0700 (MST) (envelope-from lindstream@gmail.com) Received: by fg-out-1718.google.com with SMTP id l26so1631700fgb.26 for ; Fri, 11 Jul 2008 08:51:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=+u6KcIx4AFKQWSDeMF5onyCjhoBob7cBVOvZfhx8854=; b=HebTdfTLD3UGb90E5U6qxdftTPVFyMrlHq3ATrFthAYwbDk4Tx71OJExiUiAeVhmkS U1hvwBjSylj4fCXN5XA6IQvdPNdayuFBO/FqqIgaxR5Mb6RmVRoeEiWZsLtCSDxfmn4h 7hiWTJLqYe1eQBk7NI1KpGK0Ka9oMk4FQhzWI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=gMBJDeoprR33bVs64jvu5jutXqrfVKliswilwIi5S7OEiSGQnlLIcITda8J8rbSY/h tTRl1nd3lsJUa/3z81NmjWFnEEt5t9k0WKt6VJZ0jr5z2knZHzgznupKT9F3Q3gJ68ZN TV6yJL8Jx5cLCe2ISjz9FEQ8uLbBiZ/+5Ie10= Received: by 10.86.57.9 with SMTP id f9mr10067530fga.66.1215791505310; Fri, 11 Jul 2008 08:51:45 -0700 (PDT) Received: by 10.86.9.19 with HTTP; Fri, 11 Jul 2008 08:51:45 -0700 (PDT) Message-ID: Date: Fri, 11 Jul 2008 17:51:45 +0200 From: "=?ISO-8859-1?Q?Niklas_Lindstr=F6m?=" To: "James M Snell" Subject: Re: Checksums and Link Extensions Cc: atom-syntax@imc.org In-Reply-To: <48777318.9080407@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <48777318.9080407@gmail.com> Sender: owner-atom-syntax@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: Sounds great! I for one am very interested, and at least Peter Keane as well it seems. :) It would be of great use for more secure transports where e.g. signing isn't viable. In my specific case our task is to collect document exports via Atom from over a hundred government agencies. All of whom probably won't have the capacity (at least initially) to sign their documents, but can reasonably provide an MD5 (and do the transport over HTTPS). Currently we believe the "more than nothing" of MD5 is enough to verify successful download. By relying on a Link Extensions spec, we hope the software we produce (intended to be opensourced eventually) will be more interoperable. (And of course we'd save ourselves the trouble of writing down how to supply the md5:s.) Of course, I'd still like to hear objections to this view (e.g. "md5 and https won't be enough, you really need signing for anything remotely secure"). Best regards, Niklas On Fri, Jul 11, 2008 at 4:50 PM, James M Snell wrote: > The draft was abandoned because of lack of community interest. I would h= ave > no problem resurrecting it if there is interest. > > - James > > Niklas Lindstr=F6m wrote: >> >> Hi! >> >> I need to supply checksums in Atom entries for resources linked via >> content/@src or link/@href. I currently use the Link Extensions [1] >> attribute le:md5, which fits my need precisely. >> >> But is this I-D abandoned? Is it of interest to anyone else today, or >> should I go another route for this? If nothing comparable for >> signatures exists, how much work would it be to revitalise it (and >> perhaps add e.g. an le:sha1 for completeness)? >> >> (While it's also possible to send the Content-MD5 HTTP header for the >> actual resource, I would strongly prefer to have the checksums present >> in the entry itself. And since Atom entries work so well as "resource >> manifests", the extensions defined by this I-D look very natural to >> me.) >> >> I also wonder about the applicability of XML Digital Signatures [2] >> for this. I (primarily) need checksums for out-of-line references, and >> I haven't seen examples of using signatures (the Reference element >> with DigestMethod + DigestValue) in Atom for this specific case (that >> is, not signing the entry, only (some of) it's references). It also >> feels like an awful lot of XML for this quite simple use case. :) >> >> Does anyone have any advice for this practice? >> >> Best regards, >> Niklas Lindstr=F6m >> >> [1] =3D >> [2] =3D >> >> > From owner-atom-syntax@mail.imc.org Sat Jul 12 06:24:56 2008 Return-Path: X-Original-To: ietfarch-atompub-archive@core3.amsl.com Delivered-To: ietfarch-atompub-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F28B328C0E7 for ; Sat, 12 Jul 2008 06:24:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.299 X-Spam-Level: X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fKUYEDKo6XW5 for ; Sat, 12 Jul 2008 06:24:55 -0700 (PDT) Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id 79C363A69D3 for ; Sat, 12 Jul 2008 06:24:54 -0700 (PDT) Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m6CDF6rt015437 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 12 Jul 2008 06:15:07 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id m6CDF6LX015436; Sat, 12 Jul 2008 06:15:06 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org) X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-atom-syntax@mail.imc.org using -f Received: from mail128.messagelabs.com (mail128.messagelabs.com [216.82.250.131]) by balder-227.proper.com (8.14.2/8.14.2) with SMTP id m6CDF5Ka015428 for ; Sat, 12 Jul 2008 06:15:06 -0700 (MST) (envelope-from Brett.Lindsley@motorola.com) X-VirusChecked: Checked X-Env-Sender: Brett.Lindsley@motorola.com X-Msg-Ref: server-6.tower-128.messagelabs.com!1215868504!2222890!1 X-StarScan-Version: 5.5.12.14.2; banners=-,-,- X-Originating-IP: [129.188.136.8] Received: (qmail 482 invoked from network); 12 Jul 2008 13:15:04 -0000 Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8) by server-6.tower-128.messagelabs.com with SMTP; 12 Jul 2008 13:15:04 -0000 Received: from il06exr02.mot.com (il06exr02.mot.com [129.188.137.132]) by motgate8.mot.com (8.12.11/Motorola) with ESMTP id m6CDF2Ol028898 for ; Sat, 12 Jul 2008 06:15:04 -0700 (MST) Received: from il06vts02.mot.com (il06vts02.mot.com [129.188.137.142]) by il06exr02.mot.com (8.13.1/Vontu) with SMTP id m6CDF1Kr025027 for ; Sat, 12 Jul 2008 08:15:01 -0500 (CDT) Received: from de01exm66.ds.mot.com (de01exm66.am.mot.com [10.176.8.17]) by il06exr02.mot.com (8.13.1/8.13.0) with ESMTP id m6CDF1Xo025024 for ; Sat, 12 Jul 2008 08:15:01 -0500 (CDT) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: Checksums and Link Extensions Date: Sat, 12 Jul 2008 09:14:53 -0400 Message-ID: <08AA4466F2952341B121759C24993B7C02F0856B@de01exm66.ds.mot.com> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Checksums and Link Extensions Thread-Index: Acjjcv68CGD+xKm9RiieSRINx5BLMwArcY2A References: <48777318.9080407@gmail.com> From: "Lindsley Brett-ABL001" To: =?iso-8859-1?Q?Niklas_Lindstr=F6m?= , "James M Snell" Cc: X-CFilter-Loop: Reflected Sender: owner-atom-syntax@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: I am interested in this as well. My particular application includes a = hash on the link (either MD5 or SHA1) and then signs the entry. Signing = the entry prevents the content or hash from being modified Brett Lindsley Motorola Labs Applied Research Technology Center -----Original Message----- From: owner-atom-syntax@mail.imc.org = [mailto:owner-atom-syntax@mail.imc.org] On Behalf Of Niklas Lindstr=F6m Sent: Friday, July 11, 2008 10:52 AM To: James M Snell Cc: atom-syntax@imc.org Subject: Re: Checksums and Link Extensions Sounds great! I for one am very interested, and at least Peter Keane as well it seems. :) It would be of great use for more secure transports where e.g. signing isn't viable. In my specific case our task is to collect document exports via Atom from over a hundred government agencies. All of whom probably won't have the capacity (at least initially) to sign their documents, but can reasonably provide an MD5 (and do the transport over HTTPS). Currently we believe the "more than nothing" of MD5 is enough to verify successful download. By relying on a Link Extensions spec, we hope the software we produce (intended to be opensourced eventually) will be more interoperable. (And of course we'd save ourselves the trouble of writing down how to supply the md5:s.) Of course, I'd still like to hear objections to this view (e.g. "md5 and https won't be enough, you really need signing for anything remotely secure"). Best regards, Niklas On Fri, Jul 11, 2008 at 4:50 PM, James M Snell = wrote: > The draft was abandoned because of lack of community interest. I = would have > no problem resurrecting it if there is interest. > > - James > > Niklas Lindstr=F6m wrote: >> >> Hi! >> >> I need to supply checksums in Atom entries for resources linked via >> content/@src or link/@href. I currently use the Link Extensions [1] >> attribute le:md5, which fits my need precisely. >> >> But is this I-D abandoned? Is it of interest to anyone else today, or >> should I go another route for this? If nothing comparable for >> signatures exists, how much work would it be to revitalise it (and >> perhaps add e.g. an le:sha1 for completeness)? >> >> (While it's also possible to send the Content-MD5 HTTP header for the >> actual resource, I would strongly prefer to have the checksums = present >> in the entry itself. And since Atom entries work so well as "resource >> manifests", the extensions defined by this I-D look very natural to >> me.) >> >> I also wonder about the applicability of XML Digital Signatures [2] >> for this. I (primarily) need checksums for out-of-line references, = and >> I haven't seen examples of using signatures (the Reference element >> with DigestMethod + DigestValue) in Atom for this specific case (that >> is, not signing the entry, only (some of) it's references). It also >> feels like an awful lot of XML for this quite simple use case. :) >> >> Does anyone have any advice for this practice? >> >> Best regards, >> Niklas Lindstr=F6m >> >> [1] =3D = >> [2] =3D >> >> >