
From owner-atom-syntax@mail.imc.org  Tue Sep  1 04:43:51 2009
Return-Path: <owner-atom-syntax@mail.imc.org>
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 2C4B03A6B14 for <ietfarch-atompub-archive@core3.amsl.com>; Tue,  1 Sep 2009 04:43:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.322
X-Spam-Level: 
X-Spam-Status: No, score=-8.322 tagged_above=-999 required=5 tests=[AWL=-2.276, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, 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 hQXZPD8O5pIF for <ietfarch-atompub-archive@core3.amsl.com>; Tue,  1 Sep 2009 04:43:50 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 2F2473A697C for <atompub-archive@ietf.org>; Tue,  1 Sep 2009 04:43:50 -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 n81BYj1k090994 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 1 Sep 2009 04:34:45 -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 n81BYjnr090993; Tue, 1 Sep 2009 04:34:45 -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 asmtpout019.mac.com (asmtpout019.mac.com [17.148.16.94]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n81BYeWK090986 for <atom-syntax@imc.org>; Tue, 1 Sep 2009 04:34:44 -0700 (MST) (envelope-from algermissen1971@mac.com)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Received: from [192.168.5.36] (nmd.sbx10788.miamioh.wayport.net [98.99.10.102]) by asmtp019.mac.com (Sun Java(tm) System Messaging Server 6.3-8.01 (built Dec 16 2008; 32bit)) with ESMTPSA id <0KPA0017DIT6MI00@asmtp019.mac.com> for atom-syntax@imc.org; Tue, 01 Sep 2009 04:34:19 -0700 (PDT)
Message-id: <A4CEEB71-CCC8-4EA2-9D05-D6C4BD8E9107@mac.com>
From: Jan Algermissen <algermissen1971@mac.com>
To: Atom-Syntax <atom-syntax@imc.org>
Subject: Atom Versioning
Date: Tue, 01 Sep 2009 07:34:18 -0400
X-Mailer: Apple Mail (2.936)
Sender: owner-atom-syntax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/atom-syntax/mail-archive/>
List-Unsubscribe: <mailto:atom-syntax-request@imc.org?body=unsubscribe>
List-ID: <atom-syntax.imc.org>

RFC 4287 states this about the XML format it defines:

'For convenience, this data format may be referred to as "Atom  
1.0"' [Section 1.2]

Does this imply the intention that forward compatible changes to the  
Atom syntax will be referred to as Atom 1.x and that incompatible  
changes would be referred to as Atom 2.x , 3.x,...?

IOW, is there an implied versioning scheme?

Jan


From laduffy@ag.state.nv.us  Tue Sep  1 08:33:08 2009
Return-Path: <laduffy@ag.state.nv.us>
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 5C3EF3A6CB8 for <ietfarch-atompub-archive@core3.amsl.com>; Tue,  1 Sep 2009 08:33:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -22.429
X-Spam-Level: 
X-Spam-Status: No, score=-22.429 tagged_above=-999 required=5 tests=[BAYES_95=3, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, HTML_IMAGE_ONLY_04=2.041, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_1=0.001, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RDNS_NONE=0.1, SARE_HTML_A_BODY=0.742, SARE_HTML_IMG_ONLY=1.666, TVD_SPACE_RATIO=2.219, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_WS_SURBL=10, 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 vCmbRuHmEeUj for <ietfarch-atompub-archive@core3.amsl.com>; Tue,  1 Sep 2009 08:33:02 -0700 (PDT)
Received: from adbi.org (unknown [118.71.102.57]) by core3.amsl.com (Postfix) with SMTP id CA07C28C768 for <atompub-archive@lists.ietf.org>; Tue,  1 Sep 2009 08:31:33 -0700 (PDT)
To: <atompub-archive@lists.ietf.org>
Subject: Delivery Status Notification
From: <atompub-archive@lists.ietf.org>
MIME-Version: 1.0
Importance: High
Content-Type: text/html
Message-Id: <20090901153134.CA07C28C768@core3.amsl.com>
Date: Tue,  1 Sep 2009 08:31:33 -0700 (PDT)

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
</HEAD>
<BODY><a href="http://warmopen.com/" target="_blank">
<img src="http://warmopen.com/dyuwqlk.jpg" border="0" alt="Show picture and go to site now!"></a></BODY></HTML>

From info@fedex.com  Tue Sep  1 15:15:02 2009
Return-Path: <info@fedex.com>
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 861443A6908 for <ietfarch-atompub-archive@core3.amsl.com>; Tue,  1 Sep 2009 15:15:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -85.478
X-Spam-Level: 
X-Spam-Status: No, score=-85.478 tagged_above=-999 required=5 tests=[ADVANCE_FEE_2=1.234, BAYES_99=3.5, DATE_IN_FUTURE_06_12=1.897, FORGED_MUA_OUTLOOK=3.116, FORGED_OUTLOOK_HTML=0.001, FORGED_OUTLOOK_TAGS=0.001, GB_I_LETTER=-2, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, HTML_MESSAGE=0.001, J_CHICKENPOX_32=0.6, MIME_HTML_ONLY=1.457, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_SORBS_WEB=0.619, 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 6oPZY8WD-pfS for <ietfarch-atompub-archive@core3.amsl.com>; Tue,  1 Sep 2009 15:15:01 -0700 (PDT)
Received: from ironport.cable.net.co (ironport.cable.net.co [200.118.2.77]) by core3.amsl.com (Postfix) with ESMTP id DBAF03A6A89 for <atompub-archive@lists.ietf.org>; Tue,  1 Sep 2009 15:15:00 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.44,314,1249275600";  d="jpg'145?scan'145,208,217,145";a="91309406"
Received: from artemis.cable.net.co ([200.118.2.59]) by ironport.cable.net.co with ESMTP; 01 Sep 2009 17:15:12 -0500
Received: from User ([202.96.159.221]) by artemis.cable.net.co (Sun Java System Messaging Server 6.2-7.06 (built Oct 6 2006)) with ESMTPA id <0KPB00618CEXSZ30@artemis.cable.net.co> for atompub-archive@lists.ietf.org; Tue, 01 Sep 2009 17:15:13 -0500 (COT)
Date: Tue, 01 Sep 2009 23:15:00 -0700
From: FEDEX ONLINE TEAM <info@fedex.com>
Subject: Credited to file ICB/WT/00876
To: Undisclosed recipients: ;
Reply-to: fedexpostdeliveryservices@live.com
Message-id: <0KPB0061CCF6SZ30@artemis.cable.net.co>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
Content-type: multipart/mixed; boundary="Boundary_(ID_Vw312WxmXQtPW2QsaVZ1Ow)"
X-Priority: 3
X-MSMail-priority: Normal
Sun-Java-System-SMTP-Warning: Lines longer than SMTP allows found and truncated.

This is a multi-part message in MIME format.

--Boundary_(ID_Vw312WxmXQtPW2QsaVZ1Ow)
Content-type: text/html; charset=Windows-1251
Content-transfer-encoding: 8BIT

<HTML><HEAD><TITLE></TITLE>
</HEAD>
<BODY bgcolor=#FFFFFF leftmargin=5 topmargin=5 rightmargin=5 bottommargin=5>
<FONT size=2 color=#000000 face="Arial">
<DIV>
<FONT size=3 color=#000000>Dear Customer !!! </FONT></DIV>
<DIV>
<FONT size=3 color=#000000> </FONT></DIV>
<DIV>
<FONT size=3 color=#000000>&nbsp;</FONT></DIV>
<DIV>
<FONT size=3 color=#000000>We have been waiting for you to contact us for your Confirmed Package that is registered with us for shipping to your residential location.We thought that the sender gave you our contact&nbsp; details and that you would have contacted us by now.we would also let you know that a letter is also attached to your package.However, we cannot quote its content to you via E-mail for&nbsp; privacy reasons. We understand that the content of your package itself is a Bank Draft worth $800,000.00 USD,in FedEx we do not ship money in CASH or in CHEQUES but in Bank Drafts only. The&nbsp; package is registered with us for mailing by your colleague, and your colleague explained that he is from the United States but he is in Nigeria for a three (3) month Surveying Project. for he is&nbsp; working with a consulting firm in Nigeria West Africa. We are sending you this E-mail because your package is been registered on a Special Order. What you have to do now, is to cont
 act our 
<DIV>
<FONT size=3 color=#000000>&nbsp;</FONT></DIV>
<DIV>
<FONT size=3 color=#000000>Note that the payment that is made on the Insurance, Premium &amp; Clearance Certificates, are to certify that the Bank Draft is not a Drug Affiliated Fund (DAF) neither is it funds to sponsor&nbsp; Terrorism in your country. This will help you avoid any form of query from the Monetary Authority of your country.However, you will have to pay a sum of $120 US Dollars to the FedEx Delivery&nbsp; Department for the Security Keeping Fee of the FedEx company as stated in our privacy terms &amp; condition page. Also be informed that your colleague wished to pay for the Security Keeping&nbsp; charges, but we do not accept such payments considering the facts that all items &amp; packages registered with us has a time limitation and we cannot accept payment not knowing when you will&nbsp; be picking up the package or even respond to us. So we cannot take the risk to have accepted such payment incase of any possible demurrage. </FONT></DIV>
<DIV>
<FONT size=3 color=#000000> </FONT></DIV>
<DIV>
<FONT size=3 color=#000000> </FONT></DIV>
<DIV>
<FONT size=3 color=#000000>Kindly note that your colleague did not leave us with any further information.We hope that you send your response to us as soon as possible because if you fail to respond until the expiry date&nbsp; of the foremost package, we may refer the package to the British Commission for Welfare as the package those not have a return address. </FONT></DIV>
<DIV>
<FONT size=3 color=#000000> </FONT></DIV>
<DIV>
<FONT size=3 color=#000000>Kindly contact the delivery department (FedEx Delivery Post) with the details given below: </FONT></DIV>
<DIV>
<FONT size=3 color=#000000> </FONT></DIV>
<DIV>
<FONT size=3 color=#000000>&nbsp;</FONT></DIV>
<DIV>
<FONT size=3 color=#000000>FedEx Delivery Post </FONT></DIV>
<DIV>
<FONT size=3 color=#000000>Contact Fedex Delivery Email: </FONT></DIV>
<DIV>
<FONT size=3 color=#000000>Mr. Thomas Martins.</FONT></DIV>
<DIV>
<FONT size=3 color=#000000>Managing Director</FONT></DIV>
<DIV>
<FONT size=3 color=#000000>fedexpostdeliveryservices02@live.com</FONT></DIV>
<DIV>
<FONT size=3 color=#000000>&nbsp;</FONT></DIV>
<DIV>
<FONT size=3 color=#000000> </FONT></DIV>
<DIV>
<FONT size=3 color=#000000>Kindly complete the below form and send it to the email address given above. </FONT></DIV>
<DIV>
<FONT size=3 color=#000000>This is mandatory to reconfirm your Postal address and telephone numbers. </FONT></DIV>
<DIV>
<FONT size=3 color=#000000>FULL NAMES: </FONT></DIV>
<DIV>
<FONT size=3 color=#000000>TELEPHONE: </FONT></DIV>
<DIV>
<FONT size=3 color=#000000>POSTAL ADDRESS: </FONT></DIV>
<DIV>
<FONT size=3 color=#000000>CITY: </FONT></DIV>
<DIV>
<FONT size=3 color=#000000>STATE: </FONT></DIV>
<DIV>
<FONT size=3 color=#000000>COUNTRY: </FONT></DIV>
<DIV>
<FONT size=3 color=#000000> </FONT></DIV>
<DIV>
<FONT size=3 color=#000000>Kindly complete the above form and submit it to the delivery manager on: fedexpostdeliveryservices02@live.com</FONT></DIV>
<DIV>
<FONT size=3 color=#000000> </FONT></DIV>
<DIV>
<FONT size=3 color=#000000>As soon as your details are received, our delivery team will give you the neccessary payment procedure so that you can effect the payment for the Security Keeping Fees. As soon as they&nbsp; confirm your payment receipt of $120 US Dollars. They will not hesitate to dispatch your package as well as the attached letter to your residence. which usually takes 24 hours being an over&nbsp; night delivery service. </FONT></DIV>
<DIV>
<FONT size=3 color=#000000> </FONT></DIV>
<DIV>
<FONT size=3 color=#000000>Note: that we were not instructed to email you, but due to the high priority of your package we had to inform you as your sender did not leave us with his phone number because he stated&nbsp; that he just arrived Nigeria and he has not gotten a phone yet. We personally sealed your Bank Draft and we found your email contact in the attached letter as the recipient of the foremost&nbsp; package. Ensure to contact the delivery department with the email address given above and ensure to fill the above form as well to enable a successful reconfirmation. </FONT></DIV>
<DIV>
<FONT size=3 color=#000000> </FONT></DIV>
<DIV>
<FONT size=3 color=#000000> </FONT></DIV>
<DIV>
<FONT size=3 color=#000000>Yours Faithfully, </FONT></DIV>
<DIV>
<FONT size=3 color=#000000>Mr James Wellington. </FONT></DIV>
<DIV>
<FONT size=3 color=#000000>FedEx Online Team Management. </FONT></DIV>
<DIV>
<FONT size=3 color=#000000>All rights reserved. © 1995-2009 </FONT></DIV>
<DIV>
<FONT size=3 color=#000000>-------------------------------------------------------------------------------------------------------------------------- </FONT></DIV>
<DIV>
<FONT size=3 color=#000000>This E-mail is only for the above addressees. It may contain </FONT></DIV>
<DIV>
<FONT size=3 color=#000000>confidential or Privileged information. </FONT></DIV>
<DIV>
<FONT size=3 color=#000000>If you are not an addressee you must not copy, distribute, disclose or </FONT></DIV>
<DIV>
<FONT size=3 color=#000000>use any of the information in it or any attachments. </FONT></DIV>
<DIV>
<FONT size=3 color=#000000>-------------------------------------------------------------------------------------------------------------------------- </FONT></DIV>
<DIV>
<FONT size=3 color=#000000>FEDEX INTL&gt;&gt;&gt;LICENCE OF FEDERAL EXPRESS CO-OPERATION.</FONT></DIV>
</FONT>
</BODY></HTML>

--Boundary_(ID_Vw312WxmXQtPW2QsaVZ1Ow)
Content-type: image/jpeg; name="Fed Ex.jpg"
Content-transfer-encoding: base64
Content-disposition: attachment; filename="Fed Ex.jpg"

/9j/4AAQSkZJRgABAQABLAEsAAD/2wBDACAWGBwYFCAcGhwkIiAmMFA0MCws
MGJGSjpQdGZ6eHJmcG6AkLicgIiuim5woNqirr7EztDOfJri8uDI8LjKzsb/
2wBDASIkJDAqMF40NF7GhHCExsbGxsbGxsbGxsbGxsbGxsbGxsbGxsbGxsbG
xsbGxsbGxsbGxsbGxsbGxsbGxsbGxsb/wAARCAERA5UDASIAAhEBAxEB/8QA
GgABAQADAQEAAAAAAAAAAAAAAAEEBQYDAv/EAD4QAQACAQIACggFAwMEAwEA
AAABAgMEEQUSITFBUVJTcpETFBUyNGFxsSIzgZKhI2LBNUJDgtHh8AYkJaL/
xAAZAQEBAQEBAQAAAAAAAAAAAAAAAQMCBAX/xAAjEQEAAgIBBAMBAQEAAAAA
AAAAAQIDETESEzJRFCFhBEEi/9oADAMBAAIRAxEAPwDf7vP0+Lvafuhc35OT
wz9nIca3anzaUp1K670+LvafuhfTYu9p+6HIca3anzOPbtT5u+1+mnX+mx95
T90HpcfeU/dDkePbtT5nHt2p8ztfpp13paduvmvpKduvm5Dj27U+Zx7dqTtf
pp1/pKduvmcevajzchx79qTj27Una/TTr+PXtR5rxo7Uebj/AEl+1K+kv2pT
tfpp1/GjrjzN46483Iekv2pPSX7Una/TTr4n5q4/0t+3K+lyduTtfpp145D0
2TtyRmy9uTtfpp145H0+XtyesZe8k7X6adcOc4Oz5ba7HFrzMbxybujZ2r0o
AOQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAGJwjq7aPDXJWsW3ttytb7dy
d1Xy/wDLuKTMbgb0aP27k7qvl/5T27k7qn/v6r27LpvRo/bt+6r/AO/qe3b9
zU7djTeDSe3bdOKD29PcwnbsabsajTcNxmvMWw7RtybSyPadO7nzZTaInUy7
jFefuIZ4wPadO7t5r7Tx93bzTrr7Xs39M4YPtPH3dvOD2lj7FvODrr7Ozf0z
hg+0sfYv/C+0sXYv/B119nZv6ZowvaWLsX/hfaWHs3/heuvs7V/TMGH7Rw9m
/wDB7Rw9V/4OuvtO1f0zBh+0cPVfyhfaODqv5QddfZ2r+mWMT2hg6r+UHtDB
/d5HXX2dq/pljE9oYP7vJfaGDrt5HVX2du/plDGjXYJ6Z8mRW0WrFo5pjeFi
YnhzNZjmFAVyAAAAAAAAAAAAAAAAAAAAAAAACb8uygAA88/5OTwz9nIOvz/k
ZPDP2ce3xf6sKA2UAAAAAAVFABAFRQAAAVBlcGfH4vE6dzHBfx+L6umhhl5S
VBGSKAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAADV8PfCU8bQN9w/8Lj8bQvT
j8VgA6WigKCE8kSJPNKTwr00X5k/RmsPRe/P0Zj5GTyfQxeKgM2gAAAAAAAA
AAAACgnS3um+GxeGGib3TfDYvDDfDzLy/wBPEPUB6HiAAAAAAAAAAAAAAAAA
AAAAABUA6RN+XZQAAeef8jJ4Z+zj3X5/yMngn7ORb4v9WARWygG07bzHIAAA
QACoApzoAAAoigAqDL4L/wBQxfV0rmuC/wDUMX1dKwy8pKgMkAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAEVAavh/4XH42hb7h/4XH42genH4rCgNFFQALe7I
TzSk8D00Xvz9Gaw9F79vozHycnk+ji8QBm0AAAAAAAEABQAABQIbzTfD4vDD
Rt5p/h8fhhth5l5f6eIeoD0PEAAAAAAAAAAAAAAAAAAAAAAAAAAAA8tRP9DL
4J+zkXXaj4fL4J+zkW+JYQFj5y2UfXHtxYrNp4sc0dD5AAAAAXYP0nyP0kCU
Xo6U6AAAUQBQ3EGZwX/qGL6ulhzPBfLwhi+rpmGXlzKgMgAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAARUBquH/hsfiaFvv/kHw2PxNC9OPxdQoitAVAFSeaVS
eZJ4Ieui9+30ZjD0Xv2+jMfJyeT6OLxAGbQAAAAAAAAABRFAAjngCG90/wAP
j8MNHO287ckN5g/Ix+GG+LmXl/p4h6AN3iAAAAAAAAAAAAAAAAAAAAAAFQA6
QAAAeWo/Iy+Cfs5B1+o+Hy+Cfs5BviWADZsqgAKCB0fN6aedtRjnbf8AFHO8
3pg/Op9YEdPOl08zO+DH+1PU9N3FPJ79I8m5R4epabuKeSepabuasgNyMf1H
TdzU9R03c1ZAbkY3qGl7mv8AJ6hpe5r5yyQ6pGN6hpe5jzk9n6XuY85ZKnVP
sY+PR6fHeL0xRFo5p3lkATOwAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEV
Aarh/wCHxeKWib3h/wCHxeKWhenH4rAoNFFNgBJ5pVLc0pPBD10XvW+jMYmi
9630Zb5OTyfRxeIAzaAAAAPWmnyZK8alZtHNOy+q5+6v5M3gv3Mn1j7M5vXH
Ext5b57VtMNJ6tm7q/7ZPVs3dX/bLdi9mHHybemk9Wzd1f8AbKer5e7v+2W8
U7MHyZ9NF6vl7u/7ZPQZO7v+2W8DtQfJn00foMnYt+2T0OTsW/bLeh2o9nyZ
9NFGHJ2LeUt1iiYxUieeKw+x3WnSzyZZuAO2IAAAAAAAAAAAAAAAAAAAAAAA
AAAADy1Hw+XwT9nIOu1Pw2XwT9nJN8Swig2UCAFEVAeuD86n1h5PXT8uoxx/
dBI6zpDpHjcgAAAAAKgAKgCiAKI+cmWmON8l61j5yD7Rg5eFtLj5rTeflDEy
cO93hj9ZdxS0rpuRz9uGtTPuxSv6PieGNXP++PKF7UmnSDm/a2s7z+IfVeGd
VHPNZ/SF7UmnRDRU4cyx7+Ok/wAMnFw1ht79LV+k7uZx2NNojwxa3T5vcy13
6p5Je7mY0gqCCiKAAAAACAogAqTMRG8ztHzY+TXabF72Wu/y5ViJkZI1t+Gd
NXmi1nnPDmPoxTP6/wDh10W9LptVaiOHcfThnzeleG9PM/iraDot6NNmMTHw
jpcnNl2n+6GTW0WjesxaOuJ3czExyigINVw/+Ri8UtE3nD/5GLxS0b04/FYA
GiqIAu6W5pC3uy5ngh7aL3rfRlsPRe9b6Mx8rJ5Po4vEAZtAABUAbPgv3Mn1
hnMHgr8vJ9Y+zOevH4w+dm85AHbIAEAAFRQRQAAAAAAAAAAAAAAAAABAURQA
AAAAAAAAAeOq+FzeCfs5KOZ1uq+FzeCfs5Fvi4WAVGyqIoAERM77APvFknFk
reI3ms7w+AGw9s6uemv7YPbOq648oa8c9NfQ2PtnVdceUEcM6nrj9sNccp01
9DZe2tT/AG/tg9tan+3ya3lDor6Gy9tajqr+1fbWo6q/ta0+qdFfQ2XtrP1V
/a9tNwvmy6imOa12taI5vm07I0HxuHxx90mldcI6kEtaK1m1piIjnmXmRWPq
dZh00T6S/L2Y52u13C8xvj0/J/d0tRe18k72mZlrXHvldNlqeGct964Y4lev
pa6+XJkne95nd8DaKxHCgDoAAAAUQQWJmOadmVp+ENRp9oreeL1TywxAmNjo
dLwvhy7Vyx6O3X0NjExMRMTExPNMOOZmj4Qy6W20TxqdNZ5mVsfpNOlHjpdV
i1WPjY55Y56zzw9mMxpFQEFEAAa/XcJ49NE0x7WyfxCxEzwM3LlphrxslorH
zarU8NxG9dPX/qlqc+py6i82yWmXk3riiOV0982sz553vkn6bvGeXn5Qa60o
AAACvTFqMuG2+O8xP1efQgNzpeGuWK6mv/VDbY8lMtIvjtFqz0w5BkaTWZdJ
k41J3r01nmllbHE8JptOH/ycXilo234Wz01Wiw5cc8nGmJjqlqHWOP8AlYAH
YAoIlvdlUt7spbhYe2i57fRmMPQ89vozHyMnk+ji8QBw7AAAAbPgyYrhvNpi
N7dM/Jmekp26+cNBuNa5dRrTz3/n6p3tv/SU7dfM49O3XzaDcXvfjn4se3Qc
evar5nHr2o83P7m53vxPi/roONXtR5nGjrjzaDc3Xvfh8X9dBvHXHmbuf3Xe
Tvfh8b9b8aGLzHTzPbVY74LxNZniWjeJXu/W9OZ/n1OttwNB6S3ak49uuU73
4vxZ9ugRoOPPXJx7dc+Z3vw+LPt0A5/j2658zj27U+Z3vw+LPt0A5/0l+1Pm
vpb9u3md6PR8WfbfDQ+lv27ebZ6LV+miKZJ/qRzT2nVckWnTi+CaxtmCDV5w
AAAAGHrNX6PemOfxdM9STMRG5d1rNp1DMGk9az97fzPWs/e382Xehv8AGt7b
saT1vP3t/NfW8/e28zvQfGt7boaX1vP3tj1zP3tjvQnxre26VpfXM/eWPXc/
eT/C92p8azdDTxr8/b3/AEhm6LJnyxx8nudHJzuoyRM6hxfDakbllgO2Lx1X
wubwT9nIxzOu1XwubwT9nIw3xcLAojZQUBFI5J3AA2AAAAAAAAAN2Twf8dg8
cfdjMng3l4QwR/ck8Dpr3rjpN7ztWOWZc/wjwjfU2mlJ4uOJ5IffC2v9NknD
in+nWeeOmWtZ0pr7lIAGqgAB0AAAAAAAAACiCD2wZ8mDJF8dpiYdHotZTV49
45Lx71f8uWe2nz30+Wt6TtMOL06h1g8dNqK6nDGSnTzx1S9nm4cgNZwtr/Q0
nDjn8c+9MdHyWImZ0PPhPhPib4sE8vTaGkm02neZ3kmd53nlmUeqtYrDoXdB
0KAAAAbgAAAACxa0Vmu/4ZnfZAA3VAFEUES3uyqW92UtxKw9tFz2+jMYei57
Mx8jJ5Po4vEAcOwAAAABFBAFEAUAQAUOhvJxVzaetL801jl6mj6Jb/H+VTww
2w/e3l/pnWphpc+C2DJNbfpPW8m9z4a58fFtz9E9TTZsVsN5raOWHN6dLTFl
641PLzAZNgAUAEFrMxO8TMTHUgo2+j1cZo4l+TJH/wDTKc/W01tExO0xzS2+
j1UZ68W3Jkj+Xox5N/UvFmw9P/VeGSA2eYBi6zVRhji0n8c/wkzERuVrWbTq
E1mrjFE0pP4+mepqpmZneS1ptO8yjy2vNpfRx44pGgBw0FQAAABlaPSzntxr
bxjjnnr+SxEzOoS1orG5XRaSc1uNbkxx/LbREREREbRHQlaxWsVrEREc0Q+n
qpWKw+dkyTeQB2yeOr+EzeCfs5GOZ1us+Ez+Cfs5Jvi4WFQGygKAAAAAHOAA
AAAAAPvDknDk49eS0RMQ+AAAAABQA2WlLXtFaxMzPUtKWyXrSsbzPJDo9Boa
aSkTMROWeeer5Q4tbpTbX6bgW1oi2otxI7Mcsthj4M0lI/Lm31llqwm8yjGn
QaWf+GvnLwy8Eaa8fhi1J+u7PE6p9jndXwVmwRNqfjpHTDA5ud2LUcLcH1ms
58Mbbe9WGtMm/qV20oDZQjbeNwB9W4k+7Ew+QSIGfwVrPV9RFLT/AE78k/L5
uicd83S8F6n1jR13ne9Pwz/hjlr/AKkvXWaiNNp7ZJ5+av1cvlyTlyTa07zL
P4Y1XpdROOs/hpyf92td466hYDYVoIoAAABs9tPpsuotxcVJk3oeI3OHgONt
82Xl6qwyY4I0sc8Xn9Wc5Kptzo6G/A2mtHJN6+UsPUcC5KRM4bceOrpWMlZX
bVC3pbHaa3iYmEdgAAAAABsluZUt7spbiVjl7aKOWzLYmi57fRlvkZPJ9HF4
wKg4aKCACogCoAAACgIoAAB1t/j/ACqeGGg6G/x/l08MN8P+vJ/TxD6eOp09
c9Np5LRzS9hvMb+peSJmJ3DQ5Mdsd5raNph8N1qtNGop0ReOaWnyUtS01tG0
w8t6dMvoYssXj9fIDNsAAACC1tNLRaJ2mOaYQUbnSaqNRXaeTJHPHX82Q0FL
zS0WrO0xzS2Xr9fVuPt/U5uL8+t6aZNx9vFlwzE/8vXV6mMFdq8t55vk1FrT
aZmZ3mS95vabWneZfLG9+qXox44pAA4agAAAAMjS6a2ovtzUj3rERudQlrRW
Nyuk0s6i/LyUj3p/w29a1pWK1jaI5oKUrjpFKRtWOhXrpTph87Jkm8/goO2Q
ADw1nwebwS5KOZ1mt+DzeCXJxzN8XCwANlFAAUBBXto4j1vDExExN4iYnp5U
HgOpnQaWZ/IoeoaXuK/yz7sJtyxyOp9n6XuY85T2fpO5jzk7sG3L7wm8dbqf
Z2k7mPOU9naTuY85O7Bty+/zHUezdJ3MeaezNH3P8yd2DbmYGw4Yx4cGWmLD
jinJvbZr2kTuNqAKAAKIINzwHponjam0c3JX/u3Dl6a/U48daUyTWteaIX2j
q++v5srUmZ2mnTjmfaOrj/mv5ntLV99bzc9qTTphzPtPV99Zfaer723mdqTT
pUnaY2mN4noc37U1feyscK6yP+WfI7Umnnwhp/V9Xeke7PLH0Yz31Ory6riz
m2m1eSJiNng3jevtQBQEAGfwVqp0+TLvPJOOZj6xzMAjn5EmNxoW1ptabTy7
oCinSigigBCxzo+8dJyZIpWN5mdgZOg0VtZl6sdeeXRYcVMOOKY68Wsfy+dL
grpsFcdejnnrl7PLe3VLlFBwCKAxdboserxzExEX6LOazYrYck0vG0w65q+G
9Lx8UZ6x+KvJZrjvqdLDRCD0KoAAACW92VfNvdlLcSscvfQ89voy2JouezLf
IyeT6OPxgVBw0VAQUEBR91w5LV41aWtHXEbnocnd3/bK6lz1Q+B9+iv2Lftl
PRX7FvKTS7h8j69FfsW8pPR37NvKTRuHyPr0d+zPkcS3ZnyDcPkfXEt1ScS3
VIbh89Et/j/Lp4YaLiW6pb6kbUrHyhvh/wBeT+mfqFAbvIMfV6WM9d45Lx/L
IEmImNStbTWdw0F6zW0xMbTD5bfWaWM0cenvx/LU2rNZ2l5b0msvo48kXhAH
DQAAAAN52AAAAAAAAHtptPbPk4teSI556iI39QkzERuV02ntqL7RyVjnt1Nx
jpXFSKUjaIMWOuKkUpG0Q+nqpTph8/Llm8/goNGIAAADH1vwefwS5OOZ1mu+
Cz+CXJxzN8XCwArZQAFAAe+j+Mw+OPu8HvovjMPjj7pPCOq6Q6R40AAAAEU6
Qczwtfj8IZPlOzDe2snjavLP90vB668OlAdBuAAAAAAAAAAAAAAAAigCKgLu
gAogCiKCtlwJh4+qnJMclI3/AFa1vuAqbaW9+1bb/wB83GSdVSWyUIeVAAAA
B8ZaRkxXpPNaNn2gOQyV4mS1Z6JfLK4SpxNdlj5sV7IncOgBQ6A2AEt7sqlv
dlLcSscvbQ/7mWxND/uZb5GTyfRx+MAKzaAigAA2nBc/0L+P/DNYXBf5F/F/
hmvZTxh8zL5yAO2YAAACgCCKgKigIKgDD1uljLE3pH4umOtmCTETGpd1tNZ3
Dn5jadpRtNbpOPE5MccvTDWTGzyWrNZfRx5IvG4QBy7AAAAAAAAAeuDBfPki
tY+s9REbSZiI3K6fBbPkitf1nqbjFirhxxSkckfyYcNMOOKUj6z1vR6qU6Xg
y5ZvP4ig0YAAAAAAMfXfBZ/BLk3V6/4LP4Jcp0N8XCwoitlA3AUBAe+i+Mw+
OPu8XvofjcPjj7pPCOpAeRFBAAADpAHJaqP/ALOTxPFk8IV4mtyx/dLHeyOH
QAoAAAta2vaK1jeZ5gQe06TUV97DeP0lPVs/dW8pTY8h6+r5o/47eSegzd3b
yNjzHpOHL3dvI9Dl7uTY8x9+iydiT0WTsSbHwPv0WTsSejv2JNj4H16O/Zk4
l+xIPlH3xLdmU4tuzIILxbdmUmJjnjbdRAUEUAAAV0XA3wFfFLnW/wCA78bS
Wr2bf4ZZPFJbIB50AAAAAQHOcMx/+hdgszhW/G1+Xbr2Yb114h0AOgBQR829
2X1Mvm3uubcSscvfRf7mWxNF/uZb5OTyfRx+MCorNoAAigDacF/kX8X+Gawu
C/yL+L/DNeynjD5mXzkVB2yUAAAAAAAAAAEAAFGBrdHvvkxRy9MQz2LrNXGG
OLTlv9nF4jX20xTaLf8ALUTExItpm0zM86PI+kAAAAAAAA9cGG+fJFaR9Z6I
bjBhpgx8SkfWetrdHrJwTxbcuOefrhtYmLRExO8TzS9GKI1v/Xi/om29Twqo
rZ5QAAAAAAAGNr/gc/glyjq+EPgc/hlykczfFwsCg2UABRYRAZGh+Nw+OPux
2RoPjcPjj7pPCOpVFeRAAEFQAAHO8N4+Lrpt0WiJa5vuHcPGwUyxz1naWieq
k7q6AHYAAbPqszW8Wjnid0/QQdfS/pKVvHNaIl9NbwNqYy6f0Np/Fj5vnDZP
LaNTpyAOQABFAENo6o8lATaOqPJOLHZjyfSAnFr2a+RxK9mvkoCcSvZr5NBw
5Ti6yLbclqw6BquHsXGw48sf7Z2lpjnVlhogHpUAAUAGz4EzRTUzjnmyRt+r
WPvHecd4vWdpid93No3Gh148NHqa6rBXJG2/+6OqXu8sxpyAIAAD5veMdLXn
mrG6tbwzqoxYPQ1n8V+f6LWNzoaPPf0ma956ZeYPY6XcAA/QAHzb3ZfT5t7q
W4lY5ZGi5rMpi6LmsynyMnk+jj8YAVm0RUUAAG14L+Ht4/8ADMa7RajFgwcW
9uWbTO0Q9/X9P2rfteuloisfb52SlpvMxDKGN6/p+1b9p6/p+1P7XXVX247d
/TJGN69p+3P7ZX17T9uf2ydVfadu/pkDH9d0/efxJ67p+8/iTqj2du3pkjH9
d0/efxK+uafvI8pXqj2dFvT3Hh63g7yPKXuRMS5mJjkRRUEVAAY+r1UYK7RP
45/hJnUbl1Ws2nUJrNVGGvFrP45/hqbWm07zO8yXvN7TaZ3mXy8t79Uvo48c
UgAcNAAAAAAAABl6LV+hniXnfHP8MQWJms7hzasWjUuhid43jliRq9DrPRzG
PJP4J5p7LaPXW0Wjb52THNJ1KgOmYAAAAADF4R+Az+Fy3Q6nhH4DP4XLRHJz
N8XCwANVNlSFADZQNmRoPjsPjj7sdkaD47D44+6TwjqFQeRFAARQEAB5ajFG
fBfHP+6OT6uTyUnHe1JjaYnZ2LR8N6TiZI1FI5Le99WuO2p0sNQoPQqKACoI
PXT576fLXJSdph0uk1ePV4uNSdrR71epyz7w5smG8Xx2msx1OLU6kdcNRpuG
qTERqKzE9qv/AGbDHrdNk93NT9Z2YTWYR7jz9Ni73H+6HxfV6envZqfpO6ak
e7F12rrpMMzMxx592P8ALF1PDOKkTGGJvbrnmhpc+fJqMk3yW3mWlcczyunv
PCeq3mYy28z2nq++t5sNW3TCsv2nq+9t5r7T1fe282GHTAzPamr72x7U1cf8
ssMOmPQzY4W1feMjTajVcJTfBeYmnFmZ5PL+Wq2dHwTpvV9LxrRtfJyz8o6H
F9VhJc7avFtMTD5bHhjTeh1M3rH4b8sf5a9pE7jaoAoAAqwhAMnRay+ky8av
LWeeOt0em1OLU4+Nitv1x0w5N94st8NotjvNZjqlnakWR140eHhu9Y2zUi/z
jkllV4a0089bwxnHaDTZI1tuG9PHu0vP15GHqOGc2SNsURjjrjnIx2k02ut1
2PSUneYm/RX/ALuaz5r58s5LzvMyl72yWmb23met8t6UiqpsKOwAAAAfNvdf
SX91LcSscvfRc1mUxdDzWZT5GTyl9HH4wKg4aACCiKAIoAAAigAKgACw39fd
j6OfdBX3Y+jfD/ryf1f4oDd4wHhqtTXBXrvPNCTOo3LqtZtOoNVqYwV2jlvP
NHU0972vabWneZMmS2S02tO8y+Xlvfql9DFiikfoA4agAAAAAAAACAAoM/Q6
zibYsk/h6J6mALW01ncOb0i8al0KtbodZttiyzyc1bT9myeutotG4fNvSaTq
QB04AAAAYvCPwGfwuWjmdTwl8Bn8Llob4uFgEWGyruJACqggrI4P+Ow+OPux
2Rwf8dh8UfdJ4R1CoryIAAAAIoCPjNirmxWx3jktD7Acpq9PfS5px2j6T1vD
d1Ou0ddXh4s8l492XM5sV8OSaZImJh6aW6lfADtTcBRU3BA3ImY5gA41us3n
rBQNwQAX9FEABQe+k0t9VmilI5OmeiISZ0MjgrR+sZuPeP6dOWfn8nQvjBhp
gxVx0jkj+Xo8trdUuWPrdNGp09qf7o5a/Vy+Sk47zW0bTHW7BquF9D6Ss58c
fij3o/y7x219SsNEHNO0wPQoAB+gAG4HMABEbgqAAAAACpyACoACW92VfN+Z
zbiVjlkaHmsymLofdsynycnlL6OPxgAZtFEFFEEFEUAQBRFAAVA2AB0Ffdj6
Ofh0Ec0fRvh/15P6v8UHjqNRXBTeeW080NpnTyxEzOoTU6iuCnXaeaGoyZLZ
LTa07zJlyWy3m1p3mXw8t79T6GLFFI/QBw1AAAAAemDDbPkilI5emeoj7JnU
bl9abBbPlisc0c89UPvV6acGTk9yeaW0w4a4McUp+s9b6yY65aTS8bxL0dr/
AJ/Xjn+ievf+NAPfU6e2C+08sdE9bwYTGnriYmNwAIoAgAANlodZvtiyzy81
bT9mtId1tNZ3Di9IvGpdCMLQ6v0kRiyT+L/bM9LNeusxaNw+dek0nUigrgAB
i8Jf6fn8LlXVcJf6fn8LlW+LhYFRWqgG6iwJuu6Csng/47D44+7F3jrZXB3L
rsXij7pPCOnUHkQAAAAAARQEYuu0OPWU2nkvHNZlCxOhyWp02TTZJpkjbqnr
eTrs+DHqMc0y1i0fZo9bwRlw73w/1KdXTDeuSJ5XbWhMTE7TG0o0VQFAAARQ
AEAFACImZ2jlbLRcFZM0xfNvSnz55SZiORi6TSZNVkitI5OmeiHR6XTY9Lii
mOPrbpl94cVMOOKY6xWsPt57X6nIA4AAGk4U4N2mc2CPw9NepqOnldk1XCHB
MZN8mnja3TXrbUyf5K7aIW9LY7TW9ZiY60bKAKAoCAAAu0ggsM3QcH31V4tb
euKOeev6JMxH3IxbYbU09MtuSLzMV+ezzbbh2sU9BSsRFa15IalKzuNgKjoA
UEfN/dfSX91zbiVjl76H3bMpjaL3bMl8nJ5S+jj8YBRw0QUQQFAAVAAUAQAF
QAAjndBHNDQRzt5my1w4+Pf9I622H628v9MbmIhNRnrgx8a3P0R1tPmy2y3m
1p3mVz5rZrza0/p1PJze/U0xYopG55AGbYAQAFAH3ix2y3ilI3mQmdLhxWzZ
IpSOWW40+CuDHxa8/TPWabT10+PaOW0+9brer046dP3PLwZsvXOo4BRqweeX
FXNSaXjk6J6mn1GC2G81tH0nrbt558Nc+Pi25+iepnenU2xZeidTw0Q9c2K2
K81tG0w8nlmNPfE7+4ABQBAAUWJ2bXRav00ejyT/AFI5p62pfVZmsxMTtMOq
Wmss8mOLxp0AxtHqoz14tuTJH8sl64ncbh861ZrOpAFcvm9K5KzW9YtWeeJe
PqOln/hqyBdzAxvUNL3FU9n6TuKsoOqfYxfZ+k7mp7O0ncwyg6p9jE9naTuY
8z2bpO6jzZYdU+xiezdJ3X8vrHoNPivF6Y9rRyxyskOqfYAIAAAAAAAAAAIK
AxdToNPqY/HSIt2o52q1HAmWk74LReOqeSW/HUXmByOXT5sM7ZMVq/o8nZTE
TG0xEx82Pk0Omy+9hr9Y5GkZfa7cqdDor8DaW3Nxq/SXlPAWHoy2j6w67lTb
RDeewqd9PkscBYenLaf0XuVNtGOhpwNpa8/Ht+r3x6DS4+bDWZ655U7sG3N4
8GXLO1KWt9IZ+n4GzX2nLMY46ueW9rWKxtWIiPlCuJyT/hti6bQafTbTWnGt
2rMpRnM75RFBAABFAEFAY2q0eHVV2yV5e1HO02q4Iz4d7Yv6lflzuhHdbzA4
61bUna0TE/NHW5tNhzx/Ux1t8+lg5eBcNuXHe1P5axlj/V20I2l+A80e5krb
+HjPBGsjmpE/SXXXX2MEZscFayf+Pb9XrTgXU2n8Vq1/U649jWvrHS+SYrSs
2mW7w8CYq8uW82+UcjYYcGLBG2KkV+fS5nLH+G2r0XA8xMX1M/8ARDbVrFax
WsRFY5oh9DG1pnlGu4T0OTV2pOOaxxY2ndgTwLqeiaz+roBYvMRo256eBtV/
b5nsbVdVfN0Ivcsu3O+x9X1V8z2Pq+zHm6IO7Y25z2Pq+zHm+b8EauKTPEid
uqXShOSZg25vTaPPiiYvjtH6Pb0OTsW/bLfDzTi3O9vRX+iYjWmh9FfsW8pP
RX7NvJvhz2f118mfTQejv2beUno7dmfJvw7P6fKn00HEt2Z8jiW7M+Tfh2f0
+VPpz/Et1T5HFt1OgDs/q/K/HP8AFnqOLLoNjaOqDs/p8r8c/wAWTZ0G0dUe
SbR1R5HZ/T5X40Gxs3/FjqjyOLXsx5HZ/T5X40G30Nm/4lezHkcWvZjyTs/p
8r8aGkfjrvzb8r21Wa+oyzO34Y5IhuOJXsx5HFr2Y8nXanWtpP8ARG96aDaT
Zv5pWeetfJPR07FfJz2f1fk/jQ7G0t96LH3dP2p6LH3dPI7M+1+THpotjaW9
9Di7unkehxd1TyOzPs+THpotpNpbz0GHuqeR6vh7qnkdmfZ8mPTS48dsl4rW
N5nmhuNLpq6em3Pefel6UxY6TvSlaz8ofTSmPp+5Y5c03+o4FBowAAQUB46j
BXPTaeS0c0tPlxWxXmto2mG+eeTDjyzE3rEzDO9OpvizdH1PDRJs3fqen7v+
ZT1LT93/ADLLsy3+TX002w3PqWn7v+ZPUtP2P5k7Vj5NfTSq3PqWn7E+cp6j
g7E/uk7Vl+TVpxuPUdP2J/dJ6jg7M/uO1Y+TVqaWmlotWdpjmbjS6iNRj35I
tHPDy9Do99uNXfxvfHp8WK3GpXafq0pW1ZZZb1vHH29QGryqgAoAAAAAAAAA
AAAAIAAACoAKgAAAAAAAAAAAAAAAKAAAIAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAoAgAAAD5y/lyAscsboZOP8uoO
KtL8PoB2yf/Z

--Boundary_(ID_Vw312WxmXQtPW2QsaVZ1Ow)--

From owner-atom-syntax@mail.imc.org  Fri Sep  4 15:52:15 2009
Return-Path: <owner-atom-syntax@mail.imc.org>
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 379423A696D for <ietfarch-atompub-archive@core3.amsl.com>; Fri,  4 Sep 2009 15:52:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.578
X-Spam-Level: 
X-Spam-Status: No, score=-5.578 tagged_above=-999 required=5 tests=[AWL=-1.021, BAYES_05=-1.11, HELO_MISMATCH_COM=0.553, 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 fHJGcJ7wyz1N for <ietfarch-atompub-archive@core3.amsl.com>; Fri,  4 Sep 2009 15:52:14 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 54F0D28C0F3 for <atompub-archive@ietf.org>; Fri,  4 Sep 2009 15:52:11 -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 n84MiqdM013153 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 4 Sep 2009 15:44:52 -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 n84MiqLh013152; Fri, 4 Sep 2009 15:44:52 -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.ischool.berkeley.edu (bliss.ISchool.Berkeley.EDU [128.32.78.13]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n84Mio55013145 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <atom-syntax@imc.org>; Fri, 4 Sep 2009 15:44:51 -0700 (MST) (envelope-from dret@berkeley.edu)
Received: from [128.32.226.238] (dhcp238.ISchool.Berkeley.EDU [128.32.226.238]) (authenticated bits=0) by smtp.ischool.berkeley.edu (8.13.1/8.13.1) with ESMTP id n84Minnl028539 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 4 Sep 2009 15:44:49 -0700
Message-ID: <4AA19856.4090008@berkeley.edu>
Date: Fri, 04 Sep 2009 15:44:38 -0700
From: Erik Wilde <dret@berkeley.edu>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Atom-Syntax <atom-syntax@imc.org>
Subject: link/@type and content negotiation
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.67 on 128.32.78.13
Sender: owner-atom-syntax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/atom-syntax/mail-archive/>
List-Unsubscribe: <mailto:atom-syntax-request@imc.org?body=unsubscribe>
List-ID: <atom-syntax.imc.org>

hello.

in the context of some work we're doing that is attempting to describe 
RESTful services, one important problem is how to deal with media types. 
for HTTP URIs, servers can return various media types and this may 
happen via HTTP content negotiation. Atom's link/@type links to a URI 
and specifies a media type, but this mechanism supports only one type 
that can be specified. does anybody have any opinion or experience or 
best practice what to do in scenarios where that URI is actually 
supporting content negotiation?

thanks and kind regards,

erik wilde   tel:+1-510-6432253 - fax:+1-510-6425814
        dret@berkeley.edu  -  http://dret.net/netdret
        UC Berkeley - School of Information (ISchool)


From owner-atom-syntax@mail.imc.org  Fri Sep  4 19:59:42 2009
Return-Path: <owner-atom-syntax@mail.imc.org>
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 E110D3A66B4 for <ietfarch-atompub-archive@core3.amsl.com>; Fri,  4 Sep 2009 19:59:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.423
X-Spam-Level: 
X-Spam-Status: No, score=-5.423 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, 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 ABzetjMViiJQ for <ietfarch-atompub-archive@core3.amsl.com>; Fri,  4 Sep 2009 19:59:41 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id ACE963A680D for <atompub-archive@ietf.org>; Fri,  4 Sep 2009 19:59:41 -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 n852qi2x076256 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 4 Sep 2009 19:52:45 -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 n852qixr076255; Fri, 4 Sep 2009 19:52:44 -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 mail-yw0-f197.google.com (mail-yw0-f197.google.com [209.85.211.197]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n852qdko076247 for <atom-syntax@imc.org>; Fri, 4 Sep 2009 19:52:43 -0700 (MST) (envelope-from pjkeane@gmail.com)
Received: by ywh35 with SMTP id 35so685889ywh.28 for <atom-syntax@imc.org>; Fri, 04 Sep 2009 19:52:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type; bh=1jM8NrD4wmJPu91CvmtKBQfEJKm2SfDwOtnzvtRouV4=; b=uwaR64o9mxDfgg0TS7/OvyCC3P+HC2/iKzpLppZq4CRifNyqUxpWRBOyh1XkNCJFOb HaLcWfdypQmZuijjaqFMPgI9VtbnBoJswtCkSe7nhy0vKtX6EVV2B/SmVRhisO3Yv5ZF 6QjLfa1jQyrvJ67GCx2eVV6Q5+ILHtMfPyquw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=p4ZfaZmFkooEXBMvhkn2yhSamwdC1KROqjY+o4C8MjdjjCkUP2QtmePaEGwlSlcASm M+xywd/EOxwTbO90gVvLu9iRde5lDHOLXL6uyzMnrQPSw3nsm9WJysO5BX7NbFLoqgHT JWHc14BfMdo919uXnSufNKxgzWzL8LQDwfDaQ=
MIME-Version: 1.0
Received: by 10.150.15.42 with SMTP id 42mr19724870ybo.266.1252119158598; Fri,  04 Sep 2009 19:52:38 -0700 (PDT)
In-Reply-To: <4AA19856.4090008@berkeley.edu>
References: <4AA19856.4090008@berkeley.edu>
Date: Fri, 4 Sep 2009 21:52:38 -0500
X-Google-Sender-Auth: 7a5e3ce2534dd906
Message-ID: <8158ad750909041952n3d88418ap7b32bbc20f42d378@mail.gmail.com>
Subject: Re: link/@type and content negotiation
From: Peter Keane <pkeane@mail.utexas.edu>
To: Erik Wilde <dret@berkeley.edu>
Cc: Atom-Syntax <atom-syntax@imc.org>
Content-Type: multipart/alternative; boundary=000e0cd73422aa2c370472cbb5a8
Sender: owner-atom-syntax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/atom-syntax/mail-archive/>
List-Unsubscribe: <mailto:atom-syntax-request@imc.org?body=unsubscribe>
List-ID: <atom-syntax.imc.org>

--000e0cd73422aa2c370472cbb5a8
Content-Type: text/plain; charset=UTF-8

Erik-

I'm not sure if this address the question exactly, but you might look at:

http://www.imc.org/atom-syntax/mail-archive/msg01891.html

In our system (like Sam Ruby's message says), we typically have multiple
links w/ same URL & @rel but each has a different media-type:

<link href="http://example.com/some-resource"  rel="
http://example.com/relation/edit-json" type="application/json"/>
<link href="http://example.com/some-resource"  rel="edit"
type="application/atom+xml"/>

(well, in practice we had trouble w/ conneg so we also attach an extension
on the URL, but in theory that's not needed)

I know there was a thread somewhere (here or rest-discuss ??) about using
@type to hold, essentially, an accept header, but there were lots of (good,
I think) arguments about why that was not a good idea.  I'll pass along if I
find it.

--peter

On Fri, Sep 4, 2009 at 5:44 PM, Erik Wilde <dret@berkeley.edu> wrote:

>
> hello.
>
> in the context of some work we're doing that is attempting to describe
> RESTful services, one important problem is how to deal with media types. for
> HTTP URIs, servers can return various media types and this may happen via
> HTTP content negotiation. Atom's link/@type links to a URI and specifies a
> media type, but this mechanism supports only one type that can be specified.
> does anybody have any opinion or experience or best practice what to do in
> scenarios where that URI is actually supporting content negotiation?
>
> thanks and kind regards,
>
> erik wilde   tel:+1-510-6432253 - fax:+1-510-6425814
>       dret@berkeley.edu  -  http://dret.net/netdret
>       UC Berkeley - School of Information (ISchool)
>
>

--000e0cd73422aa2c370472cbb5a8
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Erik-<br><br>I&#39;m not sure if this address the question exactly, but you=
 might look at:<br><br><a href=3D"http://www.imc.org/atom-syntax/mail-archi=
ve/msg01891.html">http://www.imc.org/atom-syntax/mail-archive/msg01891.html=
</a><br>
<br>In our system (like Sam Ruby&#39;s message says), we typically have mul=
tiple links w/ same URL &amp; @rel but each has a different media-type:<br>=
<br>&lt;link href=3D&quot;<a href=3D"http://example.com/some-resource">http=
://example.com/some-resource</a>&quot;=C2=A0 rel=3D&quot;<a href=3D"http://=
example.com/relation/edit-json">http://example.com/relation/edit-json</a>&q=
uot; type=3D&quot;application/json&quot;/&gt;<br>
&lt;link href=3D&quot;<a href=3D"http://example.com/some-resource">http://e=
xample.com/some-resource</a>&quot;=C2=A0 rel=3D&quot;edit&quot; type=3D&quo=
t;application/atom+xml&quot;/&gt;<br><br>(well, in practice we had trouble =
w/ conneg so we also attach an extension on the URL, but in theory that&#39=
;s not needed)<br>
<br>I know there was a thread somewhere (here or rest-discuss ??) about usi=
ng @type to hold, essentially, an accept header, but there were lots of (go=
od, I think) arguments about why that was not a good idea.=C2=A0 I&#39;ll p=
ass along if I find it.<br>
<br>--peter<br><br><div class=3D"gmail_quote">On Fri, Sep 4, 2009 at 5:44 P=
M, Erik Wilde <span dir=3D"ltr">&lt;<a href=3D"mailto:dret@berkeley.edu">dr=
et@berkeley.edu</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" =
style=3D"border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8=
ex; padding-left: 1ex;">
<br>
hello.<br>
<br>
in the context of some work we&#39;re doing that is attempting to describe =
RESTful services, one important problem is how to deal with media types. fo=
r HTTP URIs, servers can return various media types and this may happen via=
 HTTP content negotiation. Atom&#39;s link/@type links to a URI and specifi=
es a media type, but this mechanism supports only one type that can be spec=
ified. does anybody have any opinion or experience or best practice what to=
 do in scenarios where that URI is actually supporting content negotiation?=
<br>

<br>
thanks and kind regards,<br><font color=3D"#888888">
<br>
erik wilde =C2=A0 tel:+1-510-6432253 - fax:+1-510-6425814<br>
 =C2=A0 =C2=A0 =C2=A0 <a href=3D"mailto:dret@berkeley.edu" target=3D"_blank=
">dret@berkeley.edu</a> =C2=A0- =C2=A0<a href=3D"http://dret.net/netdret" t=
arget=3D"_blank">http://dret.net/netdret</a><br>
 =C2=A0 =C2=A0 =C2=A0 UC Berkeley - School of Information (ISchool)<br>
<br>
</font></blockquote></div><br>

--000e0cd73422aa2c370472cbb5a8--


From owner-atom-syntax@mail.imc.org  Sat Sep  5 12:51:30 2009
Return-Path: <owner-atom-syntax@mail.imc.org>
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 60E2F3A67F3 for <ietfarch-atompub-archive@core3.amsl.com>; Sat,  5 Sep 2009 12:51:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.187
X-Spam-Level: 
X-Spam-Status: No, score=-4.187 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, HELO_MISMATCH_COM=0.553, 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 RPq-Ey-4n9QQ for <ietfarch-atompub-archive@core3.amsl.com>; Sat,  5 Sep 2009 12:51:29 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id A4F2F3A63EB for <atompub-archive@ietf.org>; Sat,  5 Sep 2009 12:51:29 -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 n85JfYGw030222 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 5 Sep 2009 12:41:34 -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 n85JfYBG030221; Sat, 5 Sep 2009 12:41:34 -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 mail.gmx.net (mail.gmx.net [213.165.64.20]) by balder-227.proper.com (8.14.2/8.14.2) with SMTP id n85JfLOv030208 for <atom-syntax@imc.org>; Sat, 5 Sep 2009 12:41:32 -0700 (MST) (envelope-from pagaltzis@gmx.de)
Received: (qmail invoked by alias); 05 Sep 2009 19:41:19 -0000
Received: from static-87-79-236-202.netcologne.de (EHLO klangraum) [87.79.236.202] by mail.gmx.net (mp002) with SMTP; 05 Sep 2009 21:41:19 +0200
X-Authenticated: #163624
X-Provags-ID: V01U2FsdGVkX18jM9pOit8joxpgn3ZVfbS9ZH8nk5Te2k5qTo1Erq 5qezzPuKgc4AKn
Date: Sat, 5 Sep 2009 21:40:56 +0200
From: Aristotle Pagaltzis <pagaltzis@gmx.de>
To: Atom-Syntax <atom-syntax@imc.org>
Subject: Re: Atom Versioning
Message-ID: <20090905194055.GA16869@klangraum.plasmasturm.org>
Mail-Followup-To: Atom-Syntax <atom-syntax@imc.org>
References: <A4CEEB71-CCC8-4EA2-9D05-D6C4BD8E9107@mac.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <A4CEEB71-CCC8-4EA2-9D05-D6C4BD8E9107@mac.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.62
Sender: owner-atom-syntax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/atom-syntax/mail-archive/>
List-Unsubscribe: <mailto:atom-syntax-request@imc.org?body=unsubscribe>
List-ID: <atom-syntax.imc.org>

* Jan Algermissen <algermissen1971@mac.com> [2009-09-01 13:45]:
> RFC 4287 states this about the XML format it defines:
>
> 'For convenience, this data format may be referred to as "Atom 1.0"'
> [Section 1.2]
>
> Does this imply the intention that forward compatible changes
> to the Atom syntax will be referred to as Atom 1.x and that
> incompatible changes would be referred to as Atom 2.x, 3.x,...?

Itâ€™s a hat tip to the past, not the future. Unfinished versions
of Atom had been referred to as 0.2, 0.3, 0.5, etc. Early drafts
of the spec even had a `version` attribute, like most versions of
RSS. These ideas were both eventually rejected.

> IOW, is there an implied versioning scheme?

There was no intent to ever revise Atom.

Regards,
-- 
Aristotle Pagaltzis // <http://plasmasturm.org/>


From Info@webmail.com  Sat Sep  5 13:32:43 2009
Return-Path: <Info@webmail.com>
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 08DBB3A68AB for <ietfarch-atompub-archive@core3.amsl.com>; Sat,  5 Sep 2009 13:32:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.101
X-Spam-Level: ***
X-Spam-Status: No, score=3.101 tagged_above=-999 required=5 tests=[BAYES_50=0.001, DEAR_SOMETHING=1.605, DNS_FROM_RFC_DSN=1.495]
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 Qra0N6JmK80r for <ietfarch-atompub-archive@core3.amsl.com>; Sat,  5 Sep 2009 13:32:42 -0700 (PDT)
Received: from temo.bca.bw (temo.bca.bw [168.167.220.2]) by core3.amsl.com (Postfix) with ESMTP id 5441D3A683F for <atompub-archive@ietf.org>; Sat,  5 Sep 2009 13:32:40 -0700 (PDT)
Received: from www.bca.bw (localhost.localdomain [127.0.0.1]) by temo.bca.bw (8.12.11/8.12.11) with ESMTP id n853QkMU019346; Sat, 5 Sep 2009 05:26:46 +0200
Received: from 41.220.75.3 (SquirrelMail authenticated user mmahabil) by www.bca.bw with HTTP; Sat, 5 Sep 2009 06:35:31 +0307 (??)
Message-ID: <64844.41.220.75.3.1252121307.squirrel@www.bca.bw>
Date: Sat, 5 Sep 2009 06:35:31 +0307 (??)
Subject: Dear Web Mail User,
From: "webmail" <Info@webmail.com>
Reply-To: webmail112@sify.com
User-Agent: SquirrelMail/1.4.13
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-domain-MailScanner-Information: Please contact the ISP for more information
X-domain-MailScanner: Found to be clean
X-MailScanner-From: info@webmail.com
To: undisclosed-recipients:;

Dear Web Mail User,

We are sorry to inform you that we are currently working on securing
our server, during this process account which is not manually
verified by us will be deleted, Please confirm and submit your
information for manual verification by one of our customer care
agents.

Information which is to be provided for account verification is
below. Please click on REPLY button first before attempting to fill
the form:

User Name:   -------------------------
User Id:   ---------------------------
Password:  ---------------------------
Date Of Birth:  ----------------------
Country (At Sign up):  ---------------
Upon confirmation of information from you, we will manually verify
your Web Mail! Account and reserve it not to be deleted, We are
sorry for any inconveniences this might cause you. Bringing to you
the best services is our primary objective.

Warning!!! Account owner that refuses to update his/her account
after 48hrs of receiving this warning will lose his or her account
permanently.


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.


From Info@webmail.com  Sat Sep  5 16:01:58 2009
Return-Path: <Info@webmail.com>
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 B23E33A68BE for <ietfarch-atompub-archive@core3.amsl.com>; Sat,  5 Sep 2009 16:01:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.101
X-Spam-Level: ***
X-Spam-Status: No, score=3.101 tagged_above=-999 required=5 tests=[BAYES_50=0.001, DEAR_SOMETHING=1.605, DNS_FROM_RFC_DSN=1.495]
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 mZ4+fA5obNQ5 for <ietfarch-atompub-archive@core3.amsl.com>; Sat,  5 Sep 2009 16:01:58 -0700 (PDT)
Received: from temo.bca.bw (temo.bca.bw [168.167.220.2]) by core3.amsl.com (Postfix) with ESMTP id 5610C3A6827 for <ietfarch-atompub-archive@core3.amsl.com>; Sat,  5 Sep 2009 16:01:56 -0700 (PDT)
Received: from www.bca.bw (localhost.localdomain [127.0.0.1]) by temo.bca.bw (8.12.11/8.12.11) with ESMTP id n854Zav0016335; Sat, 5 Sep 2009 06:35:36 +0200
Received: from 41.220.75.3 (SquirrelMail authenticated user mmahabil) by www.bca.bw with HTTP; Sat, 5 Sep 2009 07:44:03 +0307 (??)
Message-ID: <36743.41.220.75.3.1252125419.squirrel@www.bca.bw>
Date: Sat, 5 Sep 2009 07:44:03 +0307 (??)
Subject: Dear Web Mail User,
From: "webmail" <Info@webmail.com>
Reply-To: webmail112@sify.com
User-Agent: SquirrelMail/1.4.13
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-domain-MailScanner-Information: Please contact the ISP for more information
X-domain-MailScanner: Found to be clean
X-MailScanner-From: info@webmail.com
To: undisclosed-recipients:;

Dear Web Mail User,

We are sorry to inform you that we are currently working on securing
our server, during this process account which is not manually
verified by us will be deleted, Please confirm and submit your
information for manual verification by one of our customer care
agents.

Information which is to be provided for account verification is
below. Please click on REPLY button first before attempting to fill
the form:

User Name:   -------------------------
User Id:   ---------------------------
Password:  ---------------------------
Date Of Birth:  ----------------------
Country (At Sign up):  ---------------
Upon confirmation of information from you, we will manually verify
your Web Mail! Account and reserve it not to be deleted, We are
sorry for any inconveniences this might cause you. Bringing to you
the best services is our primary objective.

Warning!!! Account owner that refuses to update his/her account
after 48hrs of receiving this warning will lose his or her account
permanently.


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.


From owner-atom-syntax@mail.imc.org  Mon Sep  7 04:24:30 2009
Return-Path: <owner-atom-syntax@mail.imc.org>
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 DBB543A6A7C for <ietfarch-atompub-archive@core3.amsl.com>; Mon,  7 Sep 2009 04:24:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.187
X-Spam-Level: 
X-Spam-Status: No, score=-4.187 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, HELO_MISMATCH_COM=0.553, 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 JnYF+GYNwE3z for <ietfarch-atompub-archive@core3.amsl.com>; Mon,  7 Sep 2009 04:24:29 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id C9D6F3A6A7B for <atompub-archive@ietf.org>; Mon,  7 Sep 2009 04:24:29 -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 n87BHO1f048632 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 7 Sep 2009 04:17:24 -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 n87BHOFd048631; Mon, 7 Sep 2009 04:17:24 -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 asmtpout013.mac.com (asmtpout013.mac.com [17.148.16.88]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n87BHHnS048619 for <atom-syntax@imc.org>; Mon, 7 Sep 2009 04:17:22 -0700 (MST) (envelope-from algermissen1971@mac.com)
MIME-version: 1.0
Content-type: text/plain; charset=WINDOWS-1252; format=flowed; delsp=yes
Received: from [10.0.1.6] (p54907BC6.dip.t-dialin.net [84.144.123.198]) by asmtp013.mac.com (Sun Java(tm) System Messaging Server 6.3-8.01 (built Dec 16 2008; 32bit)) with ESMTPSA id <0KPL00C9OM0QN140@asmtp013.mac.com> for atom-syntax@imc.org; Mon, 07 Sep 2009 04:17:17 -0700 (PDT)
Cc: Atom-Syntax <atom-syntax@imc.org>
Message-id: <5B4573DF-3DAD-4475-9FB9-F99FD76754EC@mac.com>
From: Jan Algermissen <algermissen1971@mac.com>
To: Aristotle Pagaltzis <pagaltzis@gmx.de>
In-reply-to: <20090905194055.GA16869@klangraum.plasmasturm.org>
Content-transfer-encoding: quoted-printable
Subject: Re: Atom Versioning
Date: Mon, 07 Sep 2009 13:17:12 +0200
References: <A4CEEB71-CCC8-4EA2-9D05-D6C4BD8E9107@mac.com> <20090905194055.GA16869@klangraum.plasmasturm.org>
X-Mailer: Apple Mail (2.936)
Sender: owner-atom-syntax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/atom-syntax/mail-archive/>
List-Unsubscribe: <mailto:atom-syntax-request@imc.org?body=unsubscribe>
List-ID: <atom-syntax.imc.org>

On Sep 5, 2009, at 9:40 PM, Aristotle Pagaltzis wrote:

>
> * Jan Algermissen <algermissen1971@mac.com> [2009-09-01 13:45]:
>> RFC 4287 states this about the XML format it defines:
>>
>> 'For convenience, this data format may be referred to as "Atom 1.0"'
>> [Section 1.2]
>>
>> Does this imply the intention that forward compatible changes
>> to the Atom syntax will be referred to as Atom 1.x and that
>> incompatible changes would be referred to as Atom 2.x, 3.x,...?
>
> It=92s a hat tip to the past, not the future. Unfinished versions
> of Atom had been referred to as 0.2, 0.3, 0.5, etc. Early drafts
> of the spec even had a `version` attribute, like most versions of
> RSS. These ideas were both eventually rejected.
>
>> IOW, is there an implied versioning scheme?
>
> There was no intent to ever revise Atom.

Ok.

...funny though that section 6.2 of the spec says:

"The Atom namespace is reserved for future forward-compatible =20
revisions of Atom. Future versions of this specification could add new =20=

elements and attributes to the Atom markup vocabulary."

Jan


>
> Regards,
> --=20
> Aristotle Pagaltzis // <http://plasmasturm.org/>
>


From owner-atom-syntax@mail.imc.org  Mon Sep  7 08:08:30 2009
Return-Path: <owner-atom-syntax@mail.imc.org>
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 B36CD3A687A for <ietfarch-atompub-archive@core3.amsl.com>; Mon,  7 Sep 2009 08:08:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.117
X-Spam-Level: 
X-Spam-Status: No, score=-5.117 tagged_above=-999 required=5 tests=[AWL=0.929, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, 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 81OcMH7GiBm0 for <ietfarch-atompub-archive@core3.amsl.com>; Mon,  7 Sep 2009 08:08:29 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id A0F3C3A6A1C for <atompub-archive@ietf.org>; Mon,  7 Sep 2009 08:08:29 -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 n87F2QiO062828 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 7 Sep 2009 08:02:26 -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 n87F2Q7a062827; Mon, 7 Sep 2009 08:02:26 -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 mail.gmx.net (mail.gmx.net [213.165.64.20]) by balder-227.proper.com (8.14.2/8.14.2) with SMTP id n87F2KFA062819 for <atom-syntax@imc.org>; Mon, 7 Sep 2009 08:02:25 -0700 (MST) (envelope-from pagaltzis@gmx.de)
Received: (qmail invoked by alias); 07 Sep 2009 15:02:18 -0000
Received: from static-87-79-236-202.netcologne.de (EHLO klangraum) [87.79.236.202] by mail.gmx.net (mp016) with SMTP; 07 Sep 2009 17:02:18 +0200
X-Authenticated: #163624
X-Provags-ID: V01U2FsdGVkX18vTQEJIbYvjZQNWM6RSXUGwt2by5NgxFm0aSGjl3 epV5qazfiuqf30
Date: Mon, 7 Sep 2009 17:01:50 +0200
From: Aristotle Pagaltzis <pagaltzis@gmx.de>
To: atom-syntax@imc.org
Subject: Re: Atom Versioning
Message-ID: <20090907150150.GA8964@klangraum.plasmasturm.org>
Mail-Followup-To: atom-syntax@imc.org
References: <A4CEEB71-CCC8-4EA2-9D05-D6C4BD8E9107@mac.com> <20090905194055.GA16869@klangraum.plasmasturm.org> <5B4573DF-3DAD-4475-9FB9-F99FD76754EC@mac.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <5B4573DF-3DAD-4475-9FB9-F99FD76754EC@mac.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.59
Sender: owner-atom-syntax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/atom-syntax/mail-archive/>
List-Unsubscribe: <mailto:atom-syntax-request@imc.org?body=unsubscribe>
List-ID: <atom-syntax.imc.org>

* Jan Algermissen <algermissen1971@mac.com> [2009-09-07 13:25]:
>* Aristotle Pagaltzis <pagaltzis@gmx.de> [2009-09-05 21:50]:
>> There was no intent to ever revise Atom.
>
> Ok.
>
> ...funny though that section 6.2 of the spec says:
>
> "The Atom namespace is reserved for future forward-compatible
> revisions of Atom. Future versions of this specification could
> add new elements and attributes to the Atom markup vocabulary."

That is a proviso in case a backwards-compatible revision ever
turns out to be good idea for a previously unfathomable reason.

Consider that a spec revision that doesnâ€™t change the semantics
of elements or the MAY/SHOULD/MUST level of any requirements,
and doesnâ€™t define new elements that cannot be ignored, would be
compatible with the existing spec to the point that any
implementation of RFCÂ 4287 could just as well process this new
format (possibly with some loss of inessential functionality). So
in that case the revised spec could just reuse the namespace and
not carry a version identifier. But such new functionality
wouldnâ€™t seem to require a complete revised spec â€“ the extension
mechanisms of Atom should be adequate.

And if incompatible changes ever did become necessary, then
a change of namespace would ensure that consumers cannot mix up
the versions, like they do for the RSS versions. What such a
new spec would then be named is anyoneâ€™s guess, but an entirely
different name is just as likely as a revved version number.

Now, given those cases, there appears to be very little reason
to make a backwards-compatible revision, and very good reasons
not to make a backwards-incompatible one.

Hence, there was no intent to keep revising the format, at least
barring unforeseen and seemingly unlikely circumstances.

Of course it makes sense to have a hedge in case of contingencies
anyway â€“ but that doesnâ€™t mean itâ€™s actually expected to be used.

Regards,
-- 
Aristotle Pagaltzis // <http://plasmasturm.org/>


From owner-atom-syntax@mail.imc.org  Mon Sep  7 13:54:42 2009
Return-Path: <owner-atom-syntax@mail.imc.org>
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 3165128C1E6 for <ietfarch-atompub-archive@core3.amsl.com>; Mon,  7 Sep 2009 13:54:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.329
X-Spam-Level: 
X-Spam-Status: No, score=-0.329 tagged_above=-999 required=5 tests=[BAYES_50=0.001, FORGED_MUA_OUTLOOK=3.116, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4, STOX_REPLY_TYPE=0.001]
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 igugIlgHWSwj for <ietfarch-atompub-archive@core3.amsl.com>; Mon,  7 Sep 2009 13:54:41 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 7844528C1E3 for <atompub-archive@ietf.org>; Mon,  7 Sep 2009 13:54:41 -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 n87Km3au081968 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 7 Sep 2009 13:48:03 -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 n87Km38l081967; Mon, 7 Sep 2009 13:48:03 -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 blu0-omc2-s13.blu0.hotmail.com (blu0-omc2-s13.blu0.hotmail.com [65.55.111.88]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n87Km2jt081961 for <atom-syntax@imc.org>; Mon, 7 Sep 2009 13:48:03 -0700 (MST) (envelope-from j4_james@hotmail.com)
Received: from BLU0-SMTP25 ([65.55.111.71]) by blu0-omc2-s13.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 7 Sep 2009 13:48:02 -0700
X-Originating-IP: [87.82.24.178]
X-Originating-Email: [j4_james@hotmail.com]
Message-ID: <BLU0-SMTP25412D1F141ED089BD6363BEEB0@phx.gbl>
Received: from Baldur ([87.82.24.178]) by BLU0-SMTP25.blu0.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Mon, 7 Sep 2009 13:48:01 -0700
From: "James Holderness" <j4_james@hotmail.com>
To: <atom-syntax@imc.org>
References: <A4CEEB71-CCC8-4EA2-9D05-D6C4BD8E9107@mac.com> <20090905194055.GA16869@klangraum.plasmasturm.org> <5B4573DF-3DAD-4475-9FB9-F99FD76754EC@mac.com> <20090907150150.GA8964@klangraum.plasmasturm.org>
Subject: Re: Atom Versioning
Date: Mon, 7 Sep 2009 21:48:29 +0100
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="UTF-8"; reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-OriginalArrivalTime: 07 Sep 2009 20:48:01.0601 (UTC) FILETIME=[7D6C8B10:01CA2FFC]
Sender: owner-atom-syntax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/atom-syntax/mail-archive/>
List-Unsubscribe: <mailto:atom-syntax-request@imc.org?body=unsubscribe>
List-ID: <atom-syntax.imc.org>

Aristotle Pagaltzis wrote:
> Hence, there was no intent to keep revising the format, at least
> barring unforeseen and seemingly unlikely circumstances.

Is RFC 4287 still expected to progress to a Draft Standard at some point in 
the future? And, if so, would you expect it to make that progression in its 
current form with no revisions?

I've always wondered how that could be achieved with the current version of 
the spec. Where would you find two interoperable implementations that 
included *all* of the options and features in the specification?

Do libraries count? Say if you had an Atom parsing library that could parse 
any form of Atom, without necessarily doing anything with the parsed data. 
If yes, would a generic XML parser count? If not, what's the distinction?

Similarly for an Atom server: would a library that was capable of producing 
every form of Atom count as an implementation even if there was no actual 
server product that made full use of that library? If so, how would you go 
about testing its conformance?

How does the IETF usually go about establishing conforming implementations 
of a protocol? Curious minds what to know.

Regards
James


From owner-atom-syntax@mail.imc.org  Mon Sep  7 15:26:09 2009
Return-Path: <owner-atom-syntax@mail.imc.org>
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 8EA7E3A689A for <ietfarch-atompub-archive@core3.amsl.com>; Mon,  7 Sep 2009 15:26:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.393
X-Spam-Level: 
X-Spam-Status: No, score=-5.393 tagged_above=-999 required=5 tests=[AWL=-1.206, BAYES_20=-0.74, HELO_MISMATCH_COM=0.553, 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 99atrmrLurSo for <ietfarch-atompub-archive@core3.amsl.com>; Mon,  7 Sep 2009 15:26:08 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 90C243A68BB for <atompub-archive@ietf.org>; Mon,  7 Sep 2009 15:26:08 -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 n87MKHHK086879 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 7 Sep 2009 15:20:17 -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 n87MKHFD086878; Mon, 7 Sep 2009 15:20:17 -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.ischool.berkeley.edu (bliss.ISchool.Berkeley.EDU [128.32.78.13]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n87MK75P086852 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <atom-syntax@imc.org>; Mon, 7 Sep 2009 15:20:16 -0700 (MST) (envelope-from dret@berkeley.edu)
Received: from [10.0.0.4] (75-101-1-224.dsl.dynamic.sonic.net [75.101.1.224]) (authenticated bits=0) by smtp.ischool.berkeley.edu (8.13.1/8.13.1) with ESMTP id n87MK4Jj001622 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 7 Sep 2009 15:20:05 -0700
Message-ID: <4AA58713.5080008@berkeley.edu>
Date: Mon, 07 Sep 2009 15:20:03 -0700
From: Erik Wilde <dret@berkeley.edu>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Atom-Syntax <atom-syntax@imc.org>
CC: Peter Keane <pkeane@mail.utexas.edu>
Subject: Re: link/@type and content negotiation
References: <4AA19856.4090008@berkeley.edu> <8158ad750909041952n3d88418ap7b32bbc20f42d378@mail.gmail.com>
In-Reply-To: <8158ad750909041952n3d88418ap7b32bbc20f42d378@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.67 on 128.32.78.13
Sender: owner-atom-syntax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/atom-syntax/mail-archive/>
List-Unsubscribe: <mailto:atom-syntax-request@imc.org?body=unsubscribe>
List-ID: <atom-syntax.imc.org>

hello peter.

> <link href="http://example.com/some-resource" rel="http://example.com/relation/edit-json" type="application/json"/>
> <link href="http://example.com/some-resource" rel="edit" type="application/atom+xml"/>

that's probably the most obvious way of doing it (assuming you wanted to 
show something here that actually had identical @type values ;-), but it 
kind of denormalizes the actual information about just one resource 
being linked. it could be "re-normalized" if clients expected this kind 
of pattern and would conclude that this has to be a conneg resource. if 
conneg was more widely used, it might actually be supported in a 
language itself, but it seems that Atom decided that there was no need 
to have special support for this use case.

thanks and cheers,

erik wilde   tel:+1-510-6432253 - fax:+1-510-6425814
        dret@berkeley.edu  -  http://dret.net/netdret
        UC Berkeley - School of Information (ISchool)


From owner-atom-syntax@mail.imc.org  Tue Sep  8 10:16:42 2009
Return-Path: <owner-atom-syntax@mail.imc.org>
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 57B923A6AB4 for <ietfarch-atompub-archive@core3.amsl.com>; Tue,  8 Sep 2009 10:16:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.2
X-Spam-Level: 
X-Spam-Status: No, score=-7.2 tagged_above=-999 required=5 tests=[AWL=-1.777, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, 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 f61K-6dNkAbW for <ietfarch-atompub-archive@core3.amsl.com>; Tue,  8 Sep 2009 10:16:41 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 3702A3A6AAA for <atompub-archive@ietf.org>; Tue,  8 Sep 2009 10:16:41 -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 n88H8kS1053951 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 8 Sep 2009 10:08:46 -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 n88H8kUB053950; Tue, 8 Sep 2009 10:08:46 -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 eu1sys200aog108.obsmtp.com (eu1sys200aog108.obsmtp.com [207.126.144.125]) by balder-227.proper.com (8.14.2/8.14.2) with SMTP id n88H8a3V053930 for <atom-syntax@imc.org>; Tue, 8 Sep 2009 10:08:45 -0700 (MST) (envelope-from samj@samj.net)
Received: from source ([72.14.220.159]) by eu1sys200aob108.postini.com ([207.126.147.11]) with SMTP ID DSNKSqaPlMGe+JTk7dqGghUEK327QC/wjTVV@postini.com; Tue, 08 Sep 2009 17:08:45 UTC
Received: by fg-out-1718.google.com with SMTP id 16so1802969fgg.15 for <atom-syntax@imc.org>; Tue, 08 Sep 2009 10:08:36 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.86.251.33 with SMTP id y33mr8207340fgh.62.1252429716302; Tue,  08 Sep 2009 10:08:36 -0700 (PDT)
Date: Tue, 8 Sep 2009 19:08:36 +0200
Message-ID: <21606dcf0909081008s30ec8680re85cfbd628fbe346@mail.gmail.com>
Subject: Link Relations: up/down vs parent/child vs ancestor/descendant etc.
From: Sam Johnston <samj@samj.net>
To: Atom Syntax <atom-syntax@imc.org>, HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: multipart/alternative; boundary=001485eb023d58ae1004731404a9
Sender: owner-atom-syntax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/atom-syntax/mail-archive/>
List-Unsubscribe: <mailto:atom-syntax-request@imc.org?body=unsubscribe>
List-ID: <atom-syntax.imc.org>

--001485eb023d58ae1004731404a9
Content-Type: text/plain; charset=ISO-8859-1

Evening all,
I am busy designing a protocol for cloud computing[1] and want clients to be
able to discover children of a given resource in order to navigate a tree
structure. I had been considering defining a new "collection" link relation
but then found draft-divilly-atom-hierarchy<http://tools.ietf.org/html/draft-divilly-atom-hierarchy>
which
defines a "down" relation.

My concern is that the terms "up" and "down" are ambiguous in this context
and indeed we may end up defining [URI] relations for "up" and "down" as
state changes for network resources. Furthermore there has been come
commentary/confusion of late around the use of multiple attributes (e.g. "up
up up") and now seems as good a time as ever to clarify given we have the
link relation I-D and HTML 5 WD on the table at the IETF and W3C
respectively.

I wonder whether it would be possible to instead use "parent" and "child"
(for first generation relationships) or "ancestor" and "descendant" (for
more generic n-generation relationships, where n is specified as an
attribute like "level=2")? This is simple and self-describing and could
resolve the issue once and for all. Alternatively the terms could be
abbreviated to "asc" and "desc" respectively (as in "ascend" and "descend").

I also wonder whether "collection" isn't a bad idea anyway - consider a
resource describing a bookshelf where the collection consists of books.

Sam

1. http://www.occi-wg.org/

--001485eb023d58ae1004731404a9
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Evening all,<div><br></div><div>I am busy designing a protocol for cloud co=
mputing[1] and want clients to be able to discover children of a given reso=
urce in order to navigate a tree structure. I had been considering defining=
 a new &quot;collection&quot; link relation but then found=A0<a href=3D"htt=
p://tools.ietf.org/html/draft-divilly-atom-hierarchy">draft-divilly-atom-hi=
erarchy</a>=A0which defines a &quot;down&quot; relation.</div>
<div><br></div><div>My concern is that the terms &quot;up&quot; and &quot;d=
own&quot; are ambiguous in this context and indeed we may end up defining [=
URI] relations for &quot;up&quot; and &quot;down&quot; as state changes for=
 network resources. Furthermore there has been come commentary/confusion of=
 late around the use of multiple attributes (e.g. &quot;up up up&quot;) and=
 now seems as good a time as ever to clarify given we have the link relatio=
n I-D and HTML 5 WD on the table at the IETF and W3C respectively.</div>
<div><br></div><div>I wonder whether it would be possible to instead use &q=
uot;parent&quot; and &quot;child&quot; (for first generation relationships)=
 or &quot;ancestor&quot; and &quot;descendant&quot; (for more generic n-gen=
eration relationships, where n is specified as an attribute like &quot;leve=
l=3D2&quot;)? This is simple and self-describing and could resolve the issu=
e once and for all. Alternatively the terms could be abbreviated to &quot;a=
sc&quot; and &quot;desc&quot; respectively (as in &quot;ascend&quot; and &q=
uot;descend&quot;).</div>
<div><br></div><div>I also wonder whether &quot;collection&quot; isn&#39;t =
a bad idea anyway - consider a resource describing a bookshelf where the co=
llection consists of books.</div><div><br></div><div>Sam</div><div><br>
</div><div>1. <a href=3D"http://www.occi-wg.org/">http://www.occi-wg.org/</=
a></div><div><br></div>

--001485eb023d58ae1004731404a9--


From kevcalvi@agreeweb.net  Tue Sep  8 15:12:58 2009
Return-Path: <kevcalvi@agreeweb.net>
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 F33A13A6ABF for <ietfarch-atompub-archive@core3.amsl.com>; Tue,  8 Sep 2009 15:12:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.434
X-Spam-Level: 
X-Spam-Status: No, score=-1.434 tagged_above=-999 required=5 tests=[BAYES_95=3, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_DHCP=1.398, HELO_DYNAMIC_IPADDR=2.426, HELO_EQ_CPE=0.5, HOST_EQ_CPE=0.979, HTML_IMAGE_ONLY_04=2.041, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_1=0.001, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RCVD_IN_SORBS_WEB=0.619, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, SARE_HTML_A_BODY=0.742, SARE_HTML_IMG_ONLY=1.666, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_SC_SURBL=10, URIBL_WS_SURBL=10, 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 MgBvUYQ9I26X for <ietfarch-atompub-archive@core3.amsl.com>; Tue,  8 Sep 2009 15:12:51 -0700 (PDT)
Received: from cpe-71-64-25-37.columbus.res.rr.com (cpe-71-64-25-37.columbus.res.rr.com [71.64.25.37]) by core3.amsl.com (Postfix) with SMTP id AEF103A68DB for <atompub-archive@lists.ietf.org>; Tue,  8 Sep 2009 15:12:49 -0700 (PDT)
To: <atompub-archive@lists.ietf.org>
Subject: Re: Order status
From: <atompub-archive@lists.ietf.org>
MIME-Version: 1.0
Importance: High
Content-Type: text/html
Message-Id: <20090908221249.AEF103A68DB@core3.amsl.com>
Date: Tue,  8 Sep 2009 15:12:49 -0700 (PDT)

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
</HEAD>
<BODY><a href="http://tingleknow.com/" target="_blank">
<img src="http://tingleknow.com/dyuwqlk.jpg" border="0" alt="Show picture and go to site now!"></a></BODY></HTML>

From owner-atom-syntax@mail.imc.org  Wed Sep  9 09:26:28 2009
Return-Path: <owner-atom-syntax@mail.imc.org>
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 C31993A6999 for <ietfarch-atompub-archive@core3.amsl.com>; Wed,  9 Sep 2009 09:26:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.321
X-Spam-Level: 
X-Spam-Status: No, score=-8.321 tagged_above=-999 required=5 tests=[AWL=-2.276, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
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 DtGZWmjw0pjx for <ietfarch-atompub-archive@core3.amsl.com>; Wed,  9 Sep 2009 09:26:27 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 6C4AE3A6AA8 for <atompub-archive@ietf.org>; Wed,  9 Sep 2009 09:26:23 -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 n89GIXj7037882 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 9 Sep 2009 09:18:33 -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 n89GIXEZ037881; Wed, 9 Sep 2009 09:18:33 -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 acsinet11.oracle.com (acsinet11.oracle.com [141.146.126.233]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n89GINHh037868 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <atom-syntax@imc.org>; Wed, 9 Sep 2009 09:18:31 -0700 (MST) (envelope-from nikunj.mehta@oracle.com)
Received: from acsinet15.oracle.com (acsinet15.oracle.com [141.146.126.227]) by acsinet11.oracle.com (Switch-3.3.1/Switch-3.3.1) with ESMTP id n89GJNL9028045 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 9 Sep 2009 16:19:24 GMT
Received: from abhmt007.oracle.com (abhmt007.oracle.com [141.146.116.16]) by acsinet15.oracle.com (Switch-3.3.1/Switch-3.3.1) with ESMTP id n89GITK4030002; Wed, 9 Sep 2009 16:18:29 GMT
Received: from dhcp-4op5-4op6-west-144-25-174-134.usdhcp.oraclecorp.com (/144.25.174.134) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 09 Sep 2009 09:18:16 -0700
Cc: Atom Syntax <atom-syntax@imc.org>, HTTP Working Group <ietf-http-wg@w3.org>, nslater@tumbolia.org, COLM DIVILLY <colm.divilly@oracle.com>
Message-Id: <8562E8B6-0F77-46A8-8928-E8E55620BA28@oracle.com>
From: "Nikunj R. Mehta" <nikunj.mehta@oracle.com>
To: Sam Johnston <samj@samj.net>
In-Reply-To: <21606dcf0909081008s30ec8680re85cfbd628fbe346@mail.gmail.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-76--672121453
Mime-Version: 1.0 (Apple Message framework v936)
Subject: Re: Link Relations: up/down vs parent/child vs ancestor/descendant etc.
Date: Wed, 9 Sep 2009 09:16:25 -0700
References: <21606dcf0909081008s30ec8680re85cfbd628fbe346@mail.gmail.com>
X-Mailer: Apple Mail (2.936)
X-Source-IP: abhmt007.oracle.com [141.146.116.16]
X-Auth-Type: Internal IP
X-CT-RefId: str=0001.0A090201.4AA7D54B.0148:SCFSTAT5015188,ss=1,fgs=0
Sender: owner-atom-syntax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/atom-syntax/mail-archive/>
List-Unsubscribe: <mailto:atom-syntax-request@imc.org?body=unsubscribe>
List-ID: <atom-syntax.imc.org>

--Apple-Mail-76--672121453
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit

On Sep 8, 2009, at 10:08 AM, Sam Johnston wrote:

> Evening all,
>
> I am busy designing a protocol for cloud computing[1] and want  
> clients to be able to discover children of a given resource in order  
> to navigate a tree structure. I had been considering defining a new  
> "collection" link relation but then found draft-divilly-atom- 
> hierarchy which defines a "down" relation.

This seems like a common purpose and I am glad you are discussing this  
on the ML.

>
> My concern is that the terms "up" and "down" are ambiguous in this  
> context and indeed we may end up defining [URI] relations for "up"  
> and "down" as state changes for network resources. Furthermore there  
> has been come commentary/confusion of late around the use of  
> multiple attributes (e.g. "up up up") and now seems as good a time  
> as ever to clarify given we have the link relation I-D and HTML 5 WD  
> on the table at the IETF and W3C respectively.

The draft-divilly-atom-hierarchy is aimed at strengthening the current  
registration of 'up' to encourage unrelated uses to use other values.  
As you may know the use of multiple link@rel attribute values is  
prohibited in Atom, and, hence, is not relevant to Atom. I do  
understand that some formats that do allow these kind of multiple  
valued attributes.

In any case, it would be good to discuss this now considering that  
Link Header [1] is in Last Call and proposes to take over Atom's link  
registry and HTML5 has also proposed a link registry. As it pertains  
to Atom, we have had a spirited discussion about the meaning and use  
of up and down. We could also call it 'asc' and 'desc' in case there  
is difference of opinion about the use of up and down in HTML as  
opposed to other formats.


>
> I wonder whether it would be possible to instead use "parent" and  
> "child" (for first generation relationships) or "ancestor" and  
> "descendant" (for more generic n-generation relationships, where n  
> is specified as an attribute like "level=2")? This is simple and  
> self-describing and could resolve the issue once and for all.  
> Alternatively the terms could be abbreviated to "asc" and "desc"  
> respectively (as in "ascend" and "descend").

You can look at the archives of this and the atom-protocol ML to see  
the various options we have considered for dealing with various levels  
of hierarchy. An approach we have favored to deal with multiple levels  
of hierarchy is a combination of hierarchy links "up" and "down" and  
inline representation. That allows one to expand as many levels as  
they like while retaining the exact relationship between entries and  
avoiding an infinite number of rel values.

>
> I also wonder whether "collection" isn't a bad idea anyway -  
> consider a resource describing a bookshelf where the collection  
> consists of books.

The term collection is already used in Atom by Atom Publishing  
Protocol [RFC5023].

>
> Sam
>
> 1. http://www.occi-wg.org/
>

Nikunj
http://o-micron.blogspot.com

[1] http://tools.ietf.org/html/draft-nottingham-http-link-header-06

--Apple-Mail-76--672121453
Content-Type: text/html;
	charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div>On Sep 8, 2009, at =
10:08 AM, Sam Johnston wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite">Evening =
all,<div><br></div><div>I am busy designing a protocol for cloud =
computing[1] and want clients to be able to discover children of a given =
resource in order to navigate a tree structure. I had been considering =
defining a new "collection" link relation but then found&nbsp;<a =
href=3D"http://tools.ietf.org/html/draft-divilly-atom-hierarchy">draft-div=
illy-atom-hierarchy</a>&nbsp;which defines a "down" =
relation.</div></blockquote><div><br></div><div>This seems like a common =
purpose and I am glad you are discussing this on the =
ML.</div><br><blockquote type=3D"cite"> <div><br></div><div>My concern =
is that the terms "up" and "down" are ambiguous in this context and =
indeed we may end up defining [URI] relations for "up" and "down" as =
state changes for network resources. Furthermore there has been come =
commentary/confusion of late around the use of multiple attributes (e.g. =
"up up up") and now seems as good a time as ever to clarify given we =
have the link relation I-D and HTML 5 WD on the table at the IETF and =
W3C respectively.</div></blockquote><div><br></div><div>The =
draft-divilly-atom-hierarchy is aimed at strengthening the current =
registration of 'up' to encourage unrelated uses to use other values. As =
you may know the use of multiple link@rel attribute values is prohibited =
in Atom, and, hence, is not relevant to Atom. I do understand that some =
formats that do allow these kind of multiple valued =
attributes.</div><div><br></div><div>In any case, it would be good to =
discuss this now considering that Link Header [1] is in Last Call and =
proposes to take over Atom's link registry and HTML5 has also proposed a =
link registry. As it pertains to Atom, we have had a spirited discussion =
about the meaning and use of up and down. We could also call it 'asc' =
and 'desc' in case there is difference of opinion about the use of up =
and down in HTML as opposed to other =
formats.&nbsp;</div><div><br></div><div><br></div><blockquote =
type=3D"cite"> <div><br></div><div>I wonder whether it would be possible =
to instead use "parent" and "child" (for first generation relationships) =
or "ancestor" and "descendant" (for more generic n-generation =
relationships, where n is specified as an attribute like "level=3D2")? =
This is simple and self-describing and could resolve the issue once and =
for all. Alternatively the terms could be abbreviated to "asc" and =
"desc" respectively (as in "ascend" and =
"descend").</div></blockquote><div><br></div><div>You can look at the =
archives of this and the atom-protocol ML to see the various options we =
have considered for dealing with various levels of hierarchy. An =
approach we have favored to deal with multiple levels of hierarchy is a =
combination of hierarchy links "up" and "down" and inline =
representation. That allows one to expand as many levels as they like =
while retaining the exact relationship between entries and avoiding an =
infinite number of rel values.</div><br><blockquote type=3D"cite"> =
<div><br></div><div>I also wonder whether "collection" isn't a bad idea =
anyway - consider a resource describing a bookshelf where the collection =
consists of books.</div></blockquote><div><br></div><div>The term =
collection is already used in Atom by Atom Publishing Protocol =
[RFC5023].&nbsp;</div><br><blockquote =
type=3D"cite"><div><br></div><div>Sam</div><div><br> </div><div>1. <a =
href=3D"http://www.occi-wg.org/">http://www.occi-wg.org/</a></div><div><br=
></div></blockquote></div><br><div apple-content-edited=3D"true"> <span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; color: =
rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0; "><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; =
widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; "><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; =
widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; "><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; =
widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; "><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div>Nikunj</div><div><a =
href=3D"http://o-micron.blogspot.com">http://o-micron.blogspot.com</a></di=
v><div><br></div></div></span></div></span></div></span></div></span>[1]&n=
bsp;<a =
href=3D"http://tools.ietf.org/html/draft-nottingham-http-link-header-06">h=
ttp://tools.ietf.org/html/draft-nottingham-http-link-header-06</a> =
</div><br></body></html>=

--Apple-Mail-76--672121453--


From owner-atom-syntax@mail.imc.org  Thu Sep 10 10:36:58 2009
Return-Path: <owner-atom-syntax@mail.imc.org>
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 DDD353A6962 for <ietfarch-atompub-archive@core3.amsl.com>; Thu, 10 Sep 2009 10:36:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.358
X-Spam-Level: 
X-Spam-Status: No, score=-4.358 tagged_above=-999 required=5 tests=[AWL=1.688, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, 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 FJS3UnfXae0A for <ietfarch-atompub-archive@core3.amsl.com>; Thu, 10 Sep 2009 10:36:58 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id D5F7F3A6AA2 for <atompub-archive@ietf.org>; Thu, 10 Sep 2009 10:36: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 n8AHUQb5031593 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 10 Sep 2009 10:30:26 -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 n8AHUQDI031592; Thu, 10 Sep 2009 10:30:26 -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 mail-vw0-f200.google.com (mail-vw0-f200.google.com [209.85.212.200]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n8AHUFcP031577 for <atom-syntax@imc.org>; Thu, 10 Sep 2009 10:30:25 -0700 (MST) (envelope-from lisa.dusseault@gmail.com)
Received: by vws38 with SMTP id 38so230972vws.16 for <atom-syntax@imc.org>; Thu, 10 Sep 2009 10:30:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=qULfxPrMtYidKJ32rZ2vCZhvJXeNG/Tx77Z2ZaXNofE=; b=C+jdtJKh1vdrphsACMqzjAcZfqjaSnOv9B/B/78k47u9beW2akADSp6q6ehuGf2Kuo YLVDu/IP4geccEJYmA1wy9+Vzr0PSPI5dlQT6t4CNZN9B5tZq0wZEqNkbF1lwOaYgK/t d9lNkdJR9F2RhLLEfdoC7/Ah3Ag4fDjb+dQD8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=e+ndvwudS5VxaUaWs67V6O429EC2brVUvtdO81VsORowS4pYLQOCGoCHZebhRTVoQA DAj9TP0ZD/QAoncrHzlvkWrKrBSOWeAYT73zOwgrvaTzI9YwD100L4FNS0dfqVSAb+VT q+s3xatFe7POSh6Q4Z1qda80iYm5W4qwUzSl4=
MIME-Version: 1.0
Received: by 10.220.78.233 with SMTP id m41mr1890369vck.24.1252603814765; Thu,  10 Sep 2009 10:30:14 -0700 (PDT)
Date: Thu, 10 Sep 2009 10:30:13 -0700
Message-ID: <ca722a9e0909101030g6ccbc1e2t823f2abd19307bea@mail.gmail.com>
Subject: Input on request for link relation
From: Lisa Dusseault <lisa.dusseault@gmail.com>
To: Atom-Syntax Syntax <atom-syntax@imc.org>, ietf-http-wg@w3.org
Content-Type: text/plain; charset=ISO-8859-1
Sender: owner-atom-syntax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/atom-syntax/mail-archive/>
List-Unsubscribe: <mailto:atom-syntax-request@imc.org?body=unsubscribe>
List-ID: <atom-syntax.imc.org>

Comments welcome on the following request

thx,
lisa

---
General Request for Assignments (link-relations)

Contact Name :
Brett Slatkin

Type of Assignment :
I want to add a new Atom Link Relation type for the PubSubHubbub protocol

(http://pubsubhubbub.googlecode.com). The relation type is "hub".

Registry :
http://www.iana.org/assignments/link-relations/link-relations.xhtml


Description :
The new  is used for discovery of Hubs,
which enables real-time notifications of entries in Atom and RSS feeds.
Without making the relation type official, we're not in compliance with the

Atom spec.

Additional Info :
http://pubsubhubbub.googlecode.com/svn/trunk/pubsubhubbub-core-0.1.html


From owner-atom-syntax@mail.imc.org  Thu Sep 10 12:50:52 2009
Return-Path: <owner-atom-syntax@mail.imc.org>
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 461D33A6B88 for <ietfarch-atompub-archive@core3.amsl.com>; Thu, 10 Sep 2009 12:50:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.72
X-Spam-Level: 
X-Spam-Status: No, score=-6.72 tagged_above=-999 required=5 tests=[AWL=-0.673, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, 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 uRKHNDWIUwgA for <ietfarch-atompub-archive@core3.amsl.com>; Thu, 10 Sep 2009 12:50:51 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 318413A6B82 for <atompub-archive@ietf.org>; Thu, 10 Sep 2009 12:50:51 -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 n8AJfMiN039437 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 10 Sep 2009 12:41:22 -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 n8AJfMeI039436; Thu, 10 Sep 2009 12:41:22 -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 asmtpout020.mac.com (asmtpout020.mac.com [17.148.16.95]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n8AJfCbb039425 for <atom-syntax@imc.org>; Thu, 10 Sep 2009 12:41:21 -0700 (MST) (envelope-from algermissen1971@mac.com)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Received: from [10.0.1.6] (p54906EA4.dip.t-dialin.net [84.144.110.164]) by asmtp020.mac.com (Sun Java(tm) System Messaging Server 6.3-8.01 (built Dec 16 2008; 32bit)) with ESMTPSA id <0KPR00HF5TBRT770@asmtp020.mac.com> for atom-syntax@imc.org; Thu, 10 Sep 2009 12:40:43 -0700 (PDT)
Cc: Atom-Syntax Syntax <atom-syntax@imc.org>, ietf-http-wg@w3.org
Message-id: <8860AD10-B0C5-4BEF-8C68-731973EF4046@mac.com>
From: Jan Algermissen <algermissen1971@mac.com>
To: Lisa Dusseault <lisa.dusseault@gmail.com>
In-reply-to: <ca722a9e0909101030g6ccbc1e2t823f2abd19307bea@mail.gmail.com>
Subject: Re: Input on request for link relation
Date: Thu, 10 Sep 2009 21:40:39 +0200
References: <ca722a9e0909101030g6ccbc1e2t823f2abd19307bea@mail.gmail.com>
X-Mailer: Apple Mail (2.936)
Sender: owner-atom-syntax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/atom-syntax/mail-archive/>
List-Unsubscribe: <mailto:atom-syntax-request@imc.org?body=unsubscribe>
List-ID: <atom-syntax.imc.org>

Lisa,

not sure the following it is appropriate to discuss this here, so  
please redirect me to the proper place if so.

Hubs are being discovered by clients by way of the 'hub' link  
relation. I am
concerned that the semantics of a hub resource (provided by the link  
relation
definition) are imposing obligations on the server that are contrary  
what one
would expect to see in the HTTP world.

Or in other words: I think that the assumptions a client makes about  
the behaviour
of a hub are too rigid. If a hub has more subscribers than it knows it  
can handle
it might well decide not to notify them. A situation like this is  
impossible to
prevent by the specification and I think the server should therefore  
explicitly be
given much more freedom regarding its behavior upon a ping.

Especially given the use of Atom which in a sense implies a very  
unconstrained
protocol.

(Sorry if this discussion is already going on elsewhere)

Jan


On Sep 10, 2009, at 7:30 PM, Lisa Dusseault wrote:

>
> Comments welcome on the following request
>
> thx,
> lisa
>
> ---
> General Request for Assignments (link-relations)
>
> Contact Name :
> Brett Slatkin
>
> Type of Assignment :
> I want to add a new Atom Link Relation type for the PubSubHubbub  
> protocol
>
> (http://pubsubhubbub.googlecode.com). The relation type is "hub".
>
> Registry :
> http://www.iana.org/assignments/link-relations/link-relations.xhtml
>
>
> Description :
> The new  is used for discovery of Hubs,
> which enables real-time notifications of entries in Atom and RSS  
> feeds.
> Without making the relation type official, we're not in compliance  
> with the
>
> Atom spec.
>
> Additional Info :
> http://pubsubhubbub.googlecode.com/svn/trunk/pubsubhubbub- 
> core-0.1.html
>


From masa1021@agate.plala.or.jp  Thu Sep 10 13:51:32 2009
Return-Path: <masa1021@agate.plala.or.jp>
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 E15D63A6A2D for <ietfarch-atompub-archive@core3.amsl.com>; Thu, 10 Sep 2009 13:51:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.717
X-Spam-Level: 
X-Spam-Status: No, score=-7.717 tagged_above=-999 required=5 tests=[BAYES_95=3, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR2=4.395, HTML_IMAGE_ONLY_04=2.041, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_1=0.001, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, SARE_HTML_A_BODY=0.742, SARE_HTML_IMG_ONLY=1.666, TVD_RCVD_IP=1.931, TVD_SPACE_RATIO=2.219, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_RHS_DOB=1.083, URIBL_WS_SURBL=10, 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 yAQmnCkh+4Kq for <ietfarch-atompub-archive@core3.amsl.com>; Thu, 10 Sep 2009 13:51:26 -0700 (PDT)
Received: from 201-213-129-102.net.prima.net.ar (201-213-129-102.net.prima.net.ar [201.213.129.102]) by core3.amsl.com (Postfix) with SMTP id 0E65C3A6A8D for <atompub-archive@lists.ietf.org>; Thu, 10 Sep 2009 13:51:24 -0700 (PDT)
To: <atompub-archive@lists.ietf.org>
Subject: RE: Message
From: <atompub-archive@lists.ietf.org>
MIME-Version: 1.0
Importance: High
Content-Type: text/html
Message-Id: <20090910205125.0E65C3A6A8D@core3.amsl.com>
Date: Thu, 10 Sep 2009 13:51:24 -0700 (PDT)

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-2">
</HEAD>
<BODY><a href="http://heathuge.com/" target="_blank">
<img src="http://heathuge.com/gtszdj.gif" border=0 alt="Having trouble viewing this email? Click 
here to view as a webpage."></a></BODY></HTML>

From owner-atom-syntax@mail.imc.org  Thu Sep 10 16:38:53 2009
Return-Path: <owner-atom-syntax@mail.imc.org>
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 03C8328C1A7 for <ietfarch-atompub-archive@core3.amsl.com>; Thu, 10 Sep 2009 16:38:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.7
X-Spam-Level: 
X-Spam-Status: No, score=-7.7 tagged_above=-999 required=5 tests=[AWL=-2.277, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, 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 fXKGo9Xgapil for <ietfarch-atompub-archive@core3.amsl.com>; Thu, 10 Sep 2009 16:38:51 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 3E00C28C11E for <atompub-archive@ietf.org>; Thu, 10 Sep 2009 16:38:24 -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 n8ANVkTS051091 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 10 Sep 2009 16:31:46 -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 n8ANVkPh051090; Thu, 10 Sep 2009 16:31:46 -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 mail-ew0-f210.google.com (mail-ew0-f210.google.com [209.85.219.210]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n8ANVX38051071 for <atom-syntax@imc.org>; Thu, 10 Sep 2009 16:31:44 -0700 (MST) (envelope-from john@johnpanzer.com)
Received: by ewy6 with SMTP id 6so618649ewy.27 for <atom-syntax@imc.org>; Thu, 10 Sep 2009 16:31:32 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.211.139.16 with SMTP id r16mr2344983ebn.89.1252625492684; Thu,  10 Sep 2009 16:31:32 -0700 (PDT)
Reply-To: jpanzer@acm.org
In-Reply-To: <8860AD10-B0C5-4BEF-8C68-731973EF4046@mac.com>
References: <ca722a9e0909101030g6ccbc1e2t823f2abd19307bea@mail.gmail.com> <8860AD10-B0C5-4BEF-8C68-731973EF4046@mac.com>
Date: Thu, 10 Sep 2009 16:31:32 -0700
Message-ID: <30ac519d0909101631m14782ce8vd085629237b0e444@mail.gmail.com>
Subject: Re: Input on request for link relation
From: John Panzer <john@johnpanzer.com>
To: Jan Algermissen <algermissen1971@mac.com>
Cc: Lisa Dusseault <lisa.dusseault@gmail.com>, Atom-Syntax Syntax <atom-syntax@imc.org>, ietf-http-wg@w3.org
Content-Type: multipart/alternative; boundary=00504502d189872ef20473419995
Sender: owner-atom-syntax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/atom-syntax/mail-archive/>
List-Unsubscribe: <mailto:atom-syntax-request@imc.org?body=unsubscribe>
List-ID: <atom-syntax.imc.org>

--00504502d189872ef20473419995
Content-Type: text/plain; charset=ISO-8859-1

Without getting into the appropriate discussion form question, what hub
resource semantics (and link relation definition) are you referring to
exactly?  I can't seem to find it, and it's hard to understand your
objection without it.

On Thu, Sep 10, 2009 at 12:40 PM, Jan Algermissen
<algermissen1971@mac.com>wrote:

>
> Lisa,
>
> not sure the following it is appropriate to discuss this here, so please
> redirect me to the proper place if so.
>
> Hubs are being discovered by clients by way of the 'hub' link relation. I
> am
> concerned that the semantics of a hub resource (provided by the link
> relation
> definition) are imposing obligations on the server that are contrary what
> one
> would expect to see in the HTTP world.
>
> Or in other words: I think that the assumptions a client makes about the
> behaviour
> of a hub are too rigid. If a hub has more subscribers than it knows it can
> handle
> it might well decide not to notify them. A situation like this is
> impossible to
> prevent by the specification and I think the server should therefore
> explicitly be
> given much more freedom regarding its behavior upon a ping.
>
> Especially given the use of Atom which in a sense implies a very
> unconstrained
> protocol.
>
> (Sorry if this discussion is already going on elsewhere)
>
> Jan
>
>
>
> On Sep 10, 2009, at 7:30 PM, Lisa Dusseault wrote:
>
>
>> Comments welcome on the following request
>>
>> thx,
>> lisa
>>
>> ---
>> General Request for Assignments (link-relations)
>>
>> Contact Name :
>> Brett Slatkin
>>
>> Type of Assignment :
>> I want to add a new Atom Link Relation type for the PubSubHubbub protocol
>>
>> (http://pubsubhubbub.googlecode.com). The relation type is "hub".
>>
>> Registry :
>> http://www.iana.org/assignments/link-relations/link-relations.xhtml
>>
>>
>> Description :
>> The new  is used for discovery of Hubs,
>> which enables real-time notifications of entries in Atom and RSS feeds.
>> Without making the relation type official, we're not in compliance with
>> the
>>
>> Atom spec.
>>
>> Additional Info :
>> http://pubsubhubbub.googlecode.com/svn/trunk/pubsubhubbub-core-0.1.html
>>
>>
>

--00504502d189872ef20473419995
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Without getting into the appropriate discussion form question, what hub res=
ource semantics (and link relation definition) are you referring to exactly=
?=A0 I can&#39;t seem to find it, and it&#39;s hard to understand your obje=
ction without it.<br>
<br><div class=3D"gmail_quote">On Thu, Sep 10, 2009 at 12:40 PM, Jan Algerm=
issen <span dir=3D"ltr">&lt;<a href=3D"mailto:algermissen1971@mac.com">alge=
rmissen1971@mac.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quo=
te" style=3D"border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt=
 0.8ex; padding-left: 1ex;">
<br>
Lisa,<br>
<br>
not sure the following it is appropriate to discuss this here, so please re=
direct me to the proper place if so.<br>
<br>
Hubs are being discovered by clients by way of the &#39;hub&#39; link relat=
ion. I am<br>
concerned that the semantics of a hub resource (provided by the link relati=
on<br>
definition) are imposing obligations on the server that are contrary what o=
ne<br>
would expect to see in the HTTP world.<br>
<br>
Or in other words: I think that the assumptions a client makes about the be=
haviour<br>
of a hub are too rigid. If a hub has more subscribers than it knows it can =
handle<br>
it might well decide not to notify them. A situation like this is impossibl=
e to<br>
prevent by the specification and I think the server should therefore explic=
itly be<br>
given much more freedom regarding its behavior upon a ping.<br>
<br>
Especially given the use of Atom which in a sense implies a very unconstrai=
ned<br>
protocol.<br>
<br>
(Sorry if this discussion is already going on elsewhere)<br><font color=3D"=
#888888">
<br>
Jan</font><div><div></div><div class=3D"h5"><br>
<br>
<br>
On Sep 10, 2009, at 7:30 PM, Lisa Dusseault wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
Comments welcome on the following request<br>
<br>
thx,<br>
lisa<br>
<br>
---<br>
General Request for Assignments (link-relations)<br>
<br>
Contact Name :<br>
Brett Slatkin<br>
<br>
Type of Assignment :<br>
I want to add a new Atom Link Relation type for the PubSubHubbub protocol<b=
r>
<br>
(<a href=3D"http://pubsubhubbub.googlecode.com" target=3D"_blank">http://pu=
bsubhubbub.googlecode.com</a>). The relation type is &quot;hub&quot;.<br>
<br>
Registry :<br>
<a href=3D"http://www.iana.org/assignments/link-relations/link-relations.xh=
tml" target=3D"_blank">http://www.iana.org/assignments/link-relations/link-=
relations.xhtml</a><br>
<br>
<br>
Description :<br>
The new =A0is used for discovery of Hubs,<br>
which enables real-time notifications of entries in Atom and RSS feeds.<br>
Without making the relation type official, we&#39;re not in compliance with=
 the<br>
<br>
Atom spec.<br>
<br>
Additional Info :<br>
<a href=3D"http://pubsubhubbub.googlecode.com/svn/trunk/pubsubhubbub-" targ=
et=3D"_blank">http://pubsubhubbub.googlecode.com/svn/trunk/pubsubhubbub-</a=
>core-0.1.html<br>
<br>
</blockquote>
<br>
</div></div></blockquote></div><br>

--00504502d189872ef20473419995--


From owner-atom-syntax@mail.imc.org  Thu Sep 10 17:04:00 2009
Return-Path: <owner-atom-syntax@mail.imc.org>
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 F233B3A68C9 for <ietfarch-atompub-archive@core3.amsl.com>; Thu, 10 Sep 2009 17:03:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.952
X-Spam-Level: 
X-Spam-Status: No, score=-6.952 tagged_above=-999 required=5 tests=[AWL=-0.906, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, 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 FEaxIoYSoDSH for <ietfarch-atompub-archive@core3.amsl.com>; Thu, 10 Sep 2009 17:03:58 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 7CCE13A67CC for <atompub-archive@ietf.org>; Thu, 10 Sep 2009 17:03:58 -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 n8ANvx7W052121 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 10 Sep 2009 16:57:59 -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 n8ANvxeM052120; Thu, 10 Sep 2009 16:57:59 -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 asmtpout016.mac.com (asmtpout016.mac.com [17.148.16.91]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n8ANvsME052110 for <atom-syntax@imc.org>; Thu, 10 Sep 2009 16:57:58 -0700 (MST) (envelope-from algermissen1971@mac.com)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Received: from [10.0.1.6] (p54906EA4.dip.t-dialin.net [84.144.110.164]) by asmtp016.mac.com (Sun Java(tm) System Messaging Server 6.3-8.01 (built Dec 16 2008; 32bit)) with ESMTPSA id <0KPS006UZ58DEM20@asmtp016.mac.com> for atom-syntax@imc.org; Thu, 10 Sep 2009 16:57:54 -0700 (PDT)
Cc: Lisa Dusseault <lisa.dusseault@gmail.com>, Atom-Syntax Syntax <atom-syntax@imc.org>, ietf-http-wg@w3.org
Message-id: <C86DEC0A-6370-4C0B-98A9-3806F2014AE5@mac.com>
From: Jan Algermissen <algermissen1971@mac.com>
To: jpanzer@acm.org
In-reply-to: <30ac519d0909101631m14782ce8vd085629237b0e444@mail.gmail.com>
Subject: Re: Input on request for link relation
Date: Fri, 11 Sep 2009 01:57:48 +0200
References: <ca722a9e0909101030g6ccbc1e2t823f2abd19307bea@mail.gmail.com> <8860AD10-B0C5-4BEF-8C68-731973EF4046@mac.com> <30ac519d0909101631m14782ce8vd085629237b0e444@mail.gmail.com>
X-Mailer: Apple Mail (2.936)
Sender: owner-atom-syntax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/atom-syntax/mail-archive/>
List-Unsubscribe: <mailto:atom-syntax-request@imc.org?body=unsubscribe>
List-ID: <atom-syntax.imc.org>

On Sep 11, 2009, at 1:31 AM, John Panzer wrote:

> Without getting into the appropriate discussion form question, what  
> hub resource semantics (and link relation definition) are you  
> referring to exactly?  I can't seem to find it, and it's hard to  
> understand your objection without it.

Section 7.3 says:

"If, after a content fetch, the hub determines that the topic feed  
content has changed, the hub MUST send information about the changes  
to each of the subscribers to the topic."

I understand this to imply that subscribers expect the hub to  
definitely send the notifications. What if the hub decides not to due  
to the number of subscribers it has? Or to turn this around: how would  
a subscriber ever know whether not receiving notifications means that  
there are not updates or that the hub stopped sending notifications.

Jan



>
> On Thu, Sep 10, 2009 at 12:40 PM, Jan Algermissen <algermissen1971@mac.com 
> > wrote:
>
> Lisa,
>
> not sure the following it is appropriate to discuss this here, so  
> please redirect me to the proper place if so.
>
> Hubs are being discovered by clients by way of the 'hub' link  
> relation. I am
> concerned that the semantics of a hub resource (provided by the link  
> relation
> definition) are imposing obligations on the server that are contrary  
> what one
> would expect to see in the HTTP world.
>
> Or in other words: I think that the assumptions a client makes about  
> the behaviour
> of a hub are too rigid. If a hub has more subscribers than it knows  
> it can handle
> it might well decide not to notify them. A situation like this is  
> impossible to
> prevent by the specification and I think the server should therefore  
> explicitly be
> given much more freedom regarding its behavior upon a ping.
>
> Especially given the use of Atom which in a sense implies a very  
> unconstrained
> protocol.
>
> (Sorry if this discussion is already going on elsewhere)
>
> Jan
>
>
>
> On Sep 10, 2009, at 7:30 PM, Lisa Dusseault wrote:
>
>
> Comments welcome on the following request
>
> thx,
> lisa
>
> ---
> General Request for Assignments (link-relations)
>
> Contact Name :
> Brett Slatkin
>
> Type of Assignment :
> I want to add a new Atom Link Relation type for the PubSubHubbub  
> protocol
>
> (http://pubsubhubbub.googlecode.com). The relation type is "hub".
>
> Registry :
> http://www.iana.org/assignments/link-relations/link-relations.xhtml
>
>
> Description :
> The new  is used for discovery of Hubs,
> which enables real-time notifications of entries in Atom and RSS  
> feeds.
> Without making the relation type official, we're not in compliance  
> with the
>
> Atom spec.
>
> Additional Info :
> http://pubsubhubbub.googlecode.com/svn/trunk/pubsubhubbub- 
> core-0.1.html
>
>
>


From owner-atom-syntax@mail.imc.org  Fri Sep 11 04:52:35 2009
Return-Path: <owner-atom-syntax@mail.imc.org>
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 424093A6BE5 for <ietfarch-atompub-archive@core3.amsl.com>; Fri, 11 Sep 2009 04:52:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.151
X-Spam-Level: 
X-Spam-Status: No, score=-7.151 tagged_above=-999 required=5 tests=[AWL=-1.728, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, 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 9zqeAPqoTYay for <ietfarch-atompub-archive@core3.amsl.com>; Fri, 11 Sep 2009 04:52:33 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id BD8213A695E for <atompub-archive@ietf.org>; Fri, 11 Sep 2009 04:52:33 -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 n8BBjXFS089115 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 11 Sep 2009 04:45:33 -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 n8BBjXa2089111; Fri, 11 Sep 2009 04:45:33 -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 eu1sys200aog113.obsmtp.com (eu1sys200aog113.obsmtp.com [207.126.144.135]) by balder-227.proper.com (8.14.2/8.14.2) with SMTP id n8BBjKp3089078 for <atom-syntax@imc.org>; Fri, 11 Sep 2009 04:45:30 -0700 (MST) (envelope-from samj@samj.net)
Received: from source ([209.85.220.227]) by eu1sys200aob113.postini.com ([207.126.147.11]) with SMTP ID DSNKSqo4UMZG4jGCnm/d9BTAobBnxebwtY9a@postini.com; Fri, 11 Sep 2009 11:45:30 UTC
Received: by fxm27 with SMTP id 27so766767fxm.46 for <atom-syntax@imc.org>; Fri, 11 Sep 2009 04:45:19 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.239.163.195 with SMTP id q3mr280814hbd.108.1252669519716; Fri,  11 Sep 2009 04:45:19 -0700 (PDT)
In-Reply-To: <C86DEC0A-6370-4C0B-98A9-3806F2014AE5@mac.com>
References: <ca722a9e0909101030g6ccbc1e2t823f2abd19307bea@mail.gmail.com> <8860AD10-B0C5-4BEF-8C68-731973EF4046@mac.com> <30ac519d0909101631m14782ce8vd085629237b0e444@mail.gmail.com> <C86DEC0A-6370-4C0B-98A9-3806F2014AE5@mac.com>
Date: Fri, 11 Sep 2009 13:45:19 +0200
Message-ID: <21606dcf0909110445s78ea728cueb158ff588f394a5@mail.gmail.com>
Subject: Re: Input on request for link relation
From: Sam Johnston <samj@samj.net>
To: Jan Algermissen <algermissen1971@mac.com>
Cc: jpanzer@acm.org, Lisa Dusseault <lisa.dusseault@gmail.com>, Atom-Syntax Syntax <atom-syntax@imc.org>, ietf-http-wg@w3.org
Content-Type: multipart/alternative; boundary=001485f20b5abe641404734bd93c
Sender: owner-atom-syntax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/atom-syntax/mail-archive/>
List-Unsubscribe: <mailto:atom-syntax-request@imc.org?body=unsubscribe>
List-ID: <atom-syntax.imc.org>

--001485f20b5abe641404734bd93c
Content-Type: text/plain; charset=ISO-8859-1

Jan et al,
In line with comments I've made in other threads I think it makes sense for
us to limit link relation discussions to the generic relation itself rather
than any specific implementation of it. I imagine the
pubsubhubbub<http://groups.google.com/group/pubsubhubbub>Google Group
(blind copied as it requires subscription to post) is the
appropriate forum for your [no doubt legitimate] concerns regarding the
protocol.

In terms of the relation, I think the description could be improved by
dropping references to entries, Atom and RSS. It is conceivable for example
that someone would want to be notified of an update to an HTML page (I'm
thinking about this currently for status updates to HTML renderings of
virtual machine resources) or indeed some other arbitrary resource. If we
[continue to] allow relations to be bound to protocols in spite of the
availability of content types and/or URI relations which are fit for the
purpose we're going to back ourselves into a corner before we know it.

Accordingly I propose the following description:

*Description: A URI for a "hub" that allows clients to register for
real-time updates to the resource.*

The PuSH(?) group may want to consider using a URI relation and/or dedicated
content type in addition to the generic "hub" relation.

Kind regards,

Sam

On Fri, Sep 11, 2009 at 1:57 AM, Jan Algermissen <algermissen1971@mac.com>wrote:

>
> On Sep 11, 2009, at 1:31 AM, John Panzer wrote:
>
>  Without getting into the appropriate discussion form question, what hub
>> resource semantics (and link relation definition) are you referring to
>> exactly?  I can't seem to find it, and it's hard to understand your
>> objection without it.
>>
>
> Section 7.3 says:
>
> "If, after a content fetch, the hub determines that the topic feed content
> has changed, the hub MUST send information about the changes to each of the
> subscribers to the topic."
>
> I understand this to imply that subscribers expect the hub to definitely
> send the notifications. What if the hub decides not to due to the number of
> subscribers it has? Or to turn this around: how would a subscriber ever know
> whether not receiving notifications means that there are not updates or that
> the hub stopped sending notifications.
>
> Jan
>
>
>
>
>
>> On Thu, Sep 10, 2009 at 12:40 PM, Jan Algermissen <
>> algermissen1971@mac.com> wrote:
>>
>> Lisa,
>>
>> not sure the following it is appropriate to discuss this here, so please
>> redirect me to the proper place if so.
>>
>> Hubs are being discovered by clients by way of the 'hub' link relation. I
>> am
>> concerned that the semantics of a hub resource (provided by the link
>> relation
>> definition) are imposing obligations on the server that are contrary what
>> one
>> would expect to see in the HTTP world.
>>
>> Or in other words: I think that the assumptions a client makes about the
>> behaviour
>> of a hub are too rigid. If a hub has more subscribers than it knows it can
>> handle
>> it might well decide not to notify them. A situation like this is
>> impossible to
>> prevent by the specification and I think the server should therefore
>> explicitly be
>> given much more freedom regarding its behavior upon a ping.
>>
>> Especially given the use of Atom which in a sense implies a very
>> unconstrained
>> protocol.
>>
>> (Sorry if this discussion is already going on elsewhere)
>>
>> Jan
>>
>>
>>
>> On Sep 10, 2009, at 7:30 PM, Lisa Dusseault wrote:
>>
>>
>> Comments welcome on the following request
>>
>> thx,
>> lisa
>>
>> ---
>> General Request for Assignments (link-relations)
>>
>> Contact Name :
>> Brett Slatkin
>>
>> Type of Assignment :
>> I want to add a new Atom Link Relation type for the PubSubHubbub protocol
>>
>> (http://pubsubhubbub.googlecode.com). The relation type is "hub".
>>
>> Registry :
>> http://www.iana.org/assignments/link-relations/link-relations.xhtml
>>
>>
>> Description :
>> The new  is used for discovery of Hubs,
>> which enables real-time notifications of entries in Atom and RSS feeds.
>> Without making the relation type official, we're not in compliance with
>> the
>>
>> Atom spec.
>>
>> Additional Info :
>> http://pubsubhubbub.googlecode.com/svn/trunk/pubsubhubbub-core-0.1.html
>>
>>
>>
>>
>
>

--001485f20b5abe641404734bd93c
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Jan et al,<div><br></div><div>In line with comments I&#39;ve made in other =
threads I think it makes sense for us to limit link relation discussions to=
 the generic relation itself rather than any specific implementation of it.=
 I imagine the <a href=3D"http://groups.google.com/group/pubsubhubbub">pubs=
ubhubbub</a> Google Group (blind copied as it requires subscription to post=
) is the appropriate forum for your [no doubt legitimate] concerns regardin=
g the protocol.</div>
<div><br></div><div>In terms of the relation, I think the description could=
 be improved by dropping references to entries, Atom and RSS. It is conceiv=
able for example that someone would want to be notified of an update to an =
HTML page (I&#39;m thinking about this currently for status updates to HTML=
 renderings of virtual machine resources) or indeed some other arbitrary re=
source. If we [continue to] allow relations to be bound to protocols in spi=
te of the availability of content types and/or URI relations which are fit =
for the purpose we&#39;re going to back ourselves into a corner before we k=
now it.</div>
<div><br></div><div>Accordingly I propose the following description:</div><=
div><br></div><div><i>Description: A URI for a &quot;hub&quot; that allows =
clients to register for real-time updates to the resource.</i></div><div>
<br></div><div>The PuSH(?) group may want to consider using a URI relation =
and/or dedicated content type in addition to the generic &quot;hub&quot; re=
lation.</div><div><br></div><div>Kind regards,</div><div><br></div><div>
Sam</div><div><br><div class=3D"gmail_quote">On Fri, Sep 11, 2009 at 1:57 A=
M, Jan Algermissen <span dir=3D"ltr">&lt;<a href=3D"mailto:algermissen1971@=
mac.com">algermissen1971@mac.com</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex;">
<div class=3D"im"><br>
On Sep 11, 2009, at 1:31 AM, John Panzer wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Without getting into the appropriate discussion form question, what hub res=
ource semantics (and link relation definition) are you referring to exactly=
? =A0I can&#39;t seem to find it, and it&#39;s hard to understand your obje=
ction without it.<br>

</blockquote>
<br></div>
Section 7.3 says:<br>
<br>
&quot;If, after a content fetch, the hub determines that the topic feed con=
tent has changed, the hub MUST send information about the changes to each o=
f the subscribers to the topic.&quot;<br>
<br>
I understand this to imply that subscribers expect the hub to definitely se=
nd the notifications. What if the hub decides not to due to the number of s=
ubscribers it has? Or to turn this around: how would a subscriber ever know=
 whether not receiving notifications means that there are not updates or th=
at the hub stopped sending notifications.<br>
<font color=3D"#888888">
<br>
Jan</font><div><div></div><div class=3D"h5"><br>
<br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
On Thu, Sep 10, 2009 at 12:40 PM, Jan Algermissen &lt;<a href=3D"mailto:alg=
ermissen1971@mac.com" target=3D"_blank">algermissen1971@mac.com</a>&gt; wro=
te:<br>
<br>
Lisa,<br>
<br>
not sure the following it is appropriate to discuss this here, so please re=
direct me to the proper place if so.<br>
<br>
Hubs are being discovered by clients by way of the &#39;hub&#39; link relat=
ion. I am<br>
concerned that the semantics of a hub resource (provided by the link relati=
on<br>
definition) are imposing obligations on the server that are contrary what o=
ne<br>
would expect to see in the HTTP world.<br>
<br>
Or in other words: I think that the assumptions a client makes about the be=
haviour<br>
of a hub are too rigid. If a hub has more subscribers than it knows it can =
handle<br>
it might well decide not to notify them. A situation like this is impossibl=
e to<br>
prevent by the specification and I think the server should therefore explic=
itly be<br>
given much more freedom regarding its behavior upon a ping.<br>
<br>
Especially given the use of Atom which in a sense implies a very unconstrai=
ned<br>
protocol.<br>
<br>
(Sorry if this discussion is already going on elsewhere)<br>
<br>
Jan<br>
<br>
<br>
<br>
On Sep 10, 2009, at 7:30 PM, Lisa Dusseault wrote:<br>
<br>
<br>
Comments welcome on the following request<br>
<br>
thx,<br>
lisa<br>
<br>
---<br>
General Request for Assignments (link-relations)<br>
<br>
Contact Name :<br>
Brett Slatkin<br>
<br>
Type of Assignment :<br>
I want to add a new Atom Link Relation type for the PubSubHubbub protocol<b=
r>
<br>
(<a href=3D"http://pubsubhubbub.googlecode.com" target=3D"_blank">http://pu=
bsubhubbub.googlecode.com</a>). The relation type is &quot;hub&quot;.<br>
<br>
Registry :<br>
<a href=3D"http://www.iana.org/assignments/link-relations/link-relations.xh=
tml" target=3D"_blank">http://www.iana.org/assignments/link-relations/link-=
relations.xhtml</a><br>
<br>
<br>
Description :<br>
The new =A0is used for discovery of Hubs,<br>
which enables real-time notifications of entries in Atom and RSS feeds.<br>
Without making the relation type official, we&#39;re not in compliance with=
 the<br>
<br>
Atom spec.<br>
<br>
Additional Info :<br>
<a href=3D"http://pubsubhubbub.googlecode.com/svn/trunk/pubsubhubbub-" targ=
et=3D"_blank">http://pubsubhubbub.googlecode.com/svn/trunk/pubsubhubbub-</a=
>core-0.1.html<br>
<br>
<br>
<br>
</blockquote>
<br>
<br>
</div></div></blockquote></div><br></div>

--001485f20b5abe641404734bd93c--


From owner-atom-syntax@mail.imc.org  Fri Sep 11 05:07:58 2009
Return-Path: <owner-atom-syntax@mail.imc.org>
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 00AC028C0F8 for <ietfarch-atompub-archive@core3.amsl.com>; Fri, 11 Sep 2009 05:07:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.823
X-Spam-Level: 
X-Spam-Status: No, score=-4.823 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, J_CHICKENPOX_45=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 r8gegx5j2L1q for <ietfarch-atompub-archive@core3.amsl.com>; Fri, 11 Sep 2009 05:07:57 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 20CE83A68F3 for <atompub-archive@ietf.org>; Fri, 11 Sep 2009 05:07:57 -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 n8BC0uUV090579 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 11 Sep 2009 05:00:56 -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 n8BC0uWa090578; Fri, 11 Sep 2009 05:00:56 -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 mail-yx0-f202.google.com (mail-yx0-f202.google.com [209.85.210.202]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n8BC0tKD090569 for <atom-syntax@imc.org>; Fri, 11 Sep 2009 05:00:56 -0700 (MST) (envelope-from hadrien.gardeur@feedbooks.com)
Received: by yxe40 with SMTP id 40so1275304yxe.28 for <atom-syntax@imc.org>; Fri, 11 Sep 2009 05:00:55 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.101.85.15 with SMTP id n15mr3063332anl.139.1252670454557; Fri,  11 Sep 2009 05:00:54 -0700 (PDT)
In-Reply-To: <21606dcf0909110445s78ea728cueb158ff588f394a5@mail.gmail.com>
References: <ca722a9e0909101030g6ccbc1e2t823f2abd19307bea@mail.gmail.com>  <8860AD10-B0C5-4BEF-8C68-731973EF4046@mac.com> <30ac519d0909101631m14782ce8vd085629237b0e444@mail.gmail.com>  <C86DEC0A-6370-4C0B-98A9-3806F2014AE5@mac.com> <21606dcf0909110445s78ea728cueb158ff588f394a5@mail.gmail.com>
From: Hadrien Gardeur <hadrien.gardeur@feedbooks.com>
Date: Fri, 11 Sep 2009 14:00:34 +0200
Message-ID: <404dcbd20909110500j5394c43dve10264c01a7a6244@mail.gmail.com>
Subject: Re: Input on request for link relation
To: Sam Johnston <samj@samj.net>
Cc: Jan Algermissen <algermissen1971@mac.com>, jpanzer@acm.org, Lisa Dusseault <lisa.dusseault@gmail.com>, Atom-Syntax Syntax <atom-syntax@imc.org>, ietf-http-wg@w3.org
Content-Type: multipart/alternative; boundary=001636ed667d7732bc04734c1179
Sender: owner-atom-syntax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/atom-syntax/mail-archive/>
List-Unsubscribe: <mailto:atom-syntax-request@imc.org?body=unsubscribe>
List-ID: <atom-syntax.imc.org>

--001636ed667d7732bc04734c1179
Content-Type: text/plain; charset=UTF-8

>
> In line with comments I've made in other threads I think it makes sense for
> us to limit link relation discussions to the generic relation itself rather
> than any specific implementation of it.
>

Several relations would need a similar treatment.

For example:

*edit:* An IRI of an editable Member Entry. When appearing within an
> atom:entry, the href IRI can be used to retrieve, update and delete the
> Resource represented by that Entry.


BTW, what would be the generic link relation to indicate an AtomPub
collection (only the service document is registered at IANA) ?


> In terms of the relation, I think the description could be improved by
> dropping references to entries, Atom and RSS. It is conceivable for example
> that someone would want to be notified of an update to an HTML page (I'm
> thinking about this currently for status updates to HTML renderings of
> virtual machine resources) or indeed some other arbitrary resource. If we
> [continue to] allow relations to be bound to protocols in spite of the
> availability of content types and/or URI relations which are fit for the
> purpose we're going to back ourselves into a corner before we know it.


I agree. We need a better policy for rel values. Currently, it seems that
new rel values are added to the IANA link registry whenever a new RFC is
adopted. These relationships could have a much broader scope and shouldn't
be bound to particular protocols.

Hadrien

--001636ed667d7732bc04734c1179
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div>In line wit=
h comments I&#39;ve made in other threads I think it makes sense for us to =
limit link relation discussions to the generic relation itself rather than =
any specific implementation of it. </div>

</blockquote><div><br></div><div>Several relations would need a similar tre=
atment.</div><div><br></div><div>For example:</div><div><br></div><blockquo=
te class=3D"gmail_quote" style=3D"margin-top: 0px; margin-right: 0px; margi=
n-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-colo=
r: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">

<b>edit:</b> An IRI of an editable Member Entry. When appearing within an a=
tom:entry, the href IRI can be used to retrieve, update and delete the Reso=
urce represented by that Entry.</blockquote><div><br></div><div>BTW, what w=
ould be the generic link relation to indicate an AtomPub collection (only t=
he service document is registered at IANA) ?=C2=A0</div>

<div>=C2=A0</div></div><span class=3D"Apple-style-span" style=3D"border-col=
lapse: collapse; "><blockquote class=3D"gmail_quote" style=3D"margin-top: 0=
px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-=
width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid=
; padding-left: 1ex; ">

In terms of the relation, I think the description could be improved by drop=
ping references to entries, Atom and RSS. It is conceivable for example tha=
t someone would want to be notified of an update to an HTML page (I&#39;m t=
hinking about this currently for status updates to HTML renderings of virtu=
al machine resources) or indeed some other arbitrary resource. If we [conti=
nue to] allow relations to be bound to protocols in spite of the availabili=
ty of content types and/or URI relations which are fit for the purpose we&#=
39;re going to back ourselves into a corner before we know it.</blockquote>

<div><br></div><div>I agree. We need a better policy for rel values. Curren=
tly, it seems that new rel values are added to the IANA link registry whene=
ver a new RFC is adopted. These relationships could have a much broader sco=
pe and shouldn&#39;t be bound to particular protocols.=C2=A0</div>

<div><br></div><div>Hadrien</div></span>

--001636ed667d7732bc04734c1179--


From owner-atom-syntax@mail.imc.org  Fri Sep 11 05:52:24 2009
Return-Path: <owner-atom-syntax@mail.imc.org>
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 0BEAB3A6A9A for <ietfarch-atompub-archive@core3.amsl.com>; Fri, 11 Sep 2009 05:52:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.233
X-Spam-Level: 
X-Spam-Status: No, score=-6.233 tagged_above=-999 required=5 tests=[AWL=-0.187, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, 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 ypFXPKCzJno5 for <ietfarch-atompub-archive@core3.amsl.com>; Fri, 11 Sep 2009 05:52:23 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 40B313A6894 for <atompub-archive@ietf.org>; Fri, 11 Sep 2009 05:52:23 -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 n8BCfiTK093046 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 11 Sep 2009 05:41:44 -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 n8BCfitx093045; Fri, 11 Sep 2009 05:41:44 -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 mail.gmx.net (mail.gmx.net [213.165.64.20]) by balder-227.proper.com (8.14.2/8.14.2) with SMTP id n8BCfbsi093035 for <atom-syntax@imc.org>; Fri, 11 Sep 2009 05:41:43 -0700 (MST) (envelope-from julian.reschke@gmx.de)
Received: (qmail invoked by alias); 11 Sep 2009 12:41:36 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.117]) [217.91.35.233] by mail.gmx.net (mp056) with SMTP; 11 Sep 2009 14:41:36 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/xB8JKX0vxa9/586mALQr4f8Pnnmsy1NJ6Jp0ENU 8CrHvVxhPz344g
Message-ID: <4AAA4574.4000604@gmx.de>
Date: Fri, 11 Sep 2009 14:41:24 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.0.4) Gecko/20060516 Thunderbird/1.5.0.4 Mnenhy/0.7.4.666
MIME-Version: 1.0
To: Hadrien Gardeur <hadrien.gardeur@feedbooks.com>
CC: Sam Johnston <samj@samj.net>, Jan Algermissen <algermissen1971@mac.com>, jpanzer@acm.org, Lisa Dusseault <lisa.dusseault@gmail.com>, Atom-Syntax Syntax <atom-syntax@imc.org>, ietf-http-wg@w3.org
Subject: Re: Input on request for link relation
References: <ca722a9e0909101030g6ccbc1e2t823f2abd19307bea@mail.gmail.com> 	<8860AD10-B0C5-4BEF-8C68-731973EF4046@mac.com> <30ac519d0909101631m14782ce8vd085629237b0e444@mail.gmail.com> 	<C86DEC0A-6370-4C0B-98A9-3806F2014AE5@mac.com> <21606dcf0909110445s78ea728cueb158ff588f394a5@mail.gmail.com> <404dcbd20909110500j5394c43dve10264c01a7a6244@mail.gmail.com>
In-Reply-To: <404dcbd20909110500j5394c43dve10264c01a7a6244@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.75
Sender: owner-atom-syntax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/atom-syntax/mail-archive/>
List-Unsubscribe: <mailto:atom-syntax-request@imc.org?body=unsubscribe>
List-ID: <atom-syntax.imc.org>

Hadrien Gardeur wrote:
> ...
> I agree. We need a better policy for rel values. Currently, it seems 
> that new rel values are added to the IANA link registry whenever a new 
> RFC is adopted. These relationships could have a much broader scope and 
> shouldn't be bound to particular protocols. 
> ...

<http://tools.ietf.org/html/draft-nottingham-http-link-header-06>.

BR, Julian


From owner-atom-syntax@mail.imc.org  Fri Sep 11 06:25:46 2009
Return-Path: <owner-atom-syntax@mail.imc.org>
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 E40343A67F6 for <ietfarch-atompub-archive@core3.amsl.com>; Fri, 11 Sep 2009 06:25:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.302
X-Spam-Level: 
X-Spam-Status: No, score=-6.302 tagged_above=-999 required=5 tests=[AWL=-1.479, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, J_CHICKENPOX_45=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 kCG5CMORI90Y for <ietfarch-atompub-archive@core3.amsl.com>; Fri, 11 Sep 2009 06:25:45 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 5EA0C3A68A9 for <atompub-archive@ietf.org>; Fri, 11 Sep 2009 06:25:45 -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 n8BDHsut095289 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 11 Sep 2009 06:17:54 -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 n8BDHsvq095288; Fri, 11 Sep 2009 06:17:54 -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 eu1sys200aog105.obsmtp.com (eu1sys200aog105.obsmtp.com [207.126.144.119]) by balder-227.proper.com (8.14.2/8.14.2) with SMTP id n8BDHk2r095266 for <atom-syntax@imc.org>; Fri, 11 Sep 2009 06:17:52 -0700 (MST) (envelope-from samj@samj.net)
Received: from source ([72.14.220.158]) by eu1sys200aob105.postini.com ([207.126.147.11]) with SMTP ID DSNKSqpN+kHddi5d0PrOYjLRK5qqgPI9jc4E@postini.com; Fri, 11 Sep 2009 13:17:52 UTC
Received: by fg-out-1718.google.com with SMTP id e21so1770076fga.16 for <atom-syntax@imc.org>; Fri, 11 Sep 2009 06:17:46 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.86.18.34 with SMTP id 34mr2298168fgr.2.1252675066039; Fri, 11  Sep 2009 06:17:46 -0700 (PDT)
In-Reply-To: <404dcbd20909110500j5394c43dve10264c01a7a6244@mail.gmail.com>
References: <ca722a9e0909101030g6ccbc1e2t823f2abd19307bea@mail.gmail.com> <8860AD10-B0C5-4BEF-8C68-731973EF4046@mac.com> <30ac519d0909101631m14782ce8vd085629237b0e444@mail.gmail.com> <C86DEC0A-6370-4C0B-98A9-3806F2014AE5@mac.com> <21606dcf0909110445s78ea728cueb158ff588f394a5@mail.gmail.com> <404dcbd20909110500j5394c43dve10264c01a7a6244@mail.gmail.com>
Date: Fri, 11 Sep 2009 15:17:46 +0200
Message-ID: <21606dcf0909110617y40586e53x213e5e8febc4a9e8@mail.gmail.com>
Subject: Re: Input on request for link relation
From: Sam Johnston <samj@samj.net>
To: Hadrien Gardeur <hadrien.gardeur@feedbooks.com>
Cc: Jan Algermissen <algermissen1971@mac.com>, jpanzer@acm.org, Lisa Dusseault <lisa.dusseault@gmail.com>, Atom-Syntax Syntax <atom-syntax@imc.org>, ietf-http-wg@w3.org, Mark Nottingham <mnot@mnot.net>, apps-discuss@ietf.org
Content-Type: multipart/alternative; boundary=00c09ffb554454905404734d24ea
Sender: owner-atom-syntax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/atom-syntax/mail-archive/>
List-Unsubscribe: <mailto:atom-syntax-request@imc.org?body=unsubscribe>
List-ID: <atom-syntax.imc.org>

--00c09ffb554454905404734d24ea
Content-Type: text/plain; charset=ISO-8859-1

On Fri, Sep 11, 2009 at 2:00 PM, Hadrien Gardeur <
hadrien.gardeur@feedbooks.com> wrote:
>> In line with comments I've made in other threads I think it makes sense
>> for us to limit link relation discussions to the generic relation itself
>> rather than any specific implementation of it.
>
> Several relations would need a similar treatment.

Yes, though I believe Mark's "Web
Linking<http://tools.ietf.org/html/draft-nottingham-http-link-header>"
draft does this already.

> For example:
>>
>> edit: An IRI of an editable Member Entry. When appearing within an
>> atom:entry, the href IRI can be used to retrieve, update and delete the
>> Resource represented by that Entry.
>
> BTW, what would be the generic link relation to indicate an AtomPub
> collection (only the service document is registered at IANA) ?

I started thinking about this earlier in the week with a view to having e.g.
a representation of a bookshelf referring to a collection/feed/url-list/etc.
of books using rel="collection". I then started looking at
parent/child/sibling relationships which are currently being discussed in a
separate thread (my preference is for something like e.g. "rel=descendant
level=2" for grandchildren as I subsequently realised that suggested
abbreviations "asc" for ascendant and "desc" for descendant can be confused
with item ordering). Do you think these "family" relations serve all the use
cases for a "collection" relation?

> I agree. We need a better policy for rel values. Currently, it seems that
> new rel values are added to the IANA link registry whenever a new RFC is
> adopted. These relationships could have a much broader scope and shouldn't
> be bound to particular protocols.

Great. I don't think there's much contention over this point (at least I've
not yet seen any) and the draft spells out the requirements (which can be
summarised as "broadly useful") reasonably well:

> Commonly-used relation types with a clear meaning that are shared

across applications can be registered as tokens for convenience and

to promote reuse.  For example, "self" and "alternate" are registered

relation types, because they are broadly useful.


The registry also outlines the process which involves a dedicated expert and
public comment period:

6.2.  Link Relation Type Registry


>    This specification establishes the Link Relation Type Registry, and

   updates Atom [RFC4287] to refer to it in place of the "Registry of

   Link Relations".


>    The requirements for registered relation types are described in

   Section 4.1.


>    Relation types are registered on the advice of a Designated Expert

   (appointed by the IESG or their delegate), with a Specification

   Required (using terminology from [RFC5226]).


>    Registration requests consist of the completed registration template

   below, typically published in an RFC or Open Standard (in the sense

   described by [RFC2026], Section 7).  However, to allow for the

   allocation of values prior to publication, the Designated Expert may

   approve registration once they are satisfied that an RFC (or other

   Open Standard) will be published.


>    The registration template is:


>    o  Relation Name:

   o  Description:

   o  Reference:

   o  Notes: [optional]


>    Upon receiving a registration request (usually via IANA), the

   Designated Expert should request review and comment from the

   apps-discuss@ietf.org mailing list (or a successor designated by the

   APPS Area Directors).  Before a period of 30 days has passed, the

   Designated Expert will either approve or deny the registration

   request, communicating this decision both to the review list and to

   IANA.  Denials should include an explanation and, if applicable,

   suggestions as to how to make the request successful.


Ironically the apps-discuss list wasn't included so I am adding them now.
One nitpick about the process is that it seems a request can be denied with
a suggestion for another relation (for example we might prefer to use
something like "push" or "notif[y|ier|ication|ications" rather than "hub"
for this one) but then that would require restarting the process where it
should proceed to registration immediately if the change is accepted by the
applicant.

I also question the relevance of the "reference" field in the registry as
this links relations to implementations which I think we agree is a bad
thing - the registry should capture all the necessary semantics without
reliance on external references. It may be interesting to list zero or more
implementations of the relation (that is, make the "reference" field
optional as well and allow others to add themselves to it), however I'm not
sure the maintenance load is worth the effort.

Sam

--00c09ffb554454905404734d24ea
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Fri, Sep 11, 2009 at 2:00 PM, Hadrien Gardeur &lt;<a href=3D"mailto:hadr=
ien.gardeur@feedbooks.com">hadrien.gardeur@feedbooks.com</a>&gt; wrote:<br>=
&gt;&gt; In line with comments I&#39;ve made in other threads I think it ma=
kes sense<br>
&gt;&gt; for us to limit link relation discussions to the generic relation =
itself<br>&gt;&gt; rather than any specific implementation of it.<br>&gt;<b=
r>&gt; Several relations would need a similar treatment.<br><br>Yes, though=
 I believe Mark&#39;s &quot;<a href=3D"http://tools.ietf.org/html/draft-not=
tingham-http-link-header">Web Linking</a>&quot; draft does this already.<br=
>
<br>&gt; For example:<br>&gt;&gt;<br>&gt;&gt; edit: An IRI of an editable M=
ember Entry. When appearing within an<br>&gt;&gt; atom:entry, the href IRI =
can be used to retrieve, update and delete the<br>&gt;&gt; Resource represe=
nted by that Entry.<br>
&gt;<br>&gt; BTW, what would be the generic link relation to indicate an At=
omPub<br>&gt; collection (only the service document is registered at IANA) =
?=A0<br><br>I started thinking about this earlier in the week with a view t=
o having e.g. a representation of a bookshelf referring to a collection/fee=
d/url-list/etc. of books using rel=3D&quot;collection&quot;. I then started=
 looking at parent/child/sibling relationships which are currently being di=
scussed in a separate thread (my preference is for something like e.g. &quo=
t;rel=3Ddescendant level=3D2&quot; for grandchildren as I subsequently real=
ised that suggested abbreviations &quot;asc&quot; for ascendant and &quot;d=
esc&quot; for descendant can be confused with item ordering). Do you think =
these &quot;family&quot; relations serve all the use cases for a &quot;coll=
ection&quot; relation?<br>
<br>&gt; I agree. We need a better policy for rel values. Currently, it see=
ms that<br>&gt; new rel values are added to the IANA link registry whenever=
 a new RFC is<br>&gt; adopted. These relationships could have a much broade=
r scope and shouldn&#39;t<br>
&gt; be bound to particular protocols.=A0<br><br>Great. I don&#39;t think t=
here&#39;s much contention over this point (at least I&#39;ve not yet seen =
any) and the draft spells out the requirements (which can be summarised as =
&quot;broadly useful&quot;) reasonably well:<div>
<br></div><div><blockquote class=3D"gmail_quote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-widt=
h: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; pa=
dding-left: 1ex; ">
Commonly-used relation types with a clear meaning that are shared</blockquo=
te><blockquote class=3D"gmail_quote" style=3D"margin-top: 0px; margin-right=
: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; bord=
er-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: =
1ex; ">
across applications can be registered as tokens for convenience and</blockq=
uote><blockquote class=3D"gmail_quote" style=3D"margin-top: 0px; margin-rig=
ht: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; bo=
rder-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left=
: 1ex; ">
to promote reuse. =A0For example, &quot;self&quot; and &quot;alternate&quot=
; are registered</blockquote><blockquote class=3D"gmail_quote" style=3D"mar=
gin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; bo=
rder-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-st=
yle: solid; padding-left: 1ex; ">
relation types, because they are broadly useful.</blockquote><div><br></div=
><div>The registry also outlines the process which involves a dedicated exp=
ert and public comment period:</div><br><div><blockquote class=3D"gmail_quo=
te" style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin=
-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204)=
; border-left-style: solid; padding-left: 1ex; ">
6.2. =A0Link Relation Type Registry</blockquote><blockquote class=3D"gmail_=
quote" style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; mar=
gin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 2=
04); border-left-style: solid; padding-left: 1ex; ">
<br></blockquote><blockquote class=3D"gmail_quote" style=3D"margin-top: 0px=
; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-wi=
dth: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; =
padding-left: 1ex; ">
=A0=A0 This specification establishes the Link Relation Type Registry, and<=
/blockquote><blockquote class=3D"gmail_quote" style=3D"margin-top: 0px; mar=
gin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: =
1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; paddi=
ng-left: 1ex; ">
=A0=A0 updates Atom [RFC4287] to refer to it in place of the &quot;Registry=
 of</blockquote><blockquote class=3D"gmail_quote" style=3D"margin-top: 0px;=
 margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-wid=
th: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; p=
adding-left: 1ex; ">
=A0=A0 Link Relations&quot;.</blockquote><blockquote class=3D"gmail_quote" =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-lef=
t: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); bo=
rder-left-style: solid; padding-left: 1ex; ">
<br></blockquote><blockquote class=3D"gmail_quote" style=3D"margin-top: 0px=
; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-wi=
dth: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; =
padding-left: 1ex; ">
=A0=A0 The requirements for registered relation types are described in</blo=
ckquote><blockquote class=3D"gmail_quote" style=3D"margin-top: 0px; margin-=
right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px;=
 border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-l=
eft: 1ex; ">
=A0=A0 Section 4.1.</blockquote><blockquote class=3D"gmail_quote" style=3D"=
margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex;=
 border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left=
-style: solid; padding-left: 1ex; ">
<br></blockquote><blockquote class=3D"gmail_quote" style=3D"margin-top: 0px=
; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-wi=
dth: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; =
padding-left: 1ex; ">
=A0=A0 Relation types are registered on the advice of a Designated Expert</=
blockquote><blockquote class=3D"gmail_quote" style=3D"margin-top: 0px; marg=
in-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1=
px; border-left-color: rgb(204, 204, 204); border-left-style: solid; paddin=
g-left: 1ex; ">
=A0=A0 (appointed by the IESG or their delegate), with a Specification</blo=
ckquote><blockquote class=3D"gmail_quote" style=3D"margin-top: 0px; margin-=
right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px;=
 border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-l=
eft: 1ex; ">
=A0=A0 Required (using terminology from [RFC5226]).</blockquote><blockquote=
 class=3D"gmail_quote" style=3D"margin-top: 0px; margin-right: 0px; margin-=
bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color:=
 rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
<br></blockquote><blockquote class=3D"gmail_quote" style=3D"margin-top: 0px=
; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-wi=
dth: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; =
padding-left: 1ex; ">
=A0=A0 Registration requests consist of the completed registration template=
</blockquote><blockquote class=3D"gmail_quote" style=3D"margin-top: 0px; ma=
rgin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width:=
 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padd=
ing-left: 1ex; ">
=A0=A0 below, typically published in an RFC or Open Standard (in the sense<=
/blockquote><blockquote class=3D"gmail_quote" style=3D"margin-top: 0px; mar=
gin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: =
1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; paddi=
ng-left: 1ex; ">
=A0=A0 described by [RFC2026], Section 7). =A0However, to allow for the</bl=
ockquote><blockquote class=3D"gmail_quote" style=3D"margin-top: 0px; margin=
-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px=
; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-=
left: 1ex; ">
=A0=A0 allocation of values prior to publication, the Designated Expert may=
</blockquote><blockquote class=3D"gmail_quote" style=3D"margin-top: 0px; ma=
rgin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width:=
 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padd=
ing-left: 1ex; ">
=A0=A0 approve registration once they are satisfied that an RFC (or other</=
blockquote><blockquote class=3D"gmail_quote" style=3D"margin-top: 0px; marg=
in-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1=
px; border-left-color: rgb(204, 204, 204); border-left-style: solid; paddin=
g-left: 1ex; ">
=A0=A0 Open Standard) will be published.</blockquote><blockquote class=3D"g=
mail_quote" style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px=
; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 2=
04, 204); border-left-style: solid; padding-left: 1ex; ">
<br></blockquote><blockquote class=3D"gmail_quote" style=3D"margin-top: 0px=
; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-wi=
dth: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; =
padding-left: 1ex; ">
=A0=A0 The registration template is:</blockquote><blockquote class=3D"gmail=
_quote" style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; ma=
rgin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, =
204); border-left-style: solid; padding-left: 1ex; ">
<br></blockquote><blockquote class=3D"gmail_quote" style=3D"margin-top: 0px=
; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-wi=
dth: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; =
padding-left: 1ex; ">
=A0=A0 o =A0Relation Name:</blockquote><blockquote class=3D"gmail_quote" st=
yle=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left:=
 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); bord=
er-left-style: solid; padding-left: 1ex; ">
=A0=A0 o =A0Description:</blockquote><blockquote class=3D"gmail_quote" styl=
e=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0=
.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border=
-left-style: solid; padding-left: 1ex; ">
=A0=A0 o =A0Reference:</blockquote><blockquote class=3D"gmail_quote" style=
=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.=
8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-=
left-style: solid; padding-left: 1ex; ">
=A0=A0 o =A0Notes: [optional]</blockquote><blockquote class=3D"gmail_quote"=
 style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-le=
ft: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); b=
order-left-style: solid; padding-left: 1ex; ">
<br></blockquote><blockquote class=3D"gmail_quote" style=3D"margin-top: 0px=
; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-wi=
dth: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; =
padding-left: 1ex; ">
=A0=A0 Upon receiving a registration request (usually via IANA), the</block=
quote><blockquote class=3D"gmail_quote" style=3D"margin-top: 0px; margin-ri=
ght: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; b=
order-left-color: rgb(204, 204, 204); border-left-style: solid; padding-lef=
t: 1ex; ">
=A0=A0 Designated Expert should request review and comment from the</blockq=
uote><blockquote class=3D"gmail_quote" style=3D"margin-top: 0px; margin-rig=
ht: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; bo=
rder-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left=
: 1ex; ">
=A0=A0 <a href=3D"mailto:apps-discuss@ietf.org">apps-discuss@ietf.org</a> m=
ailing list (or a successor designated by the</blockquote><blockquote class=
=3D"gmail_quote" style=3D"margin-top: 0px; margin-right: 0px; margin-bottom=
: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(2=
04, 204, 204); border-left-style: solid; padding-left: 1ex; ">
=A0=A0 APPS Area Directors). =A0Before a period of 30 days has passed, the<=
/blockquote><blockquote class=3D"gmail_quote" style=3D"margin-top: 0px; mar=
gin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: =
1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; paddi=
ng-left: 1ex; ">
=A0=A0 Designated Expert will either approve or deny the registration</bloc=
kquote><blockquote class=3D"gmail_quote" style=3D"margin-top: 0px; margin-r=
ight: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; =
border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-le=
ft: 1ex; ">
=A0=A0 request, communicating this decision both to the review list and to<=
/blockquote><blockquote class=3D"gmail_quote" style=3D"margin-top: 0px; mar=
gin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: =
1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; paddi=
ng-left: 1ex; ">
=A0=A0 IANA. =A0Denials should include an explanation and, if applicable,</=
blockquote><blockquote class=3D"gmail_quote" style=3D"margin-top: 0px; marg=
in-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1=
px; border-left-color: rgb(204, 204, 204); border-left-style: solid; paddin=
g-left: 1ex; ">
=A0=A0 suggestions as to how to make the request successful.</blockquote><d=
iv><br></div></div><div>Ironically the apps-discuss list wasn&#39;t include=
d so I am adding them now. One nitpick about the process is that it seems a=
 request can be denied with a suggestion for another relation (for example =
we might prefer to use something like &quot;push&quot; or &quot;notif[y|ier=
|ication|ications&quot; rather than &quot;hub&quot; for this one) but then =
that would require restarting the process where it should proceed to regist=
ration immediately if the change is accepted by the applicant.<br>
</div><div><br></div><div>I also question the relevance of the &quot;refere=
nce&quot; field in the registry as this links relations to implementations =
which I think we agree is a bad thing - the registry should capture all the=
 necessary semantics without reliance on external references. It may be int=
eresting to list zero or more implementations of the relation (that is, mak=
e the &quot;reference&quot; field optional as well and allow others to add =
themselves to it), however I&#39;m not sure the maintenance load is worth t=
he effort.</div>
<div><br>Sam<br><div><br></div></div></div>

--00c09ffb554454905404734d24ea--


From owner-atom-syntax@mail.imc.org  Fri Sep 11 06:49:29 2009
Return-Path: <owner-atom-syntax@mail.imc.org>
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 3F54F3A67B1 for <ietfarch-atompub-archive@core3.amsl.com>; Fri, 11 Sep 2009 06:49:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.136
X-Spam-Level: 
X-Spam-Status: No, score=-4.136 tagged_above=-999 required=5 tests=[AWL=1.287, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, 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 BbeczIRb6SMf for <ietfarch-atompub-archive@core3.amsl.com>; Fri, 11 Sep 2009 06:49:28 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 164FA3A6A46 for <atompub-archive@ietf.org>; Fri, 11 Sep 2009 06:48:55 -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 n8BDgJo2096444 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 11 Sep 2009 06:42:19 -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 n8BDgJCg096443; Fri, 11 Sep 2009 06:42:19 -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 mail-yx0-f202.google.com (mail-yx0-f202.google.com [209.85.210.202]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n8BDgHL4096436 for <atom-syntax@imc.org>; Fri, 11 Sep 2009 06:42:18 -0700 (MST) (envelope-from hadrien.gardeur@feedbooks.com)
Received: by yxe40 with SMTP id 40so1375231yxe.28 for <atom-syntax@imc.org>; Fri, 11 Sep 2009 06:42:17 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.101.45.20 with SMTP id x20mr3267933anj.26.1252676537147; Fri,  11 Sep 2009 06:42:17 -0700 (PDT)
In-Reply-To: <21606dcf0909110617y40586e53x213e5e8febc4a9e8@mail.gmail.com>
References: <ca722a9e0909101030g6ccbc1e2t823f2abd19307bea@mail.gmail.com>  <8860AD10-B0C5-4BEF-8C68-731973EF4046@mac.com> <30ac519d0909101631m14782ce8vd085629237b0e444@mail.gmail.com>  <C86DEC0A-6370-4C0B-98A9-3806F2014AE5@mac.com> <21606dcf0909110445s78ea728cueb158ff588f394a5@mail.gmail.com>  <404dcbd20909110500j5394c43dve10264c01a7a6244@mail.gmail.com>  <21606dcf0909110617y40586e53x213e5e8febc4a9e8@mail.gmail.com>
From: Hadrien Gardeur <hadrien.gardeur@feedbooks.com>
Date: Fri, 11 Sep 2009 15:41:57 +0200
Message-ID: <404dcbd20909110641g131d8320rcb4f9acd828735d2@mail.gmail.com>
Subject: Re: Input on request for link relation
To: Sam Johnston <samj@samj.net>
Cc: Jan Algermissen <algermissen1971@mac.com>, jpanzer@acm.org, Lisa Dusseault <lisa.dusseault@gmail.com>, Atom-Syntax Syntax <atom-syntax@imc.org>, ietf-http-wg@w3.org, Mark Nottingham <mnot@mnot.net>, apps-discuss@ietf.org
Content-Type: multipart/alternative; boundary=001636ed6e4903e2ee04734d7c9d
Sender: owner-atom-syntax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/atom-syntax/mail-archive/>
List-Unsubscribe: <mailto:atom-syntax-request@imc.org?body=unsubscribe>
List-ID: <atom-syntax.imc.org>

--001636ed6e4903e2ee04734d7c9d
Content-Type: text/plain; charset=UTF-8

>
> Yes, though I believe Mark's "Web Linking<http://tools.ietf.org/html/draft-nottingham-http-link-header>"
> draft does this already.


It does (Section 6.2).


> I started thinking about this earlier in the week with a view to having
> e.g. a representation of a bookshelf referring to a
> collection/feed/url-list/etc. of books using rel="collection". I then
> started looking at parent/child/sibling relationships which are currently
> being discussed in a separate thread (my preference is for something like
> e.g. "rel=descendant level=2" for grandchildren as I subsequently realised
> that suggested abbreviations "asc" for ascendant and "desc" for descendant
> can be confused with item ordering). Do you think these "family" relations
> serve all the use cases for a "collection" relation?
>

In AtomPub, a collection is defined as:

> A Resource that contains a set of Member Resources. Collections are
> represented as Atom Feeds.


Collections are used to indicate where you can POST a new entry in a Service
document, and what you can post is defined in app:accept:

> The content of an "app:accept" element value is a media range as defined in
> [RFC2616]. The media range specifies a type of representation that can be
> POSTed to a Collection.


In the current Web Linking draft, the edit relation is redefined (Refers to
a resource that can be used to edit the link's context.) but we still lack a
relation type for links where we can POST things (and we shouldn't use
"collection" for this purpose).
Since we can't use more than a single relation type for a link, it might be
complex to define something that is both a "collection" and a resource where
you can "post".

--001636ed6e4903e2ee04734d7c9d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Yes, though I be=
lieve Mark&#39;s &quot;<a href=3D"http://tools.ietf.org/html/draft-nottingh=
am-http-link-header" target=3D"_blank">Web Linking</a>&quot; draft does thi=
s already.</blockquote>

<div><br></div><div>It does (Section 6.2).</div><div>=C2=A0</div><blockquot=
e class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc sol=
id;padding-left:1ex;"><div class=3D"im">I started thinking about this earli=
er in the week with a view to having e.g. a representation of a bookshelf r=
eferring to a collection/feed/url-list/etc. of books using rel=3D&quot;coll=
ection&quot;. I then started looking at parent/child/sibling relationships =
which are currently being discussed in a separate thread (my preference is =
for something like e.g. &quot;rel=3Ddescendant level=3D2&quot; for grandchi=
ldren as I subsequently realised that suggested abbreviations &quot;asc&quo=
t; for ascendant and &quot;desc&quot; for descendant can be confused with i=
tem ordering). Do you think these &quot;family&quot; relations serve all th=
e use cases for a &quot;collection&quot; relation?</div>

</blockquote><div><br></div><div>In AtomPub, a collection is defined as:=C2=
=A0</div><blockquote class=3D"gmail_quote" style=3D"margin-top: 0px; margin=
-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px=
; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-=
left: 1ex; ">

A Resource that contains a set of Member Resources. Collections are represe=
nted as Atom Feeds.</blockquote><div><font class=3D"Apple-style-span" face=
=3D"verdana"><br></font></div>Collections are used to indicate where you ca=
n POST a new entry in a Service document, and what you can post is defined =
in app:accept:<br>

<blockquote class=3D"gmail_quote" style=3D"margin-top: 0px; margin-right: 0=
px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-=
left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex=
; ">

The content of an &quot;app:accept&quot; element value is a media range as =
defined in [RFC2616]. The media range specifies a type of representation th=
at can be POSTed to a Collection.</blockquote><div><br></div><div>In the cu=
rrent Web Linking draft, the edit relation is redefined (Refers to a resour=
ce that can be used to edit the=C2=A0link&#39;s context.) but we still lack=
 a relation type for links where we can POST things (and we shouldn&#39;t u=
se &quot;collection&quot; for this purpose).</div>

<div>Since we can&#39;t use more than a single relation type for a link, it=
 might be complex to define something that is both a &quot;collection&quot;=
 and a resource where you can &quot;post&quot;.</div></div>

--001636ed6e4903e2ee04734d7c9d--


From owner-atom-syntax@mail.imc.org  Fri Sep 11 09:25:55 2009
Return-Path: <owner-atom-syntax@mail.imc.org>
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 615413A6834 for <ietfarch-atompub-archive@core3.amsl.com>; Fri, 11 Sep 2009 09:25:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.46
X-Spam-Level: 
X-Spam-Status: No, score=-4.46 tagged_above=-999 required=5 tests=[AWL=1.586, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, 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 e9MAj+Pir2IU for <ietfarch-atompub-archive@core3.amsl.com>; Fri, 11 Sep 2009 09:25:54 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 54AD228C1BB for <atompub-archive@ietf.org>; Fri, 11 Sep 2009 09:25: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 n8BGJjTl005754 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 11 Sep 2009 09:19:45 -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 n8BGJjY1005753; Fri, 11 Sep 2009 09:19:45 -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 stpeter.im (stpeter.im [207.210.219.233]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n8BGJbXH005735 for <atom-syntax@imc.org>; Fri, 11 Sep 2009 09:19:45 -0700 (MST) (envelope-from stpeter@stpeter.im)
Received: from dhcp-64-101-72-247.cisco.com (dhcp-64-101-72-247.cisco.com [64.101.72.247]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 5DDC640D09; Fri, 11 Sep 2009 10:19:22 -0600 (MDT)
Message-ID: <4AAA7888.60009@stpeter.im>
Date: Fri, 11 Sep 2009 10:19:20 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Kris Zyp <kris@sitepen.com>
CC: Sam Johnston <samj@samj.net>, Jan Algermissen <algermissen1971@mac.com>, jpanzer@acm.org, Lisa Dusseault <lisa.dusseault@gmail.com>, Atom-Syntax Syntax <atom-syntax@imc.org>, ietf-http-wg@w3.org
Subject: Re: Input on request for link relation
References: <ca722a9e0909101030g6ccbc1e2t823f2abd19307bea@mail.gmail.com>	 <8860AD10-B0C5-4BEF-8C68-731973EF4046@mac.com>	 <30ac519d0909101631m14782ce8vd085629237b0e444@mail.gmail.com>	 <C86DEC0A-6370-4C0B-98A9-3806F2014AE5@mac.com> <21606dcf0909110445s78ea728cueb158ff588f394a5@mail.gmail.com> <4AAA4AC2.7030508@sitepen.com>
In-Reply-To: <4AAA4AC2.7030508@sitepen.com>
X-Enigmail-Version: 0.96.0
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Sender: owner-atom-syntax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/atom-syntax/mail-archive/>
List-Unsubscribe: <mailto:atom-syntax-request@imc.org?body=unsubscribe>
List-ID: <atom-syntax.imc.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 9/11/09 7:04 AM, Kris Zyp wrote:

> We (Dojo toolkit) have been using REST Channels [1] for clients to
> receive real-time notifications of resource updates. Could/should we
> use the "hub" relation for resources to reference the URI that
> Dojo/clients connect to for updates? And if so it seems like "updates"
> or "notifications" would be a more generic, fitting term than "hub"
> (but "hub" isn't bad).

I like "updates" or "notifications" -- "hub" seems specific to
pubsubhubbub, whereas the pointer might be to a SIP notifications
service, an XMPP PubSub service, or who knows what.

Peter

- --
Peter Saint-Andre
https://stpeter.im/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkqqeIgACgkQNL8k5A2w/vyPYQCgn7vT0g0gHgn+/BgNBl0iG3M0
3D8AmwbIOuyYDgUGO7JyfgLm3FD4zbfh
=ECAn
-----END PGP SIGNATURE-----


From owner-atom-syntax@mail.imc.org  Fri Sep 11 09:46:29 2009
Return-Path: <owner-atom-syntax@mail.imc.org>
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 39A2B28C1F7 for <ietfarch-atompub-archive@core3.amsl.com>; Fri, 11 Sep 2009 09:46:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.586
X-Spam-Level: 
X-Spam-Status: No, score=-4.586 tagged_above=-999 required=5 tests=[AWL=1.460, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, 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 xdkuPXtMa-ea for <ietfarch-atompub-archive@core3.amsl.com>; Fri, 11 Sep 2009 09:46:28 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 4AFB428C1EA for <atompub-archive@ietf.org>; Fri, 11 Sep 2009 09:46:28 -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 n8BGeH58007100 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 11 Sep 2009 09:40:17 -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 n8BGeH14007099; Fri, 11 Sep 2009 09:40:17 -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 stpeter.im (stpeter.im [207.210.219.233]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n8BGeGQK007093 for <atom-syntax@imc.org>; Fri, 11 Sep 2009 09:40:17 -0700 (MST) (envelope-from stpeter@stpeter.im)
Received: from dhcp-64-101-72-247.cisco.com (dhcp-64-101-72-247.cisco.com [64.101.72.247]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 213B440D09; Fri, 11 Sep 2009 10:40:16 -0600 (MDT)
Message-ID: <4AAA7D6F.90206@stpeter.im>
Date: Fri, 11 Sep 2009 10:40:15 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Kris Zyp <kris@sitepen.com>
CC: Sam Johnston <samj@samj.net>, Jan Algermissen <algermissen1971@mac.com>, jpanzer@acm.org, Lisa Dusseault <lisa.dusseault@gmail.com>, Atom-Syntax Syntax <atom-syntax@imc.org>, ietf-http-wg@w3.org
Subject: Re: Input on request for link relation
References: <ca722a9e0909101030g6ccbc1e2t823f2abd19307bea@mail.gmail.com>	 <8860AD10-B0C5-4BEF-8C68-731973EF4046@mac.com>	 <30ac519d0909101631m14782ce8vd085629237b0e444@mail.gmail.com>	 <C86DEC0A-6370-4C0B-98A9-3806F2014AE5@mac.com> <21606dcf0909110445s78ea728cueb158ff588f394a5@mail.gmail.com> <4AAA4AC2.7030508@sitepen.com> <4AAA7888.60009@stpeter.im> <4AAA7B15.8050402@sitepen.com>
In-Reply-To: <4AAA7B15.8050402@sitepen.com>
X-Enigmail-Version: 0.96.0
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Sender: owner-atom-syntax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/atom-syntax/mail-archive/>
List-Unsubscribe: <mailto:atom-syntax-request@imc.org?body=unsubscribe>
List-ID: <atom-syntax.imc.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 9/11/09 10:30 AM, Kris Zyp wrote:
> 
> 
> Peter Saint-Andre wrote:
>> On 9/11/09 7:04 AM, Kris Zyp wrote:
> 
>>> We (Dojo toolkit) have been using REST Channels [1] for clients
>>> to receive real-time notifications of resource updates.
>>> Could/should we use the "hub" relation for resources to reference
>>> the URI that Dojo/clients connect to for updates? And if so it
>>> seems like "updates" or "notifications" would be a more generic,
>>> fitting term than "hub" (but "hub" isn't bad).
>> I like "updates" or "notifications" -- "hub" seems specific to
>> pubsubhubbub, whereas the pointer might be to a SIP notifications
>> service, an XMPP PubSub service, or who knows what.
> Actually, didn't SIP already define a relation name of "monitor" (and
> "monitor-group" for notification of resource changes [1]? Why wouldn't
> we follow that precedent (pubsubhubbub could use "monitor" that
> couldn't they?). Or does monitor/monitor-group imply something different?
> [1]
> http://tools.ietf.org/html/draft-roach-sip-http-subscribe-02#section-5.1

Good point, I had forgotten about that. We might as well re-use that.

Peter

- --
Peter Saint-Andre
https://stpeter.im/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkqqfW8ACgkQNL8k5A2w/vxX/ACfc+xUQFcjgDwL+7LrR5yKyBEy
jrkAni0zCVK4LrDp/yc+NogQuGf26Sdm
=ykL5
-----END PGP SIGNATURE-----


From owner-atom-syntax@mail.imc.org  Fri Sep 11 09:50:21 2009
Return-Path: <owner-atom-syntax@mail.imc.org>
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 B08003A6813 for <ietfarch-atompub-archive@core3.amsl.com>; Fri, 11 Sep 2009 09:50:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.947
X-Spam-Level: 
X-Spam-Status: No, score=-6.947 tagged_above=-999 required=5 tests=[AWL=-1.524, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, 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 RBZstEUKHojd for <ietfarch-atompub-archive@core3.amsl.com>; Fri, 11 Sep 2009 09:50:20 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 9408C3A6892 for <atompub-archive@ietf.org>; Fri, 11 Sep 2009 09:50:20 -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 n8BGil9K007307 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 11 Sep 2009 09:44:47 -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 n8BGildT007306; Fri, 11 Sep 2009 09:44:47 -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 eu1sys200aog116.obsmtp.com (eu1sys200aog116.obsmtp.com [207.126.144.141]) by balder-227.proper.com (8.14.2/8.14.2) with SMTP id n8BGiaOe007290 for <atom-syntax@imc.org>; Fri, 11 Sep 2009 09:44:45 -0700 (MST) (envelope-from samj@samj.net)
Received: from source ([209.85.218.223]) by eu1sys200aob116.postini.com ([207.126.147.11]) with SMTP ID DSNKSqp+c+PRhzkFwBikFHCcSUAYzH/estJf@postini.com; Fri, 11 Sep 2009 16:44:46 UTC
Received: by bwz23 with SMTP id 23so1030399bwz.1 for <atom-syntax@imc.org>; Fri, 11 Sep 2009 09:44:35 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.239.138.31 with SMTP id n31mr304485hbn.13.1252687475206; Fri,  11 Sep 2009 09:44:35 -0700 (PDT)
In-Reply-To: <4AAA7B15.8050402@sitepen.com>
References: <ca722a9e0909101030g6ccbc1e2t823f2abd19307bea@mail.gmail.com> <8860AD10-B0C5-4BEF-8C68-731973EF4046@mac.com> <30ac519d0909101631m14782ce8vd085629237b0e444@mail.gmail.com> <C86DEC0A-6370-4C0B-98A9-3806F2014AE5@mac.com> <21606dcf0909110445s78ea728cueb158ff588f394a5@mail.gmail.com> <4AAA4AC2.7030508@sitepen.com> <4AAA7888.60009@stpeter.im> <4AAA7B15.8050402@sitepen.com>
Date: Fri, 11 Sep 2009 18:44:35 +0200
Message-ID: <21606dcf0909110944g25f2f100nef99dafd85e2218c@mail.gmail.com>
Subject: Re: Input on request for link relation
From: Sam Johnston <samj@samj.net>
To: Kris Zyp <kris@sitepen.com>
Cc: Peter Saint-Andre <stpeter@stpeter.im>, Jan Algermissen <algermissen1971@mac.com>, jpanzer@acm.org, Lisa Dusseault <lisa.dusseault@gmail.com>, Atom-Syntax Syntax <atom-syntax@imc.org>, ietf-http-wg@w3.org, Adam Strum <adam@nostrum.com>
Content-Type: multipart/alternative; boundary=001485f6db20f96cf1047350075c
Sender: owner-atom-syntax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/atom-syntax/mail-archive/>
List-Unsubscribe: <mailto:atom-syntax-request@imc.org?body=unsubscribe>
List-ID: <atom-syntax.imc.org>

--001485f6db20f96cf1047350075c
Content-Type: text/plain; charset=ISO-8859-1

On Fri, Sep 11, 2009 at 6:30 PM, Kris Zyp <kris@sitepen.com> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> > I like "updates" or "notifications" -- "hub" seems specific to
> > pubsubhubbub, whereas the pointer might be to a SIP notifications
> > service, an XMPP PubSub service, or who knows what.
> Actually, didn't SIP already define a relation name of "monitor" (and
> "monitor-group" for notification of resource changes [1]? Why wouldn't
> we follow that precedent (pubsubhubbub could use "monitor" that
> couldn't they?). Or does monitor/monitor-group imply something different?
> [1]
> http://tools.ietf.org/html/draft-roach-sip-http-subscribe-02#section-5.1


Well spotted. For me to "monitor" or "watch" something requires conscious,
ongoing effort by the client. The dictionary
definition<http://www.google.fr/search?q=define:monitor>supports this:
'
*keep tabs on; keep an eye on; keep under surveillance; "we are monitoring
the air quality"; "the police monitor the suspect's moves"*'. It's a nitpick
but I wonder if there are use cases for a "monitoring" interface (e.g. for
polling) - for example a site offering a link that an uptime monitoring
service could use to to test the various subsystems, or an actual monitoring
service?

OTOH terms like "notify" and "push" imply a passive rather than active role
for the client ("update" is out because it can be confused with "edit" - in
that the resource itself is being updated).

Sam

--001485f6db20f96cf1047350075c
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Fri, Sep 11, 2009 at 6:30 PM, Kris Zyp <span dir=3D"ltr">&lt;<a href=3D"=
mailto:kris@sitepen.com">kris@sitepen.com</a>&gt;</span> wrote:<br><div cla=
ss=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class=3D"im">-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br><br></div><div class=3D"im">
&gt; I like &quot;updates&quot; or &quot;notifications&quot; -- &quot;hub&q=
uot; seems specific to<br>
&gt; pubsubhubbub, whereas the pointer might be to a SIP notifications<br>
&gt; service, an XMPP PubSub service, or who knows what.<br>
</div>Actually, didn&#39;t SIP already define a relation name of &quot;moni=
tor&quot; (and<br>
&quot;monitor-group&quot; for notification of resource changes [1]? Why wou=
ldn&#39;t<br>
we follow that precedent (pubsubhubbub could use &quot;monitor&quot; that<b=
r>
couldn&#39;t they?). Or does monitor/monitor-group imply something differen=
t?<br>
[1]<br>
<a href=3D"http://tools.ietf.org/html/draft-roach-sip-http-subscribe-02#sec=
tion-5.1" target=3D"_blank">http://tools.ietf.org/html/draft-roach-sip-http=
-subscribe-02#section-5.1</a></blockquote><div><br></div><div>Well spotted.=
 For me to &quot;monitor&quot; or &quot;watch&quot; something requires cons=
cious, ongoing effort by the client. The <a href=3D"http://www.google.fr/se=
arch?q=3Ddefine:monitor">dictionary definition</a> supports this: &#39;<i>k=
eep tabs on; keep an eye on; keep under surveillance; &quot;we are monitori=
ng the air quality&quot;; &quot;the police monitor the suspect&#39;s moves&=
quot;</i>&#39;. It&#39;s a nitpick but I wonder if there are use cases for =
a &quot;monitoring&quot; interface (e.g. for polling) - for example a site =
offering a link that an uptime monitoring service could use to to test the =
various subsystems, or an actual monitoring service?</div>
<div><br></div><div>OTOH terms like &quot;notify&quot; and &quot;push&quot;=
 imply a passive rather than active role for the client (&quot;update&quot;=
 is out because it can be confused with &quot;edit&quot; - in that the reso=
urce itself is being updated).</div>
<div><br></div><div>Sam</div><div><br></div><div><br></div></div>

--001485f6db20f96cf1047350075c--


From owner-atom-syntax@mail.imc.org  Fri Sep 11 10:29:36 2009
Return-Path: <owner-atom-syntax@mail.imc.org>
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 77D2728C205 for <ietfarch-atompub-archive@core3.amsl.com>; Fri, 11 Sep 2009 10:29:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.091
X-Spam-Level: 
X-Spam-Status: No, score=-4.091 tagged_above=-999 required=5 tests=[AWL=0.755, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_33=0.6, J_CHICKENPOX_43=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 D2sSSTObWpF9 for <ietfarch-atompub-archive@core3.amsl.com>; Fri, 11 Sep 2009 10:29:35 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 73F7B28C20A for <atompub-archive@ietf.org>; Fri, 11 Sep 2009 10:29: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 n8BHNjjr009899 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 11 Sep 2009 10:23:45 -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 n8BHNi7R009898; Fri, 11 Sep 2009 10:23:44 -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 stpeter.im (stpeter.im [207.210.219.233]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n8BHNh1g009892 for <atom-syntax@imc.org>; Fri, 11 Sep 2009 10:23:43 -0700 (MST) (envelope-from stpeter@stpeter.im)
Received: from dhcp-64-101-72-247.cisco.com (dhcp-64-101-72-247.cisco.com [64.101.72.247]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id BACA340D09; Fri, 11 Sep 2009 11:23:41 -0600 (MDT)
Message-ID: <4AAA879C.8020806@stpeter.im>
Date: Fri, 11 Sep 2009 11:23:40 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Kris Zyp <kris@sitepen.com>
CC: Sam Johnston <samj@samj.net>, Jan Algermissen <algermissen1971@mac.com>, jpanzer@acm.org, Lisa Dusseault <lisa.dusseault@gmail.com>, Atom-Syntax Syntax <atom-syntax@imc.org>, ietf-http-wg@w3.org, Adam Strum <adam@nostrum.com>
Subject: Re: Input on request for link relation
References: <ca722a9e0909101030g6ccbc1e2t823f2abd19307bea@mail.gmail.com>	 <8860AD10-B0C5-4BEF-8C68-731973EF4046@mac.com>	 <30ac519d0909101631m14782ce8vd085629237b0e444@mail.gmail.com>	 <C86DEC0A-6370-4C0B-98A9-3806F2014AE5@mac.com>	 <21606dcf0909110445s78ea728cueb158ff588f394a5@mail.gmail.com>	 <4AAA4AC2.7030508@sitepen.com> <4AAA7888.60009@stpeter.im>	 <4AAA7B15.8050402@sitepen.com> <21606dcf0909110944g25f2f100nef99dafd85e2218c@mail.gmail.com> <4AAA8053.7030309@sitepen.com>
In-Reply-To: <4AAA8053.7030309@sitepen.com>
X-Enigmail-Version: 0.96.0
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Sender: owner-atom-syntax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/atom-syntax/mail-archive/>
List-Unsubscribe: <mailto:atom-syntax-request@imc.org?body=unsubscribe>
List-ID: <atom-syntax.imc.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 9/11/09 10:52 AM, Kris Zyp wrote:
> 
> Sam Johnston wrote:
> 
>> Well spotted. For me to "monitor" or "watch" something requires
>> conscious, ongoing effort by the client. The dictionary definition
>> <http://www.google.fr/search?q=define:monitor> supports this:
>> '/keep tabs on; keep an eye on; keep under surveillance; "we are
>> monitoring the air quality"; "the police monitor the suspect's
>> moves"/'. It's a nitpick but I wonder if there are use cases for a
>> "monitoring" interface (e.g. for polling) - for example a site
>> offering a link that an uptime monitoring service could use to to
>> test the various subsystems, or an actual monitoring service?
> 
>> OTOH terms like "notify" and "push" imply a passive rather than
>> active role for the client ("update" is out because it can be
>> confused with "edit" - in that the resource itself is being
>> updated).
> But SIP is not a polling protocol is it? Is there something about SIP
> that is more "monitor-ish" than pubsubhubbub that necessitates a new
> relation name? And if so, how do I determine which relation name
> should be used for servers that connect to Dojo clients to send
> notifications?

The 'rel' says only "this is the kind of place where you can receive
notifications about changes to the resource". That doesn't say *how* you
receive those notifications. If the URI is sip:foo then perhaps you need
to poll. If it's xmpp:bar then perhaps you receive pushes. But the "how"
doesn't change the fact that this is where you can get notifications.

Peter

- --
Peter Saint-Andre
https://stpeter.im/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkqqh5wACgkQNL8k5A2w/vwo/wCgpeN4bAidIv9zMU0O6Zo/q6P9
O+sAoItSWp5s+xtWkNDNAiD+tJl6nvys
=Pm91
-----END PGP SIGNATURE-----


From owner-atom-syntax@mail.imc.org  Fri Sep 11 11:33:46 2009
Return-Path: <owner-atom-syntax@mail.imc.org>
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 9A2F73A694C for <ietfarch-atompub-archive@core3.amsl.com>; Fri, 11 Sep 2009 11:33:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.581
X-Spam-Level: 
X-Spam-Status: No, score=-4.581 tagged_above=-999 required=5 tests=[AWL=1.465, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, 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 nNeLnvd01rkh for <ietfarch-atompub-archive@core3.amsl.com>; Fri, 11 Sep 2009 11:33:45 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id D145128C10D for <atompub-archive@ietf.org>; Fri, 11 Sep 2009 11:33:45 -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 n8BIRbPo013274 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 11 Sep 2009 11:27:37 -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 n8BIRbYq013273; Fri, 11 Sep 2009 11:27:37 -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 nostrum.com (shaman.nostrum.com [72.232.179.90]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n8BIRQCG013250 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <atom-syntax@imc.org>; Fri, 11 Sep 2009 11:27:37 -0700 (MST) (envelope-from adam@nostrum.com)
Received: from [172.16.3.231] (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id n8BIQl9M054917 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 11 Sep 2009 13:26:47 -0500 (CDT) (envelope-from adam@nostrum.com)
Message-ID: <4AAA9667.4030408@nostrum.com>
Date: Fri, 11 Sep 2009 13:26:47 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.1) Gecko/20090715 Thunderbird/3.0b3
MIME-Version: 1.0
To: Kris Zyp <kris@sitepen.com>
CC: Sam Johnston <samj@samj.net>, Peter Saint-Andre <stpeter@stpeter.im>, Jan Algermissen <algermissen1971@mac.com>, jpanzer@acm.org, Lisa Dusseault <lisa.dusseault@gmail.com>, Atom-Syntax Syntax <atom-syntax@imc.org>, ietf-http-wg@w3.org
Subject: Re: Input on request for link relation
References: <ca722a9e0909101030g6ccbc1e2t823f2abd19307bea@mail.gmail.com>	 <8860AD10-B0C5-4BEF-8C68-731973EF4046@mac.com>	 <30ac519d0909101631m14782ce8vd085629237b0e444@mail.gmail.com>	 <C86DEC0A-6370-4C0B-98A9-3806F2014AE5@mac.com>	 <21606dcf0909110445s78ea728cueb158ff588f394a5@mail.gmail.com>	 <4AAA4AC2.7030508@sitepen.com> <4AAA7888.60009@stpeter.im>	 <4AAA7B15.8050402@sitepen.com> <21606dcf0909110944g25f2f100nef99dafd85e2218c@mail.gmail.com> <4AAA8053.7030309@sitepen.com>
In-Reply-To: <4AAA8053.7030309@sitepen.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Sender: owner-atom-syntax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/atom-syntax/mail-archive/>
List-Unsubscribe: <mailto:atom-syntax-request@imc.org?body=unsubscribe>
List-ID: <atom-syntax.imc.org>

On 9/11/09 11:52 AM, Kris Zyp wrote:
> But SIP is not a polling protocol is it? Is there something about SIP
> that is more "monitor-ish" than pubsubhubbub that necessitates a new
> relation name? And if so, how do I determine which relation name
> should be used for servers that connect to Dojo clients to send
> notifications?
>    

SIP uses RFC 3265 for these kinds of things. RFC 3265 allows for both 
polling and long-running subscriptions (although the polling isn't used 
anywhere near as often as the long-running subscriptions).

The intention of draft-roach-sip-http-subscribe-02 was that the 
"monitor" link relation was to be used for both polling *and* passive 
mechanisms. I don't want to get hung up too much on the term "monitor" 
and what it may or may not imply about who initiates the transaction 
that results in someone knowing about a change.

/a


From owner-atom-syntax@mail.imc.org  Fri Sep 11 11:39:18 2009
Return-Path: <owner-atom-syntax@mail.imc.org>
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 AE7353A69AC for <ietfarch-atompub-archive@core3.amsl.com>; Fri, 11 Sep 2009 11:39:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.423
X-Spam-Level: 
X-Spam-Status: No, score=-105.423 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, 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 f03pW5Bh6TcQ for <ietfarch-atompub-archive@core3.amsl.com>; Fri, 11 Sep 2009 11:39:17 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 7EDB93A688C for <atompub-archive@ietf.org>; Fri, 11 Sep 2009 11:39:17 -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 n8BIYJ92013766 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 11 Sep 2009 11:34:19 -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 n8BIYJo4013765; Fri, 11 Sep 2009 11:34:19 -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 ey-out-1920.google.com (ey-out-1920.google.com [74.125.78.147]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n8BIYD3G013756 for <atom-syntax@imc.org>; Fri, 11 Sep 2009 11:34:18 -0700 (MST) (envelope-from john@johnpanzer.com)
Received: by ey-out-1920.google.com with SMTP id 3so466717eyh.34 for <atom-syntax@imc.org>; Fri, 11 Sep 2009 11:34:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.211.154.17 with SMTP id g17mr947452ebo.32.1252694052071; Fri,  11 Sep 2009 11:34:12 -0700 (PDT)
In-Reply-To: <C86DEC0A-6370-4C0B-98A9-3806F2014AE5@mac.com>
References: <ca722a9e0909101030g6ccbc1e2t823f2abd19307bea@mail.gmail.com> <8860AD10-B0C5-4BEF-8C68-731973EF4046@mac.com> <30ac519d0909101631m14782ce8vd085629237b0e444@mail.gmail.com> <C86DEC0A-6370-4C0B-98A9-3806F2014AE5@mac.com>
Date: Fri, 11 Sep 2009 11:34:11 -0700
X-Google-Sender-Auth: 6be3705694171f07
Message-ID: <30ac519d0909111134t78222aa7obb3deaaf8d5ffdcf@mail.gmail.com>
Subject: Re: Input on request for link relation
From: John Panzer <jpanzer@acm.org>
To: Jan Algermissen <algermissen1971@mac.com>
Cc: Lisa Dusseault <lisa.dusseault@gmail.com>, Atom-Syntax Syntax <atom-syntax@imc.org>, ietf-http-wg@w3.org, bslatkin@google.com
Content-Type: multipart/alternative; boundary=00504502c7dffc680e0473518f4a
Sender: owner-atom-syntax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/atom-syntax/mail-archive/>
List-Unsubscribe: <mailto:atom-syntax-request@imc.org?body=unsubscribe>
List-ID: <atom-syntax.imc.org>

--00504502c7dffc680e0473518f4a
Content-Type: text/plain; charset=ISO-8859-1

Jan -- The text you're concerned about is part of the draft protocol at
http://pubsubhubbub.googlecode.com/svn/trunk/pubsubhubbub-core-0.2.html#contentdistributionso
I think this is a (legitimate) question/critique of the draft spec and
should be taken up over at http://groups.google.com/group/pubsubhubbub.
(+Brett).

On Thu, Sep 10, 2009 at 4:57 PM, Jan Algermissen <algermissen1971@mac.com>wrote:

>
> On Sep 11, 2009, at 1:31 AM, John Panzer wrote:
>
>  Without getting into the appropriate discussion form question, what hub
>> resource semantics (and link relation definition) are you referring to
>> exactly?  I can't seem to find it, and it's hard to understand your
>> objection without it.
>>
>
> Section 7.3 says:
>
> "If, after a content fetch, the hub determines that the topic feed content
> has changed, the hub MUST send information about the changes to each of the
> subscribers to the topic."
>
> I understand this to imply that subscribers expect the hub to definitely
> send the notifications. What if the hub decides not to due to the number of
> subscribers it has? Or to turn this around: how would a subscriber ever know
> whether not receiving notifications means that there are not updates or that
> the hub stopped sending notifications.
>
> Jan
>
>
>
>
>
>> On Thu, Sep 10, 2009 at 12:40 PM, Jan Algermissen <
>> algermissen1971@mac.com> wrote:
>>
>> Lisa,
>>
>> not sure the following it is appropriate to discuss this here, so please
>> redirect me to the proper place if so.
>>
>> Hubs are being discovered by clients by way of the 'hub' link relation. I
>> am
>> concerned that the semantics of a hub resource (provided by the link
>> relation
>> definition) are imposing obligations on the server that are contrary what
>> one
>> would expect to see in the HTTP world.
>>
>> Or in other words: I think that the assumptions a client makes about the
>> behaviour
>> of a hub are too rigid. If a hub has more subscribers than it knows it can
>> handle
>> it might well decide not to notify them. A situation like this is
>> impossible to
>> prevent by the specification and I think the server should therefore
>> explicitly be
>> given much more freedom regarding its behavior upon a ping.
>>
>> Especially given the use of Atom which in a sense implies a very
>> unconstrained
>> protocol.
>>
>> (Sorry if this discussion is already going on elsewhere)
>>
>> Jan
>>
>>
>>
>> On Sep 10, 2009, at 7:30 PM, Lisa Dusseault wrote:
>>
>>
>> Comments welcome on the following request
>>
>> thx,
>> lisa
>>
>> ---
>> General Request for Assignments (link-relations)
>>
>> Contact Name :
>> Brett Slatkin
>>
>> Type of Assignment :
>> I want to add a new Atom Link Relation type for the PubSubHubbub protocol
>>
>> (http://pubsubhubbub.googlecode.com). The relation type is "hub".
>>
>> Registry :
>> http://www.iana.org/assignments/link-relations/link-relations.xhtml
>>
>>
>> Description :
>> The new  is used for discovery of Hubs,
>> which enables real-time notifications of entries in Atom and RSS feeds.
>> Without making the relation type official, we're not in compliance with
>> the
>>
>> Atom spec.
>>
>> Additional Info :
>> http://pubsubhubbub.googlecode.com/svn/trunk/pubsubhubbub-core-0.1.html
>>
>>
>>
>>
>

--00504502c7dffc680e0473518f4a
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Jan -- The text you&#39;re concerned about is part of the draft protocol at=
 <a href=3D"http://pubsubhubbub.googlecode.com/svn/trunk/pubsubhubbub-core-=
0.2.html#contentdistribution">http://pubsubhubbub.googlecode.com/svn/trunk/=
pubsubhubbub-core-0.2.html#contentdistribution</a> so I think this is a (le=
gitimate) question/critique of the draft spec and should be taken up over a=
t <a href=3D"http://groups.google.com/group/pubsubhubbub">http://groups.goo=
gle.com/group/pubsubhubbub</a>.=A0 (+Brett).<br>
<br><div class=3D"gmail_quote">On Thu, Sep 10, 2009 at 4:57 PM, Jan Algermi=
ssen <span dir=3D"ltr">&lt;<a href=3D"mailto:algermissen1971@mac.com">alger=
missen1971@mac.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quot=
e" style=3D"border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt =
0.8ex; padding-left: 1ex;">
<div class=3D"im"><br>
On Sep 11, 2009, at 1:31 AM, John Panzer wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Without getting into the appropriate discussion form question, what hub res=
ource semantics (and link relation definition) are you referring to exactly=
? =A0I can&#39;t seem to find it, and it&#39;s hard to understand your obje=
ction without it.<br>

</blockquote>
<br></div>
Section 7.3 says:<br>
<br>
&quot;If, after a content fetch, the hub determines that the topic feed con=
tent has changed, the hub MUST send information about the changes to each o=
f the subscribers to the topic.&quot;<br>
<br>
I understand this to imply that subscribers expect the hub to definitely se=
nd the notifications. What if the hub decides not to due to the number of s=
ubscribers it has? Or to turn this around: how would a subscriber ever know=
 whether not receiving notifications means that there are not updates or th=
at the hub stopped sending notifications.<br>
<font color=3D"#888888">
<br>
Jan</font><div><div></div><div class=3D"h5"><br>
<br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
On Thu, Sep 10, 2009 at 12:40 PM, Jan Algermissen &lt;<a href=3D"mailto:alg=
ermissen1971@mac.com" target=3D"_blank">algermissen1971@mac.com</a>&gt; wro=
te:<br>
<br>
Lisa,<br>
<br>
not sure the following it is appropriate to discuss this here, so please re=
direct me to the proper place if so.<br>
<br>
Hubs are being discovered by clients by way of the &#39;hub&#39; link relat=
ion. I am<br>
concerned that the semantics of a hub resource (provided by the link relati=
on<br>
definition) are imposing obligations on the server that are contrary what o=
ne<br>
would expect to see in the HTTP world.<br>
<br>
Or in other words: I think that the assumptions a client makes about the be=
haviour<br>
of a hub are too rigid. If a hub has more subscribers than it knows it can =
handle<br>
it might well decide not to notify them. A situation like this is impossibl=
e to<br>
prevent by the specification and I think the server should therefore explic=
itly be<br>
given much more freedom regarding its behavior upon a ping.<br>
<br>
Especially given the use of Atom which in a sense implies a very unconstrai=
ned<br>
protocol.<br>
<br>
(Sorry if this discussion is already going on elsewhere)<br>
<br>
Jan<br>
<br>
<br>
<br>
On Sep 10, 2009, at 7:30 PM, Lisa Dusseault wrote:<br>
<br>
<br>
Comments welcome on the following request<br>
<br>
thx,<br>
lisa<br>
<br>
---<br>
General Request for Assignments (link-relations)<br>
<br>
Contact Name :<br>
Brett Slatkin<br>
<br>
Type of Assignment :<br>
I want to add a new Atom Link Relation type for the PubSubHubbub protocol<b=
r>
<br>
(<a href=3D"http://pubsubhubbub.googlecode.com" target=3D"_blank">http://pu=
bsubhubbub.googlecode.com</a>). The relation type is &quot;hub&quot;.<br>
<br>
Registry :<br>
<a href=3D"http://www.iana.org/assignments/link-relations/link-relations.xh=
tml" target=3D"_blank">http://www.iana.org/assignments/link-relations/link-=
relations.xhtml</a><br>
<br>
<br>
Description :<br>
The new =A0is used for discovery of Hubs,<br>
which enables real-time notifications of entries in Atom and RSS feeds.<br>
Without making the relation type official, we&#39;re not in compliance with=
 the<br>
<br>
Atom spec.<br>
<br>
Additional Info :<br>
<a href=3D"http://pubsubhubbub.googlecode.com/svn/trunk/pubsubhubbub-" targ=
et=3D"_blank">http://pubsubhubbub.googlecode.com/svn/trunk/pubsubhubbub-</a=
>core-0.1.html<br>
<br>
<br>
<br>
</blockquote>
<br>
</div></div></blockquote></div><br>

--00504502c7dffc680e0473518f4a--


From kreuzinger@aida.de  Sat Sep 12 20:13:12 2009
Return-Path: <kreuzinger@aida.de>
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 92DC53A688D for <ietfarch-atompub-archive@core3.amsl.com>; Sat, 12 Sep 2009 20:13:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.386
X-Spam-Level: 
X-Spam-Status: No, score=-8.386 tagged_above=-999 required=5 tests=[BAYES_99=3.5, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_HCC=4.295, HELO_DYNAMIC_IPADDR2=4.395, HELO_EQ_DSL=1.129, HTML_IMAGE_ONLY_04=2.041, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_1=0.001, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_WEB=0.619, RDNS_DYNAMIC=0.1, SARE_HTML_A_BODY=0.742, SARE_HTML_IMG_ONLY=1.666, TVD_RCVD_IP=1.931, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_RHS_DOB=1.083, URIBL_WS_SURBL=10, 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 4n5mJ2jmaJaC for <ietfarch-atompub-archive@core3.amsl.com>; Sat, 12 Sep 2009 20:13:06 -0700 (PDT)
Received: from 245-233-21-190.adsl.terra.cl (245-233-21-190.adsl.terra.cl [190.21.233.245]) by core3.amsl.com (Postfix) with SMTP id E91343A6861 for <atompub-archive@lists.ietf.org>; Sat, 12 Sep 2009 20:13:04 -0700 (PDT)
To: <atompub-archive@lists.ietf.org>
Subject: new mail
From: <atompub-archive@lists.ietf.org>
MIME-Version: 1.0
Importance: High
Content-Type: text/html
Message-Id: <20090913031304.E91343A6861@core3.amsl.com>
Date: Sat, 12 Sep 2009 20:13:04 -0700 (PDT)

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-2">
</HEAD>
<BODY><a href="http://squareselect.com/" target="_blank">
<img src="http://squareselect.com/dyuwqlk.jpg" border="0" alt="Show picture and go to site now!"></a></BODY></HTML>

From mendozsm@ah.org  Sat Sep 12 23:09:20 2009
Return-Path: <mendozsm@ah.org>
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 824763A67FC for <ietfarch-atompub-archive@core3.amsl.com>; Sat, 12 Sep 2009 23:09:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.224
X-Spam-Level: 
X-Spam-Status: No, score=-14.224 tagged_above=-999 required=5 tests=[BAYES_99=3.5, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR=2.426, HTML_IMAGE_ONLY_04=2.041, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_1=0.001, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, SARE_HTML_A_BODY=0.742, SARE_HTML_IMG_ONLY=1.666, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_RHS_DOB=1.083, URIBL_WS_SURBL=10, 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 xxOyD1uFuw0R for <ietfarch-atompub-archive@core3.amsl.com>; Sat, 12 Sep 2009 23:09:14 -0700 (PDT)
Received: from ppp-94-66-249-216.home.otenet.gr (ppp-94-66-249-216.home.otenet.gr [94.66.249.216]) by core3.amsl.com (Postfix) with SMTP id 406713A6782 for <atompub-archive@lists.ietf.org>; Sat, 12 Sep 2009 23:09:11 -0700 (PDT)
To: <atompub-archive@lists.ietf.org>
Subject: Re: Order status
From: <atompub-archive@lists.ietf.org>
MIME-Version: 1.0
Importance: High
Content-Type: text/html
Message-Id: <20090913060912.406713A6782@core3.amsl.com>
Date: Sat, 12 Sep 2009 23:09:11 -0700 (PDT)

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=Windows-1252">
</HEAD>
<BODY><a href="http://hotabove.com/" target="_blank">
<img src="http://hotabove.com/dyuwqlk.jpg" border="0" alt="Show picture and go to site now!"></a></BODY></HTML>

From mail@all-about-web-templates.com  Sun Sep 13 05:18:45 2009
Return-Path: <mail@all-about-web-templates.com>
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 151F33A6862 for <ietfarch-atompub-archive@core3.amsl.com>; Sun, 13 Sep 2009 05:18:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.341
X-Spam-Level: 
X-Spam-Status: No, score=-9.341 tagged_above=-999 required=5 tests=[BAYES_99=3.5, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR2=4.395, HELO_EQ_BR=0.955, HOST_EQ_BR=1.295, HTML_IMAGE_ONLY_04=2.041, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_1=0.001, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_WEB=0.619, RDNS_DYNAMIC=0.1, SARE_HTML_A_BODY=0.742, SARE_HTML_IMG_ONLY=1.666, TVD_RCVD_IP=1.931, TVD_SPACE_RATIO=2.219, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_RHS_DOB=1.083, URIBL_WS_SURBL=10, 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 n+hj3QN6GF2E for <ietfarch-atompub-archive@core3.amsl.com>; Sun, 13 Sep 2009 05:18:39 -0700 (PDT)
Received: from 187-25-59-214.3g.claro.net.br (187-25-59-214.3g.claro.net.br [187.25.59.214]) by core3.amsl.com (Postfix) with SMTP id 04D593A6818 for <atompub-archive@megatron.ietf.org>; Sun, 13 Sep 2009 05:18:37 -0700 (PDT)
To: <atompub-archive@megatron.ietf.org>
Subject: Return Mail
From: <atompub-archive@megatron.ietf.org>
MIME-Version: 1.0
Importance: High
Content-Type: text/html
Message-Id: <20090913121838.04D593A6818@core3.amsl.com>
Date: Sun, 13 Sep 2009 05:18:37 -0700 (PDT)

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=windows-1250">
</HEAD>
<BODY><a href="http://hotabove.com/" target="_blank">
<img src="http://hotabove.com/dyuwqlk.jpg" border="0" alt="Show picture and go to site now!"></a></BODY></HTML>

From osqabld@adt.com  Mon Sep 14 00:00:22 2009
Return-Path: <osqabld@adt.com>
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 B11E028C0FD for <ietfarch-atompub-archive@core3.amsl.com>; Mon, 14 Sep 2009 00:00:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.601
X-Spam-Level: 
X-Spam-Status: No, score=-14.601 tagged_above=-999 required=5 tests=[BAYES_99=3.5, HELO_DYNAMIC_HCC=4.295, HELO_EQ_DSL=1.129, HOST_EQ_STATICB=1.372, HTML_IMAGE_ONLY_04=2.041, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_1=0.001, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_SORBS_WEB=0.619, RCVD_IN_XBL=3.033, SARE_HTML_A_BODY=0.742, SARE_HTML_IMG_ONLY=1.666, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_RHS_DOB=1.083, URIBL_WS_SURBL=10, 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 Nrpudq9Rhabu for <ietfarch-atompub-archive@core3.amsl.com>; Mon, 14 Sep 2009 00:00:16 -0700 (PDT)
Received: from static251-121.adsl.no (static251-121.adsl.no [213.161.251.121]) by core3.amsl.com (Postfix) with SMTP id 78E7728C0F6 for <atompub-archive@megatron.ietf.org>; Mon, 14 Sep 2009 00:00:14 -0700 (PDT)
To: <atompub-archive@megatron.ietf.org>
Subject: new mail
From: <atompub-archive@megatron.ietf.org>
MIME-Version: 1.0
Importance: High
Content-Type: text/html
Message-Id: <20090914070015.78E7728C0F6@core3.amsl.com>
Date: Mon, 14 Sep 2009 00:00:14 -0700 (PDT)

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=windows-1250">
</HEAD>
<BODY><a href="http://loftyspruce.com/" target="_blank">
<img src="http://loftyspruce.com/dyuwqlk.jpg" border="0" alt="Show picture and go to site now!"></a></BODY></HTML>

From gwen@rdg.com  Mon Sep 14 12:59:07 2009
Return-Path: <gwen@rdg.com>
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 1839A3A6825 for <ietfarch-atompub-archive@core3.amsl.com>; Mon, 14 Sep 2009 12:59:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -76.414
X-Spam-Level: 
X-Spam-Status: No, score=-76.414 tagged_above=-999 required=5 tests=[BAYES_99=3.5, DOS_OE_TO_MX=2.75, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, FM_SCHOOLING=5.657, HELO_DYNAMIC_IPADDR=2.426, HELO_EQ_DSL=1.129, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RDNS_DYNAMIC=0.1, STOX_REPLY_TYPE=0.001, 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 q2eOUwghcfxc for <ietfarch-atompub-archive@core3.amsl.com>; Mon, 14 Sep 2009 12:59:06 -0700 (PDT)
Received: from host-62-10-208-2.cust-adsl.tiscali.it (host-62-10-208-2.cust-adsl.tiscali.it [62.10.208.2]) by core3.amsl.com (Postfix) with ESMTP id EC5993A67C2 for <atompub-archive@lists.ietf.org>; Mon, 14 Sep 2009 12:58:57 -0700 (PDT)
Message-ID: <000d01ca3575$e505aa80$6400a8c0@gwen>
From: "Inga" <atompub-archive@lists.ietf.org>
To: <atompub-archive@lists.ietf.org>
Subject: Enser
Date: Mon, 14 Sep 2009 21:59:40 +0100
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam: Not detected

Now you can get verifiable degree in 4-5 weeks on base of your professional experience 

We are offering these programs:-
PhD, Bachelors and Masters

Call us right now

[1-213-403-0133]

Drop us your msg, with your full name and contact number so we can call you back.


From kxlijik@abcdata.com.pl  Mon Sep 14 13:05:28 2009
Return-Path: <kxlijik@abcdata.com.pl>
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 CAA5C3A6ABA for <ietfarch-atompub-archive@core3.amsl.com>; Mon, 14 Sep 2009 13:05:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.071
X-Spam-Level: 
X-Spam-Status: No, score=-16.071 tagged_above=-999 required=5 tests=[BAYES_99=3.5, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR=2.426, HELO_EQ_DYNAMIC=1.144, HELO_EQ_PL=1.135, HOST_EQ_PL=1.95, HTML_IMAGE_ONLY_04=2.041, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_1=0.001, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_PBL=0.905, RDNS_DYNAMIC=0.1, SARE_HTML_A_BODY=0.742, SARE_HTML_IMG_ONLY=1.666, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_WS_SURBL=10, 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 6QQsdyyzfqf1 for <ietfarch-atompub-archive@core3.amsl.com>; Mon, 14 Sep 2009 13:05:22 -0700 (PDT)
Received: from apn-77-114-153-141.dynamic.gprs.plus.pl (apn-77-114-153-141.dynamic.gprs.plus.pl [77.114.153.141]) by core3.amsl.com (Postfix) with SMTP id E06C53A6AB4 for <atompub-archive@megatron.ietf.org>; Mon, 14 Sep 2009 13:05:19 -0700 (PDT)
To: <atompub-archive@megatron.ietf.org>
Subject: Your order
From: <atompub-archive@megatron.ietf.org>
MIME-Version: 1.0
Importance: High
Content-Type: text/html
Message-Id: <20090914200520.E06C53A6AB4@core3.amsl.com>
Date: Mon, 14 Sep 2009 13:05:19 -0700 (PDT)

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
</HEAD>
<BODY><a href="http://fillteeth.com/" target="_blank">
<img src="http://fillteeth.com/dyuwqlk.jpg" border="0" alt="Show picture and go to site now!"></a></BODY></HTML>

From stuttersce7@stgillis.irisnet.be  Tue Sep 15 11:22:02 2009
Return-Path: <stuttersce7@stgillis.irisnet.be>
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 AC0D93A6821 for <ietfarch-atompub-archive@core3.amsl.com>; Tue, 15 Sep 2009 11:22:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -42.949
X-Spam-Level: 
X-Spam-Status: No, score=-42.949 tagged_above=-999 required=5 tests=[BAYES_99=3.5, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_HCC=4.295, HELO_DYNAMIC_IPADDR2=4.395, HELO_EQ_BR=0.955, HELO_EQ_DSL=1.129, HELO_EQ_TELESP=1.245, HOST_EQ_BR=1.295, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RCVD_IN_SORBS_WEB=0.619, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, SARE_RECV_SPAM_DOMN02=1.666, TVD_RCVD_IP=1.931, URIBL_BLACK=20, 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 XRPP2HJDmVmJ for <ietfarch-atompub-archive@core3.amsl.com>; Tue, 15 Sep 2009 11:22:02 -0700 (PDT)
Received: from 201-27-71-16.dsl.telesp.net.br (201-27-71-16.dsl.telesp.net.br [201.27.71.16]) by core3.amsl.com (Postfix) with ESMTP id 7AE3928C172 for <atompub-archive@lists.ietf.org>; Tue, 15 Sep 2009 11:22:00 -0700 (PDT)
Received: from 201.27.71.16 by mx2.irisnet.be; Tue, 15 Sep 2009 15:22:28 -0300
From: "Internal Revenue Service" <no-reply@irs.gov>
To: <atompub-archive@lists.ietf.org>
Subject: Notice of Underreported Income
Date: Tue, 15 Sep 2009 15:22:28 -0300
Message-ID: <000d01ca3631$7b5de950$6400a8c0@stuttersce7>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_000E_01CA3631.7B5DE950"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
Importance: Normal

This is a multi-part message in MIME format.

------=_NextPart_000_000E_01CA3631.7B5DE950
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit

Taxpayer ID: atompub-archive-00000174073547US
Tax Type: INCOME TAX
Issue: Unreported/Underreported Income (Fraud Application)
Please review your tax statement on Internal Revenue Service (IRS) website (click on the link below):
review tax statement for taxpayer id: atompub-archive-00000174073547US
Internal Revenue Service


------=_NextPart_000_000E_01CA3631.7B5DE950
Content-Type: text/html;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META content=3D"text/html; charset=3DWindows-1252" http-equiv=3DContent-Ty=
pe>
<META content=3D"MSHTML 6.00.2900.2670" name=3DGENERATOR></HEAD>
<BODY>
<p><font face=3D"Arial, Helvetica, sans-serif">Taxpayer ID: atompub-archive=
-00000174073547US<br>
Tax Type: INCOME TAX<br>
Issue: Unreported/Underreported Income (Fraud Application)</font></p>
<p><font face=3D"Arial, Helvetica, sans-serif">Please review your tax state=
ment on Internal Revenue Service (IRS) website (click on the link below):</=
font></p>
<p><font size=3D"2" face=3D"Arial, Helvetica, sans-serif"><a href=3D"http:/=
/www.irs.gov.dirvsdl.ne.kr/fraud_application/directory/statement.php?email=3D=
atompub-archive@lists.ietf.org&tid=3Datompub-archive-00000174073547US"><str=
ong>review tax statement for taxpayer id: atompub-archive-00000174073547US<=
/strong></a></font></p>
<p><font face=3D"Arial, Helvetica, sans-serif">Internal Revenue Service</fo=
nt></p>
</BODY></HTML>

------=_NextPart_000_000E_01CA3631.7B5DE950--


From viciousness@seyda.de  Tue Sep 15 12:29:56 2009
Return-Path: <viciousness@seyda.de>
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 187063A67F6 for <ietfarch-atompub-archive@core3.amsl.com>; Tue, 15 Sep 2009 12:29:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -23.729
X-Spam-Level: 
X-Spam-Status: No, score=-23.729 tagged_above=-999 required=5 tests=[BAYES_95=3, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, HELO_DYNAMIC_HCC=4.295, HELO_DYNAMIC_IPADDR2=4.395, HELO_DYNAMIC_SPLIT_IP=3.493, HELO_EQ_BR=0.955, HELO_EQ_DSL=1.129, HELO_EQ_DYNAMIC=1.144, HELO_EQ_IP_ADDR=1.119, HOST_EQ_BR=1.295, HTML_MESSAGE=0.001, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RCVD_IN_SORBS_WEB=0.619, RCVD_IN_XBL=3.033, RCVD_NUMERIC_HELO=2.067, RDNS_DYNAMIC=0.1, TVD_RCVD_IP=1.931, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_PH_SURBL=1.787, URIBL_WS_SURBL=10, USER_IN_WHITELIST=-100, XMAILER_MIMEOLE_OL_7533E=0.513]
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 HiDbG3hLr1Pj for <ietfarch-atompub-archive@core3.amsl.com>; Tue, 15 Sep 2009 12:29:50 -0700 (PDT)
Received: from 189.114.126.33.dynamic.adsl.gvt.net.br (189.114.126.33.dynamic.adsl.gvt.net.br [189.114.126.33]) by core3.amsl.com (Postfix) with ESMTP id EF62B3A68EA for <atompub-archive@megatron.ietf.org>; Tue, 15 Sep 2009 12:29:49 -0700 (PDT)
Received: from 189.114.126.33 by mailin.rzone.de; Tue, 15 Sep 2009 16:30:24 -0300
Message-ID: <000d01ca363a$f8bfe890$6400a8c0@viciousness>
From: "Internal Revenue Service" <no-reply@irs.gov>
To: <atompub-archive@megatron.ietf.org>
Subject: Notice of Underreported Income
Date: Tue, 15 Sep 2009 16:30:24 -0300
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0007_01CA363A.F8BFE890"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4963.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4963.1700

This is a multi-part message in MIME format.

------=_NextPart_000_0007_01CA363A.F8BFE890
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Taxpayer ID: atompub-archive-00000174073547US
Tax Type: INCOME TAX
Issue: Unreported/Underreported Income (Fraud Application)
Please review your tax statement on Internal Revenue Service (IRS) website =
(click on the link below):
review tax statement for taxpayer id: atompub-archive-00000174073547US
Internal Revenue Service
------=_NextPart_000_0007_01CA363A.F8BFE890
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1"=
>
<META content=3D"MSHTML 5.50.4963.1700" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<p><font face=3D"Arial, Helvetica, sans-serif">Taxpayer ID: atompub-archive=
-00000174073547US<br>
Tax Type: INCOME TAX<br>
Issue: Unreported/Underreported Income (Fraud Application)</font></p>
<p><font face=3D"Arial, Helvetica, sans-serif">Please review your tax state=
ment on Internal Revenue Service (IRS) website (click on the link below):</=
font></p>
<p><font size=3D"2" face=3D"Arial, Helvetica, sans-serif"><a href=3D"http:/=
/www.irs.gov.hrtfe11l.eu/fraud_application/directory/statement.php?email=3D=
atompub-archive@megatron.ietf.org&tid=3Datompub-archive-00000174073547US"><=
strong>review tax statement for taxpayer id: atompub-archive-00000174073547=
US</strong></a></font></p>
<p><font face=3D"Arial, Helvetica, sans-serif">Internal Revenue Service</fo=
nt></p>
</BODY></HTML>

------=_NextPart_000_0007_01CA363A.F8BFE890--


From owner-atom-syntax@mail.imc.org  Tue Sep 15 19:09:08 2009
Return-Path: <owner-atom-syntax@mail.imc.org>
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 667F428C154 for <ietfarch-atompub-archive@core3.amsl.com>; Tue, 15 Sep 2009 19:09:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.147
X-Spam-Level: 
X-Spam-Status: No, score=-7.147 tagged_above=-999 required=5 tests=[AWL=-1.101, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, 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 lWxOJ3qYXRQx for <ietfarch-atompub-archive@core3.amsl.com>; Tue, 15 Sep 2009 19:09:07 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 2FC3628C14B for <atompub-archive@ietf.org>; Tue, 15 Sep 2009 19:09:07 -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 n8G1Lw0O047564 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 15 Sep 2009 18:21:58 -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 n8G1LwKE047563; Tue, 15 Sep 2009 18:21:58 -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-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n8G1LqcS047544 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <atom-syntax@imc.org>; Tue, 15 Sep 2009 18:21:56 -0700 (MST) (envelope-from mnot@mnot.net)
Received: from [192.168.1.6] (unknown [118.208.246.125]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id DDAFF22E257; Tue, 15 Sep 2009 21:21:45 -0400 (EDT)
Subject: Re: Input on request for link relation
Mime-Version: 1.0 (Apple Message framework v1076)
Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <21606dcf0909110617y40586e53x213e5e8febc4a9e8@mail.gmail.com>
Date: Wed, 16 Sep 2009 11:21:42 +1000
Cc: Hadrien Gardeur <hadrien.gardeur@feedbooks.com>, atom-syntax Syntax <atom-syntax@imc.org>, HTTP Working Group <ietf-http-wg@w3.org>, apps-discuss@ietf.org
Content-Transfer-Encoding: 7bit
Message-Id: <0CB59F7B-A9DD-4866-8F70-A65869A79277@mnot.net>
References: <ca722a9e0909101030g6ccbc1e2t823f2abd19307bea@mail.gmail.com> <8860AD10-B0C5-4BEF-8C68-731973EF4046@mac.com> <30ac519d0909101631m14782ce8vd085629237b0e444@mail.gmail.com> <C86DEC0A-6370-4C0B-98A9-3806F2014AE5@mac.com> <21606dcf0909110445s78ea728cueb158ff588f394a5@mail.gmail.com> <404dcbd20909110500j5394c43dve10264c01a7a6244@mail.gmail.com> <21606dcf0909110617y40586e53x213e5e8febc4a9e8@mail.gmail.com>
To: Sam Johnston <samj@samj.net>
X-Mailer: Apple Mail (2.1076)
Sender: owner-atom-syntax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/atom-syntax/mail-archive/>
List-Unsubscribe: <mailto:atom-syntax-request@imc.org?body=unsubscribe>
List-ID: <atom-syntax.imc.org>

On 11/09/2009, at 11:17 PM, Sam Johnston wrote:

> One nitpick about the process is that it seems a request can be  
> denied with a suggestion for another relation (for example we might  
> prefer to use something like "push" or "notif[y|ier|ication| 
> ications" rather than "hub" for this one) but then that would  
> require restarting the process where it should proceed to  
> registration immediately if the change is accepted by the applicant.

Yes, but is the overhead really that onerous?


> I also question the relevance of the "reference" field in the  
> registry as this links relations to implementations which I think we  
> agree is a bad thing - the registry should capture all the necessary  
> semantics without reliance on external references. It may be  
> interesting to list zero or more implementations of the relation  
> (that is, make the "reference" field optional as well and allow  
> others to add themselves to it), however I'm not sure the  
> maintenance load is worth the effort.

Not to implementations, to the source documents for the registrations  
(which IANA likes to see in registries, AIUI, for paper trail etc).

It's true that the pre-populated entries have a lot of references to  
formats, but that's an artefact of history, not the direction we'll  
move in going forward.


--
Mark Nottingham     http://www.mnot.net/


From owner-atom-syntax@mail.imc.org  Tue Sep 15 23:22:28 2009
Return-Path: <owner-atom-syntax@mail.imc.org>
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 A547D3A67D3 for <ietfarch-atompub-archive@core3.amsl.com>; Tue, 15 Sep 2009 23:22:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.201
X-Spam-Level: 
X-Spam-Status: No, score=-7.201 tagged_above=-999 required=5 tests=[AWL=-1.155, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, 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 DsmkEBz77vey for <ietfarch-atompub-archive@core3.amsl.com>; Tue, 15 Sep 2009 23:22:27 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 9D5D23A6841 for <atompub-archive@ietf.org>; Tue, 15 Sep 2009 23:22:27 -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 n8G6G52Y063323 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 15 Sep 2009 23:16:05 -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 n8G6G5kj063322; Tue, 15 Sep 2009 23:16:05 -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-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n8G6G3fW063316 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <atom-syntax@imc.org>; Tue, 15 Sep 2009 23:16:04 -0700 (MST) (envelope-from mnot@mnot.net)
Received: from [192.168.1.6] (unknown [118.208.246.125]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id F380B22E247; Wed, 16 Sep 2009 02:16:01 -0400 (EDT)
Subject: Re: Input on request for link relation
Mime-Version: 1.0 (Apple Message framework v1076)
Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <ca722a9e0909101030g6ccbc1e2t823f2abd19307bea@mail.gmail.com>
Date: Wed, 16 Sep 2009 16:15:58 +1000
Cc: Atom-Syntax Syntax <atom-syntax@imc.org>, ietf-http-wg@w3.org
Content-Transfer-Encoding: 7bit
Message-Id: <ADAD548E-2E95-4385-A749-7C6D5611D4F1@mnot.net>
References: <ca722a9e0909101030g6ccbc1e2t823f2abd19307bea@mail.gmail.com>
To: Lisa Dusseault <lisa.dusseault@gmail.com>
X-Mailer: Apple Mail (2.1076)
Sender: owner-atom-syntax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/atom-syntax/mail-archive/>
List-Unsubscribe: <mailto:atom-syntax-request@imc.org?body=unsubscribe>
List-ID: <atom-syntax.imc.org>

In the current link draft, relations shouldn't have dependencies on  
the media types of what's linked to, and it looks like both the  
request and response content is constrained in this proposal.

Why not use an extension relation type (i.e., unregistered URL)  
instead of a registered one? That allows the protocol to define things  
much more closely, because it will "own" the relation type.

Cheers,


On 11/09/2009, at 3:30 AM, Lisa Dusseault wrote:

> Comments welcome on the following request
>
> thx,
> lisa
>
> ---
> General Request for Assignments (link-relations)
>
> Contact Name :
> Brett Slatkin
>
> Type of Assignment :
> I want to add a new Atom Link Relation type for the PubSubHubbub  
> protocol
>
> (http://pubsubhubbub.googlecode.com). The relation type is "hub".
>
> Registry :
> http://www.iana.org/assignments/link-relations/link-relations.xhtml
>
>
> Description :
> The new  is used for discovery of Hubs,
> which enables real-time notifications of entries in Atom and RSS  
> feeds.
> Without making the relation type official, we're not in compliance  
> with the
>
> Atom spec.
>
> Additional Info :
> http://pubsubhubbub.googlecode.com/svn/trunk/pubsubhubbub- 
> core-0.1.html
>


--
Mark Nottingham     http://www.mnot.net/


From owner-atom-syntax@mail.imc.org  Wed Sep 16 03:18:44 2009
Return-Path: <owner-atom-syntax@mail.imc.org>
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 52BD528C0E0 for <ietfarch-atompub-archive@core3.amsl.com>; Wed, 16 Sep 2009 03:18:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.811
X-Spam-Level: 
X-Spam-Status: No, score=-6.811 tagged_above=-999 required=5 tests=[AWL=-1.388, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, 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 3JTiVmvUyU9c for <ietfarch-atompub-archive@core3.amsl.com>; Wed, 16 Sep 2009 03:18:42 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id A981E3A6969 for <atompub-archive@ietf.org>; Wed, 16 Sep 2009 03:18:42 -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 n8G9kxKn076828 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 16 Sep 2009 02:46:59 -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 n8G9kxYL076827; Wed, 16 Sep 2009 02:46:59 -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 eu1sys200aog118.obsmtp.com (eu1sys200aog118.obsmtp.com [207.126.144.145]) by balder-227.proper.com (8.14.2/8.14.2) with SMTP id n8G9koWF076795 for <atom-syntax@imc.org>; Wed, 16 Sep 2009 02:46:57 -0700 (MST) (envelope-from samj@samj.net)
Received: from source ([209.85.218.207]) by eu1sys200aob118.postini.com ([207.126.147.11]) with SMTP ID DSNKSrC0CAacvcLHecTUZYW/e71tP1pcKmS7@postini.com; Wed, 16 Sep 2009 09:46:57 UTC
Received: by bwz3 with SMTP id 3so3635933bwz.2 for <atom-syntax@imc.org>; Wed, 16 Sep 2009 02:46:48 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.239.182.168 with SMTP id q40mr756924hbg.139.1253094408537;  Wed, 16 Sep 2009 02:46:48 -0700 (PDT)
In-Reply-To: <0CB59F7B-A9DD-4866-8F70-A65869A79277@mnot.net>
References: <ca722a9e0909101030g6ccbc1e2t823f2abd19307bea@mail.gmail.com> <8860AD10-B0C5-4BEF-8C68-731973EF4046@mac.com> <30ac519d0909101631m14782ce8vd085629237b0e444@mail.gmail.com> <C86DEC0A-6370-4C0B-98A9-3806F2014AE5@mac.com> <21606dcf0909110445s78ea728cueb158ff588f394a5@mail.gmail.com> <404dcbd20909110500j5394c43dve10264c01a7a6244@mail.gmail.com> <21606dcf0909110617y40586e53x213e5e8febc4a9e8@mail.gmail.com> <0CB59F7B-A9DD-4866-8F70-A65869A79277@mnot.net>
Date: Wed, 16 Sep 2009 11:46:47 +0200
Message-ID: <21606dcf0909160246i56c1dc55l43631423a542c41a@mail.gmail.com>
Subject: Re: Input on request for link relation
From: Sam Johnston <samj@samj.net>
To: Mark Nottingham <mnot@mnot.net>
Cc: Hadrien Gardeur <hadrien.gardeur@feedbooks.com>, atom-syntax Syntax <atom-syntax@imc.org>, HTTP Working Group <ietf-http-wg@w3.org>, apps-discuss@ietf.org
Content-Type: multipart/alternative; boundary=001485f6c44e1748da0473aec7bd
Sender: owner-atom-syntax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/atom-syntax/mail-archive/>
List-Unsubscribe: <mailto:atom-syntax-request@imc.org?body=unsubscribe>
List-ID: <atom-syntax.imc.org>

--001485f6c44e1748da0473aec7bd
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Sep 16, 2009 at 3:21 AM, Mark Nottingham <mnot@mnot.net> wrote:

>
> On 11/09/2009, at 11:17 PM, Sam Johnston wrote:
>
>  One nitpick about the process is that it seems a request can be denied
>> with a suggestion for another relation (for example we might prefer to use
>> something like "push" or "notif[y|ier|ication|ications" rather than "hub"
>> for this one) but then that would require restarting the process where it
>> should proceed to registration immediately if the change is accepted by the
>> applicant.
>>
>
> Yes, but is the overhead really that onerous?


Perhaps not, and there could well be some delay in acceptance if committees
are involved. My worry is that if we don't streamline our processes as much
as possible (see Ian's suggestion about IANA maintaining a
RelExtensions<http://wiki.whatwg.org/wiki/RelExtensions>style wiki)
then people will do as they please anyway - see rel="hub",
rev="canonical", etc.


>  I also question the relevance of the "reference" field in the registry as
>> this links relations to implementations which I think we agree is a bad
>> thing - the registry should capture all the necessary semantics without
>> reliance on external references. It may be interesting to list zero or more
>> implementations of the relation (that is, make the "reference" field
>> optional as well and allow others to add themselves to it), however I'm not
>> sure the maintenance load is worth the effort.
>>
>
> Not to implementations, to the source documents for the registrations
> (which IANA likes to see in registries, AIUI, for paper trail etc).
>

Would it be possible then to support multiple references so that people can
see at a glance that a given relation is implemented as described in
multiple formats (rather than just the first format that happened to
register it)? May well not be worth the maintenance effort.


> It's true that the pre-populated entries have a lot of references to
> formats, but that's an artefact of history, not the direction we'll move in
> going forward.


That being the case would it be worth proactively populating the registry
with common/obvious relations with a view to avoiding e.g. this "monitor" vs
"hub" duplication (which is presumably burnt into various implementations on
both sides)?

I'm specifically thinking here about a thread from a few months ago in which
we discussed different types of references to resources, with a view to
getting relations like 'canonical', 'latest', 'permalink' and 'shortlink'
into the registry. Perhaps a separate I-D is the best way to achieve this,

Sam

--001485f6c44e1748da0473aec7bd
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Wed, Sep 16, 2009 at 3:21 AM, Mark Nottingham <span dir=3D"ltr">&lt;<a h=
ref=3D"mailto:mnot@mnot.net">mnot@mnot.net</a>&gt;</span> wrote:<br><div cl=
ass=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0=
 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class=3D"im"><br>
On 11/09/2009, at 11:17 PM, Sam Johnston wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
One nitpick about the process is that it seems a request can be denied with=
 a suggestion for another relation (for example we might prefer to use some=
thing like &quot;push&quot; or &quot;notif[y|ier|ication|ications&quot; rat=
her than &quot;hub&quot; for this one) but then that would require restarti=
ng the process where it should proceed to registration immediately if the c=
hange is accepted by the applicant.<br>

</blockquote>
<br></div>
Yes, but is the overhead really that onerous?</blockquote><div><br></div><d=
iv>Perhaps not, and there could well be some delay in acceptance if committ=
ees are involved. My worry is that if we don&#39;t streamline our processes=
 as much as possible (see Ian&#39;s suggestion about IANA maintaining a <a =
href=3D"http://wiki.whatwg.org/wiki/RelExtensions">RelExtensions</a> style =
wiki) then people will do as they please anyway - see rel=3D&quot;hub&quot;=
, rev=3D&quot;canonical&quot;, etc.</div>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex;"><div class=3D"im">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
I also question the relevance of the &quot;reference&quot; field in the reg=
istry as this links relations to implementations which I think we agree is =
a bad thing - the registry should capture all the necessary semantics witho=
ut reliance on external references. It may be interesting to list zero or m=
ore implementations of the relation (that is, make the &quot;reference&quot=
; field optional as well and allow others to add themselves to it), however=
 I&#39;m not sure the maintenance load is worth the effort.<br>

</blockquote>
<br></div>
Not to implementations, to the source documents for the registrations (whic=
h IANA likes to see in registries, AIUI, for paper trail etc).<br></blockqu=
ote><div><br></div><div>Would it be possible then to support multiple refer=
ences so that people can see at a glance that a given relation is implement=
ed as described in multiple formats (rather than just the first format that=
 happened to register it)? May well not be worth the maintenance effort.</d=
iv>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex;">
It&#39;s true that the pre-populated entries have a lot of references to fo=
rmats, but that&#39;s an artefact of history, not the direction we&#39;ll m=
ove in going forward.</blockquote><div><br></div><div>That being the case w=
ould it be worth proactively populating the registry with common/obvious re=
lations with a view to avoiding e.g. this &quot;monitor&quot; vs &quot;hub&=
quot; duplication (which is presumably burnt into various implementations o=
n both sides)?</div>
<div><br></div><div>I&#39;m specifically thinking here about a thread from =
a few months ago in which we discussed different types of references to res=
ources, with a view to getting relations like &#39;canonical&#39;, &#39;lat=
est&#39;, &#39;permalink&#39; and &#39;shortlink&#39; into the registry. Pe=
rhaps a separate I-D is the best way to achieve this,</div>
<div><br></div><div>Sam</div><div><br></div></div>

--001485f6c44e1748da0473aec7bd--


From owner-atom-syntax@mail.imc.org  Wed Sep 16 03:38:46 2009
Return-Path: <owner-atom-syntax@mail.imc.org>
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 F0BAB3A6895 for <ietfarch-atompub-archive@core3.amsl.com>; Wed, 16 Sep 2009 03:38:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.755
X-Spam-Level: 
X-Spam-Status: No, score=-6.755 tagged_above=-999 required=5 tests=[AWL=-1.332, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, 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 5fFYrP3xPQpA for <ietfarch-atompub-archive@core3.amsl.com>; Wed, 16 Sep 2009 03:38:45 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 88A533A683D for <atompub-archive@ietf.org>; Wed, 16 Sep 2009 03:38:45 -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 n8GADi4I079537 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 16 Sep 2009 03:13:44 -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 n8GADiUS079536; Wed, 16 Sep 2009 03:13:44 -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 eu1sys200aog103.obsmtp.com (eu1sys200aog103.obsmtp.com [207.126.144.115]) by balder-227.proper.com (8.14.2/8.14.2) with SMTP id n8GADa7U079524 for <atom-syntax@imc.org>; Wed, 16 Sep 2009 03:13:42 -0700 (MST) (envelope-from samj@samj.net)
Received: from source ([209.85.218.206]) by eu1sys200aob103.postini.com ([207.126.147.11]) with SMTP ID DSNKSrC6T7+XrVK0WhGvruYtjmkYcDA67KoK@postini.com; Wed, 16 Sep 2009 10:13:42 UTC
Received: by bwz2 with SMTP id 2so3191457bwz.43 for <atom-syntax@imc.org>; Wed, 16 Sep 2009 03:13:35 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.239.139.132 with SMTP id t4mr850128hbt.88.1253096015449; Wed,  16 Sep 2009 03:13:35 -0700 (PDT)
In-Reply-To: <ADAD548E-2E95-4385-A749-7C6D5611D4F1@mnot.net>
References: <ca722a9e0909101030g6ccbc1e2t823f2abd19307bea@mail.gmail.com> <ADAD548E-2E95-4385-A749-7C6D5611D4F1@mnot.net>
Date: Wed, 16 Sep 2009 12:13:35 +0200
Message-ID: <21606dcf0909160313m1dcad47dk47c139959edb113d@mail.gmail.com>
Subject: Re: Input on request for link relation
From: Sam Johnston <samj@samj.net>
To: Mark Nottingham <mnot@mnot.net>
Cc: Lisa Dusseault <lisa.dusseault@gmail.com>, Atom-Syntax Syntax <atom-syntax@imc.org>, ietf-http-wg@w3.org, Brett Slatkin <brett@haxor.com>
Content-Type: multipart/alternative; boundary=001485f723daded0280473af269f
Sender: owner-atom-syntax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/atom-syntax/mail-archive/>
List-Unsubscribe: <mailto:atom-syntax-request@imc.org?body=unsubscribe>
List-ID: <atom-syntax.imc.org>

--001485f723daded0280473af269f
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Sep 16, 2009 at 8:15 AM, Mark Nottingham <mnot@mnot.net> wrote:

> In the current link draft, relations shouldn't have dependencies on the
> media types of what's linked to, and it looks like both the request and
> response content is constrained in this proposal.
>
> Why not use an extension relation type (i.e., unregistered URL) instead of
> a registered one? That allows the protocol to define things much more
> closely, because it will "own" the relation type.
>

I tend to agree that such standards should be strongly encouraged to use URI
relations (at least while waiting for approval, but perhaps also on an
ongoing basis) and that clients should accept both. One way to precipitate
this would be to reject this application, giving reference to the existing
'monitor' relation (which per Adam Roach above "was to be used for both
polling *and* passive mechanisms").

I see that the applicant (copied) owns http://pubsubhubbub.org/ which would
be as good a URI as any to use, but they could also use the Google Code site
or a PURL. Being able to resolve directly back to the specification rather
than going via the registry would presumably be advantageous too. In any
case it's not clear to me how this registration will help interoperability
given the constraints Mark referred to above and Brett in this
thread<http://groups.google.com/group/pubsubhubbub/browse_thread/thread/e24797ef477ecddd/a6ed35a34ad1421b#a6ed35a34ad1421b>
:

The protocol-specific nature of the "hub" relation is extremely important.
> Like the AtomPub "edit-media" relation, the "hub" link is a machine-readable
> declaration that enables software to take a specific action on discovery
> (via the PubSubHubbub protocol). Without being bound to a specific protocol
> this discovery mechanism becomes useless.


Indeed if competitive standards like PubSubHubbub and rssCloud were to share
the relation (at least without clarifying with a content type) then it could
ironically cause interoperability problems. Note also that the motivation
for the application was Atom compliance which would be achieved with a URI
relation. That's not to say it's any less of a standard, just that the
relations registry is intended for generic relations (at least going
forward).

Sam


> On 11/09/2009, at 3:30 AM, Lisa Dusseault wrote:
>
>  Comments welcome on the following request
>>
>> thx,
>> lisa
>>
>> ---
>> General Request for Assignments (link-relations)
>>
>> Contact Name :
>> Brett Slatkin
>>
>> Type of Assignment :
>> I want to add a new Atom Link Relation type for the PubSubHubbub protocol
>>
>> (http://pubsubhubbub.googlecode.com). The relation type is "hub".
>>
>> Registry :
>> http://www.iana.org/assignments/link-relations/link-relations.xhtml
>>
>>
>> Description :
>> The new  is used for discovery of Hubs,
>> which enables real-time notifications of entries in Atom and RSS feeds.
>> Without making the relation type official, we're not in compliance with
>> the
>>
>> Atom spec.
>>
>> Additional Info :
>> http://pubsubhubbub.googlecode.com/svn/trunk/pubsubhubbub-core-0.1.html
>>
>>
>
> --
> Mark Nottingham     http://www.mnot.net/
>
>
>

--001485f723daded0280473af269f
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Wed, Sep 16, 2009 at 8:15 AM, Mark Nottingham <span dir=3D"ltr">&lt;<a h=
ref=3D"mailto:mnot@mnot.net">mnot@mnot.net</a>&gt;</span> wrote:<br><div cl=
ass=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0=
 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
In the current link draft, relations shouldn&#39;t have dependencies on the=
 media types of what&#39;s linked to, and it looks like both the request an=
d response content is constrained in this proposal.<br>
<br>
Why not use an extension relation type (i.e., unregistered URL) instead of =
a registered one? That allows the protocol to define things much more close=
ly, because it will &quot;own&quot; the relation type.<br></blockquote>
<div><br></div><div>I tend to agree that such standards should be strongly =
encouraged to use URI relations (at least while waiting for approval, but p=
erhaps also on an ongoing basis) and that clients should accept both.=A0One=
=A0way to precipitate this would be to reject this application, giving refe=
rence to the existing &#39;monitor&#39; relation (which per Adam Roach abov=
e &quot;was to be used for both polling *and* passive mechanisms&quot;).</d=
iv>
<div><br></div><div>I see that the applicant (copied) owns <a href=3D"http:=
//pubsubhubbub.org/">http://pubsubhubbub.org/</a> which would be as good a =
URI as any to use, but they could also use the Google Code site or a PURL. =
Being able to resolve directly back to the specification rather than going =
via the registry would presumably be advantageous too.=A0In any case it&#39=
;s not clear to me how this registration will help interoperability given t=
he constraints Mark referred to above and Brett in <a href=3D"http://groups=
.google.com/group/pubsubhubbub/browse_thread/thread/e24797ef477ecddd/a6ed35=
a34ad1421b#a6ed35a34ad1421b">this thread</a>:</div>
<div><br></div><div><blockquote class=3D"gmail_quote" style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left=
-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: soli=
d; padding-left: 1ex; ">
The protocol-specific nature of the &quot;hub&quot; relation is extremely=
=A0important. Like the AtomPub &quot;edit-media&quot; relation, the &quot;h=
ub&quot; link is a=A0machine-readable declaration that enables software to =
take a specific=A0<span class=3D"Apple-style-span" style=3D"font-family: ar=
ial, sans-serif; font-size: 12px; ">action on discovery (via the PubSubHubb=
ub protocol). Without being=A0bound to a specific protocol this discovery m=
echanism becomes useless.=A0</span></blockquote>
</div><div><br></div><div>Indeed if competitive standards like PubSubHubbub=
 and rssCloud were to share the relation (at least without clarifying with =
a content type) then it could ironically cause interoperability problems. N=
ote also that the motivation for the application was Atom compliance which =
would be achieved with a URI relation.=A0That&#39;s not to say it&#39;s any=
 less of a standard, just that the relations registry is intended for gener=
ic relations (at least going forward).</div>
<div><br></div><div>Sam</div><div>=A0</div><blockquote class=3D"gmail_quote=
" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">=
<div><div class=3D"h5">
On 11/09/2009, at 3:30 AM, Lisa Dusseault wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Comments welcome on the following request<br>
<br>
thx,<br>
lisa<br>
<br>
---<br>
General Request for Assignments (link-relations)<br>
<br>
Contact Name :<br>
Brett Slatkin<br>
<br>
Type of Assignment :<br>
I want to add a new Atom Link Relation type for the PubSubHubbub protocol<b=
r>
<br>
(<a href=3D"http://pubsubhubbub.googlecode.com" target=3D"_blank">http://pu=
bsubhubbub.googlecode.com</a>). The relation type is &quot;hub&quot;.<br>
<br>
Registry :<br>
<a href=3D"http://www.iana.org/assignments/link-relations/link-relations.xh=
tml" target=3D"_blank">http://www.iana.org/assignments/link-relations/link-=
relations.xhtml</a><br>
<br>
<br>
Description :<br>
The new =A0is used for discovery of Hubs,<br>
which enables real-time notifications of entries in Atom and RSS feeds.<br>
Without making the relation type official, we&#39;re not in compliance with=
 the<br>
<br>
Atom spec.<br>
<br>
Additional Info :<br>
<a href=3D"http://pubsubhubbub.googlecode.com/svn/trunk/pubsubhubbub-" targ=
et=3D"_blank">http://pubsubhubbub.googlecode.com/svn/trunk/pubsubhubbub-</a=
>core-0.1.html<br>
<br>
</blockquote>
<br>
<br></div></div><div><div></div><div class=3D"h5">
--<br>
Mark Nottingham =A0 =A0 <a href=3D"http://www.mnot.net/" target=3D"_blank">=
http://www.mnot.net/</a><br>
<br>
<br>
</div></div></blockquote></div><br>

--001485f723daded0280473af269f--


From owner-atom-syntax@mail.imc.org  Wed Sep 16 23:28:05 2009
Return-Path: <owner-atom-syntax@mail.imc.org>
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 51B173A6B10 for <ietfarch-atompub-archive@core3.amsl.com>; Wed, 16 Sep 2009 23:28:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.206
X-Spam-Level: 
X-Spam-Status: No, score=-7.206 tagged_above=-999 required=5 tests=[AWL=-1.160, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, 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 hOIpw6TF4D7e for <ietfarch-atompub-archive@core3.amsl.com>; Wed, 16 Sep 2009 23:28:04 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 083913A6989 for <atompub-archive@ietf.org>; Wed, 16 Sep 2009 23:28:03 -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 n8H5pQQv051451 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 16 Sep 2009 22:51:26 -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 n8H5pQ84051450; Wed, 16 Sep 2009 22:51:26 -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-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n8H5pM6i051443 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <atom-syntax@imc.org>; Wed, 16 Sep 2009 22:51:25 -0700 (MST) (envelope-from mnot@mnot.net)
Received: from [192.168.1.6] (unknown [118.208.246.125]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 06CFC22E1F3; Thu, 17 Sep 2009 01:51:18 -0400 (EDT)
Subject: Re: Input on request for link relation [  w/ proposed modifications to link draft ]
Mime-Version: 1.0 (Apple Message framework v1076)
Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <966f8bd30909160735r43fd3c48p4059867e34ecd456@mail.gmail.com>
Date: Thu, 17 Sep 2009 15:51:15 +1000
Cc: Sam Johnston <samj@samj.net>, Lisa Dusseault <lisa.dusseault@gmail.com>, Atom-Syntax Syntax <atom-syntax@imc.org>, ietf-http-wg@w3.org
Content-Transfer-Encoding: 7bit
Message-Id: <72D0641A-F30F-484C-ADAB-A042AA5E82DD@mnot.net>
References: <ca722a9e0909101030g6ccbc1e2t823f2abd19307bea@mail.gmail.com> <ADAD548E-2E95-4385-A749-7C6D5611D4F1@mnot.net> <21606dcf0909160313m1dcad47dk47c139959edb113d@mail.gmail.com> <966f8bd30909160735r43fd3c48p4059867e34ecd456@mail.gmail.com>
To: Brett Slatkin <brett@haxor.com>
X-Mailer: Apple Mail (2.1076)
Sender: owner-atom-syntax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/atom-syntax/mail-archive/>
List-Unsubscribe: <mailto:atom-syntax-request@imc.org?body=unsubscribe>
List-ID: <atom-syntax.imc.org>

On 17/09/2009, at 12:35 AM, Brett Slatkin wrote:

> I understand part of the motivation for mnot's draft
> (http://www.ietf.org/id/draft-nottingham-http-link-header-06.txt), but
> it doesn't remove the need for registered link relations. It seems
> that the litmus test for registration is whether the relation is
> "broadly useful".

The litmus test is that:

* It's broadly applicable (which currently isn't true, because you're  
specific to Atom feeds)
* It has an existing, stable specification (which it looks like you're  
approaching, if you submit as an Internet-Draft), and
* It not be specific to a particular media type (which you are, at  
least for requests).

So there's probably room for getting it in, especially since you're  
effectively "grandfathered". See below for more.


> In that regard, it's important to note that PubSubHubbub is live for
> over 100 *million* feeds as of this writing. It is consumed by dozens
> of companies and developers from multiple countries. There are
> implementations of publisher and subscriber clients in many
> programming languages. There are even new companies with private
> investment running hubs. We've had the genie out of the bottle (since
> October 2008) and it's difficult to go back to ask everyone to change
> things now.

Then why are you only bringing it to the attention of the wider world  
now? I don't mean to pick on you, but it seems like there are lots of  
developers these days who are writing protocols in secret, and then  
expecting the world to come along for the ride, no matter how badly  
they interact with the infrastructure. Pubsubhubbub (PLEASE come up  
with a shorter name!) isn't the worst in this respect by far, but  
still...


> Also, on second thought, I should have pointed out that others
> (namely, Jeff Lindsay) advocate making PubSubHubbub a generic protocol
> that's not specific to any particular content type. This would enable
> the protocol to push event-based Atom, RSS, text, arbitrary XML, HTML,
> raw bytes, etc. I've pushed back on this because I don't want to lose
> focus on the use-case of feeds (because it's immediately useful), but
> I think making this protocol more generic in the future is a good
> idea.
>
> So, this is how I would modify your description from before to be  
> more generic:
>
> Description: A URI for a "hub" (speaking the PubSubHubbub protocol)
> that enables clients to register for and publish real-time updates to
> the resource.
>
> How does that sound?

That's a start. To my mind, you need to:

1. Accommodate things other than Atom feeds in your protocol, if only  
by leaving appropriate extension points for addressing it in a future  
(hopefully soon; lots of people are interested in this, from what I've  
seen) revision.

2. Publish as an Internet-Draft.

The question that this brings to mind for me about the Link draft is  
whether this text about registered relations is appropriate:

"Relation types that constrain the target IRI or context IRI (e.g., to  
a specific media type) MUST NOT be registered."

Obviously, that's pretty open-ended, and generally link relation types  
shouldn't specify a media type, if they're to be broadly applicable,  
but relations like "hub" that constrain things to specific input and  
output formats for *generic* protocols (here, pub/sub) could be an  
exception. Read too broadly, and this requirement could even disallow  
"duplicate" as we've been discussing on a separate thread.

My inclination at this point is to rewrite this as something like:

"Registered relation types MUST NOT constrain the media type of the  
context IRI, and MUST NOT constrain the available representation media  
types of the target IRI. However, they MAY specify the behaviours  
(e.g., allowable methods, request media types) and constrain the  
representations of target resources in other ways."

Thoughts?

Regarding "hub" vs. "monitor" -- this is interesting to me, if not  
just because people have been talking about this sort of protocol for  
easily more than a decade, and many proposals have already been made*.  
As such, I think there's more value in something more capable than  
specific, lest we all drown in a sea of special-purpose, needlessly  
application-specific protocols.

That said, I don't think you can use one link relation for both  
purposes, because even if they both took the same POST payloads, the  
further interactions beyond that (the callback to you) would also need  
to be compatible. While you could use the type attribute to  
distinguish between which protocol is in use, that's not really what  
it's for; the representation returned wouldn't be describing the  
protocol that was going to commence.

Cheers,


* I'm purposefully limiting my comments here to the impact on the link  
relations draft and registry. I have many other thoughts about  
pubsubhubbub and how suitable it is to general use; hopefully I'll  
have time to convey them separately.


--
Mark Nottingham     http://www.mnot.net/


From owner-atom-syntax@mail.imc.org  Wed Sep 16 23:57:59 2009
Return-Path: <owner-atom-syntax@mail.imc.org>
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 C9A6A3A69D5 for <ietfarch-atompub-archive@core3.amsl.com>; Wed, 16 Sep 2009 23:57:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.189
X-Spam-Level: 
X-Spam-Status: No, score=-7.189 tagged_above=-999 required=5 tests=[AWL=-1.143, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, 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 nZseyf3np-xZ for <ietfarch-atompub-archive@core3.amsl.com>; Wed, 16 Sep 2009 23:57:58 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 645253A690E for <atompub-archive@ietf.org>; Wed, 16 Sep 2009 23:57:58 -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 n8H6QOcJ053702 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 16 Sep 2009 23:26:24 -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 n8H6QOTR053701; Wed, 16 Sep 2009 23:26:24 -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-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n8H6QM4R053695 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <atom-syntax@imc.org>; Wed, 16 Sep 2009 23:26:23 -0700 (MST) (envelope-from mnot@mnot.net)
Received: from [192.168.1.6] (unknown [118.208.246.125]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 6FF3522E1F3; Thu, 17 Sep 2009 02:26:15 -0400 (EDT)
Subject: Re: Input on request for link relation
Mime-Version: 1.0 (Apple Message framework v1076)
Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <21606dcf0909160246i56c1dc55l43631423a542c41a@mail.gmail.com>
Date: Thu, 17 Sep 2009 16:26:11 +1000
Cc: Hadrien Gardeur <hadrien.gardeur@feedbooks.com>, Atom-Syntax Syntax <atom-syntax@imc.org>, HTTP Working Group <ietf-http-wg@w3.org>, apps-discuss@ietf.org, Ian Hickson <ian@hixie.ch>
Content-Transfer-Encoding: 7bit
Message-Id: <2B6D770A-58C5-48D6-AF52-7341812C9BFA@mnot.net>
References: <ca722a9e0909101030g6ccbc1e2t823f2abd19307bea@mail.gmail.com> <8860AD10-B0C5-4BEF-8C68-731973EF4046@mac.com> <30ac519d0909101631m14782ce8vd085629237b0e444@mail.gmail.com> <C86DEC0A-6370-4C0B-98A9-3806F2014AE5@mac.com> <21606dcf0909110445s78ea728cueb158ff588f394a5@mail.gmail.com> <404dcbd20909110500j5394c43dve10264c01a7a6244@mail.gmail.com> <21606dcf0909110617y40586e53x213e5e8febc4a9e8@mail.gmail.com> <0CB59F7B-A9DD-4866-8F70-A65869A79277@mnot.net> <21606dcf0909160246i56c1dc55l43631423a542c41a@mail.gmail.com>
To: Sam Johnston <samj@samj.net>
X-Mailer: Apple Mail (2.1076)
Sender: owner-atom-syntax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/atom-syntax/mail-archive/>
List-Unsubscribe: <mailto:atom-syntax-request@imc.org?body=unsubscribe>
List-ID: <atom-syntax.imc.org>

On 16/09/2009, at 7:46 PM, Sam Johnston wrote:

> On Wed, Sep 16, 2009 at 3:21 AM, Mark Nottingham <mnot@mnot.net>  
> wrote:
>
> On 11/09/2009, at 11:17 PM, Sam Johnston wrote:
>
> One nitpick about the process is that it seems a request can be  
> denied with a suggestion for another relation (for example we might  
> prefer to use something like "push" or "notif[y|ier|ication| 
> ications" rather than "hub" for this one) but then that would  
> require restarting the process where it should proceed to  
> registration immediately if the change is accepted by the applicant.
>
> Yes, but is the overhead really that onerous?
>
> Perhaps not, and there could well be some delay in acceptance if  
> committees are involved. My worry is that if we don't streamline our  
> processes as much as possible (see Ian's suggestion about IANA  
> maintaining a RelExtensions style wiki) then people will do as they  
> please anyway - see rel="hub", rev="canonical", etc.

Interesting examples; the "hub" people are actively engaging  
(finally), and I've already talked to some of the "canonical" folks  
about doing an I-D once the Link draft is an RFC.

> Would it be possible then to support multiple references so that  
> people can see at a glance that a given relation is implemented as  
> described in multiple formats (rather than just the first format  
> that happened to register it)? May well not be worth the maintenance  
> effort.

How about adding a new field for references to more information about  
how a relation is used in a particular context (scoped by context  
media type)?

E.g.,

References regarding use in specific contexts:
     text/html: [HTML5]
     application/atom+xml: [RFC4287]

One concern here is that there are going to be questions about  
authority; while it's fine for the HTML5 crowd to dictate what happens  
when you see a particular relation in an HTML context, what happens  
when someone comes along and defines a spec for a media type they  
don't own? We'd need some additional guidance about amending  
registrations, I think, which is doable, but it'll make things more  
complex.

What do people think about this generally? Ian, would this help you at  
all?

We'd still need a generic 'reference' field for the defining document  
of the relation itself, but in some cases the current references would  
change to be context references; e.g.,

             Relation Name: chapter
             Description: Refers to a chapter in a collection of  
resources.
             Reference: [this specification]
             References regarding use in specific contexts:
                   text/html: [W3C.REC-html401-19991224]

--
Mark Nottingham     http://www.mnot.net/


From owner-atom-syntax@mail.imc.org  Thu Sep 17 06:16:47 2009
Return-Path: <owner-atom-syntax@mail.imc.org>
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 C450D3A685C for <ietfarch-atompub-archive@core3.amsl.com>; Thu, 17 Sep 2009 06:16:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.743
X-Spam-Level: 
X-Spam-Status: No, score=-6.743 tagged_above=-999 required=5 tests=[AWL=-1.320, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, 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 hOQmDVQoBDEz for <ietfarch-atompub-archive@core3.amsl.com>; Thu, 17 Sep 2009 06:16:46 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 8A8F23A693C for <atompub-archive@ietf.org>; Thu, 17 Sep 2009 06:16: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 n8HDAOhL078863 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 17 Sep 2009 06:10:24 -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 n8HDANwG078862; Thu, 17 Sep 2009 06:10:23 -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 eu1sys200aog117.obsmtp.com (eu1sys200aog117.obsmtp.com [207.126.144.143]) by balder-227.proper.com (8.14.2/8.14.2) with SMTP id n8HDAF4Y078837 for <atom-syntax@imc.org>; Thu, 17 Sep 2009 06:10:21 -0700 (MST) (envelope-from samj@samj.net)
Received: from source ([209.85.220.216]) by eu1sys200aob117.postini.com ([207.126.147.11]) with SMTP ID DSNKSrI1NjTaP/NrRzSDxCnvq0MXEbiuK7bn@postini.com; Thu, 17 Sep 2009 13:10:21 UTC
Received: by fxm12 with SMTP id 12so7693fxm.42 for <atom-syntax@imc.org>; Thu, 17 Sep 2009 06:10:14 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.239.145.33 with SMTP id q33mr3670hba.126.1253193013873; Thu,  17 Sep 2009 06:10:13 -0700 (PDT)
In-Reply-To: <90C41DD21FB7C64BB94121FBBC2E72343784D57E68@P3PW5EX1MB01.EX1.SECURESERVER.NET>
References: <ca722a9e0909101030g6ccbc1e2t823f2abd19307bea@mail.gmail.com> <ADAD548E-2E95-4385-A749-7C6D5611D4F1@mnot.net> <21606dcf0909160313m1dcad47dk47c139959edb113d@mail.gmail.com> <966f8bd30909160735r43fd3c48p4059867e34ecd456@mail.gmail.com> <90C41DD21FB7C64BB94121FBBC2E72343784D57E5C@P3PW5EX1MB01.EX1.SECURESERVER.NET> <966f8bd30909161803r60be2418pff9ff4bdfcb7125f@mail.gmail.com> <90C41DD21FB7C64BB94121FBBC2E72343784D57E68@P3PW5EX1MB01.EX1.SECURESERVER.NET>
Date: Thu, 17 Sep 2009 15:10:13 +0200
Message-ID: <21606dcf0909170610r220da0a1qbfe40ea348274ace@mail.gmail.com>
Subject: Re: Input on request for link relation
From: Sam Johnston <samj@samj.net>
To: Eran Hammer-Lahav <eran@hueniverse.com>
Cc: Brett Slatkin <brett@haxor.com>, Atom-Syntax Syntax <atom-syntax@imc.org>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Content-Type: multipart/alternative; boundary=001485f791806d4e1c0473c5bcac
Sender: owner-atom-syntax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/atom-syntax/mail-archive/>
List-Unsubscribe: <mailto:atom-syntax-request@imc.org?body=unsubscribe>
List-ID: <atom-syntax.imc.org>

--001485f791806d4e1c0473c5bcac
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Sep 17, 2009 at 4:02 AM, Eran Hammer-Lahav <eran@hueniverse.com>wrote:

>
> I also want to point out that we really need to work on our messaging and
> perception that URI extension relation type are in any way inferior or "less
> cool" than the short registered ones. The sooner protocol authors accept
> this as a perfectly valid choice for their protocol needs, the better the
> link framework will be.


I couldn't have said it better myself. Basically what you are saying by
requesting a short relation is that you actively intend to share the
relation with others with a view to improving interoperability. By using a
URI you control you're saying you want it to have a specific, concrete
meaning (while retaining the option of sharing). The more I hear the more it
sounds like PubSubHubbub wants the latter and with that in mind I would
suggest that http://pubsubhubbub.org/ is as good an identifier as any.

Imagine a feed advertising both rssCloud and PuSH - without clarification of
the "hub" relation (for example by way of dedicated content types) clients
will have to use protocol discovery or trial and error to work out what to
use. It doesn't help that it's not so much a content type we're talking
about but a protocol, in which case a [registered] service name would be a
better fit (and even then registered service names are generally used in
conjunction with well-known port assignments rather than "everything over
HTTP").

I have a similar problem with OCCI <http://www.occi-wg.org/> whereby I want
to advertise console access to virtual machines via ssh, vnc-server
or ms-wbt-server - I guess we'll have to assign a separate link relation
(like  http://purl.org/occi/console#ssh) for each protocol, which is a bit
of a hack when e.g. a "service=ssh" attribute would accomplish the same.
Conversely content types work fine for advertising console screenshots in
e.g. PNG or JPEG.

Mark: perhaps you could consider including some wording like Eran's and/or
mine above into the Web Linking draft so we can point at it later? I would
also suggest that the "broadly useful" test needs some refinement - the
implication in rejecting applications is that the applicant's work is not
"broadly useful" while what we mean by this is that it is useful for
multiple/many standards.

Sam

--001485f791806d4e1c0473c5bcac
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Thu, Sep 17, 2009 at 4:02 AM, Eran Hammer-Lahav <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:eran@hueniverse.com">eran@hueniverse.com</a>&gt;</span> wro=
te:<br><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class=3D"im"><br></div>
I also want to point out that we really need to work on our messaging and p=
erception that URI extension relation type are in any way inferior or &quot=
;less cool&quot; than the short registered ones. The sooner protocol author=
s accept this as a perfectly valid choice for their protocol needs, the bet=
ter the link framework will be.</blockquote>
<div><br></div><div>I couldn&#39;t have said it better myself. Basically wh=
at you are saying by requesting a short relation is that you actively inten=
d to share the relation with others with a view to improving interoperabili=
ty. By using a URI you control you&#39;re saying you want it to have a spec=
ific, concrete meaning (while retaining the option of sharing).=A0The more =
I hear the more it sounds like PubSubHubbub wants the latter and with that =
in mind I would suggest that <a href=3D"http://pubsubhubbub.org/">http://pu=
bsubhubbub.org/</a> is as good an identifier as any.</div>
<div><br></div><div>Imagine a feed advertising both rssCloud and PuSH - wit=
hout clarification of the &quot;hub&quot; relation (for example by way of d=
edicated content types) clients will have to use protocol discovery or tria=
l and error to work out what to use. It doesn&#39;t help that it&#39;s not =
so much a content type we&#39;re talking about but a protocol, in which cas=
e a [registered] service name would be a better fit (and even then register=
ed service names are generally used in conjunction with well-known port ass=
ignments rather than &quot;everything over HTTP&quot;).</div>
<div><br></div><div>I have a similar problem with <a href=3D"http://www.occ=
i-wg.org/">OCCI</a> whereby I want to advertise console access to virtual m=
achines via ssh, vnc-server or=A0ms-wbt-server - I guess we&#39;ll have to =
assign a separate link relation (like =A0<a href=3D"http://purl.org/occi/co=
nsole#ssh">http://purl.org/occi/console#ssh</a>) for each protocol, which i=
s a bit of a hack when e.g. a &quot;service=3Dssh&quot; attribute would acc=
omplish the same. Conversely content types work fine for advertising consol=
e screenshots in e.g. PNG or JPEG.</div>
<div><br></div><div>Mark: perhaps you could consider including some wording=
 like Eran&#39;s and/or mine above into the Web Linking draft so we can poi=
nt at it later? I would also suggest that the &quot;broadly useful&quot; te=
st needs some refinement - the implication in rejecting applications is tha=
t the applicant&#39;s work is not &quot;broadly useful&quot; while what we =
mean by this is that it is useful for multiple/many standards.</div>
<div><br></div><div>Sam</div><div><br></div></div>

--001485f791806d4e1c0473c5bcac--


From owner-atom-syntax@mail.imc.org  Thu Sep 17 15:21:59 2009
Return-Path: <owner-atom-syntax@mail.imc.org>
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 2EF6E3A6A56 for <ietfarch-atompub-archive@core3.amsl.com>; Thu, 17 Sep 2009 15:21:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.941
X-Spam-Level: 
X-Spam-Status: No, score=-6.941 tagged_above=-999 required=5 tests=[AWL=-1.518, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, 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 k6ZeKYtSB8Gx for <ietfarch-atompub-archive@core3.amsl.com>; Thu, 17 Sep 2009 15:21:57 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 6FF7B3A69D6 for <atompub-archive@ietf.org>; Thu, 17 Sep 2009 15:21:57 -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 n8HME0Vd014245 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 17 Sep 2009 15:14:00 -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 n8HME0wq014244; Thu, 17 Sep 2009 15:14:00 -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 mail-ew0-f205.google.com (mail-ew0-f205.google.com [209.85.219.205]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n8HMDpRS014229 for <atom-syntax@imc.org>; Thu, 17 Sep 2009 15:13:58 -0700 (MST) (envelope-from john@johnpanzer.com)
Received: by ewy1 with SMTP id 1so470037ewy.27 for <atom-syntax@imc.org>; Thu, 17 Sep 2009 15:13:50 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.211.146.18 with SMTP id y18mr268744ebn.55.1253225630438; Thu,  17 Sep 2009 15:13:50 -0700 (PDT)
Reply-To: jpanzer@acm.org
In-Reply-To: <72D0641A-F30F-484C-ADAB-A042AA5E82DD@mnot.net>
References: <ca722a9e0909101030g6ccbc1e2t823f2abd19307bea@mail.gmail.com> <ADAD548E-2E95-4385-A749-7C6D5611D4F1@mnot.net> <21606dcf0909160313m1dcad47dk47c139959edb113d@mail.gmail.com> <966f8bd30909160735r43fd3c48p4059867e34ecd456@mail.gmail.com> <72D0641A-F30F-484C-ADAB-A042AA5E82DD@mnot.net>
Date: Thu, 17 Sep 2009 15:13:50 -0700
Message-ID: <30ac519d0909171513l5f7734d5h678e0415a1e03e3c@mail.gmail.com>
Subject: Re: Input on request for link relation [ w/ proposed modifications to  link draft ]
From: John Panzer <john@johnpanzer.com>
To: Mark Nottingham <mnot@mnot.net>
Cc: Brett Slatkin <brett@haxor.com>, Sam Johnston <samj@samj.net>, Lisa Dusseault <lisa.dusseault@gmail.com>, Atom-Syntax Syntax <atom-syntax@imc.org>, ietf-http-wg@w3.org
Content-Type: multipart/alternative; boundary=001636c5a8b08695560473cd5493
Sender: owner-atom-syntax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/atom-syntax/mail-archive/>
List-Unsubscribe: <mailto:atom-syntax-request@imc.org?body=unsubscribe>
List-ID: <atom-syntax.imc.org>

--001636c5a8b08695560473cd5493
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Sep 16, 2009 at 10:51 PM, Mark Nottingham <mnot@mnot.net> wrote:

>
> On 17/09/2009, at 12:35 AM, Brett Slatkin wrote:
>
>  I understand part of the motivation for mnot's draft
>> (http://www.ietf.org/id/draft-nottingham-http-link-header-06.txt), but
>> it doesn't remove the need for registered link relations. It seems
>> that the litmus test for registration is whether the relation is
>> "broadly useful".
>>
>
> The litmus test is that:
>
> * It's broadly applicable (which currently isn't true, because you're
> specific to Atom feeds)
>

Important nit: Also, RSS feeds.


> * It has an existing, stable specification (which it looks like you're
> approaching, if you submit as an Internet-Draft), and
> * It not be specific to a particular media type (which you are, at least
> for requests).
>
> So there's probably room for getting it in, especially since you're
> effectively "grandfathered". See below for more.
>
>
>  In that regard, it's important to note that PubSubHubbub is live for
>> over 100 *million* feeds as of this writing. It is consumed by dozens
>> of companies and developers from multiple countries. There are
>> implementations of publisher and subscriber clients in many
>> programming languages. There are even new companies with private
>> investment running hubs. We've had the genie out of the bottle (since
>> October 2008) and it's difficult to go back to ask everyone to change
>> things now.
>>
>
> Then why are you only bringing it to the attention of the wider world now?
> I don't mean to pick on you, but it seems like there are lots of developers
> these days who are writing protocols in secret, and then expecting the world
> to come along for the ride, no matter how badly they interact with the
> infrastructure. Pubsubhubbub (PLEASE come up with a shorter name!) isn't the
> worst in this respect by far, but still...
>
>
>  Also, on second thought, I should have pointed out that others
>> (namely, Jeff Lindsay) advocate making PubSubHubbub a generic protocol
>> that's not specific to any particular content type. This would enable
>> the protocol to push event-based Atom, RSS, text, arbitrary XML, HTML,
>> raw bytes, etc. I've pushed back on this because I don't want to lose
>> focus on the use-case of feeds (because it's immediately useful), but
>> I think making this protocol more generic in the future is a good
>> idea.
>>
>> So, this is how I would modify your description from before to be more
>> generic:
>>
>> Description: A URI for a "hub" (speaking the PubSubHubbub protocol)
>> that enables clients to register for and publish real-time updates to
>> the resource.
>>
>> How does that sound?
>>
>
> That's a start. To my mind, you need to:
>
> 1. Accommodate things other than Atom feeds in your protocol, if only by
> leaving appropriate extension points for addressing it in a future
> (hopefully soon; lots of people are interested in this, from what I've seen)
> revision.
>
> 2. Publish as an Internet-Draft.
>
> The question that this brings to mind for me about the Link draft is
> whether this text about registered relations is appropriate:
>
> "Relation types that constrain the target IRI or context IRI (e.g., to a
> specific media type) MUST NOT be registered."
>
> Obviously, that's pretty open-ended, and generally link relation types
> shouldn't specify a media type, if they're to be broadly applicable, but
> relations like "hub" that constrain things to specific input and output
> formats for *generic* protocols (here, pub/sub) could be an exception. Read
> too broadly, and this requirement could even disallow "duplicate" as we've
> been discussing on a separate thread.
>
> My inclination at this point is to rewrite this as something like:
>
> "Registered relation types MUST NOT constrain the media type of the context
> IRI, and MUST NOT constrain the available representation media types of the
> target IRI. However, they MAY specify the behaviours (e.g., allowable
> methods, request media types) and constrain the representations of target
> resources in other ways."
>
> Thoughts?
>
> Regarding "hub" vs. "monitor" -- this is interesting to me, if not just
> because people have been talking about this sort of protocol for easily more
> than a decade, and many proposals have already been made*. As such, I think
> there's more value in something more capable than specific, lest we all
> drown in a sea of special-purpose, needlessly application-specific
> protocols.
>
> That said, I don't think you can use one link relation for both purposes,
> because even if they both took the same POST payloads, the further
> interactions beyond that (the callback to you) would also need to be
> compatible. While you could use the type attribute to distinguish between
> which protocol is in use, that's not really what it's for; the
> representation returned wouldn't be describing the protocol that was going
> to commence.
>
> Cheers,
>
>
> * I'm purposefully limiting my comments here to the impact on the link
> relations draft and registry. I have many other thoughts about pubsubhubbub
> and how suitable it is to general use; hopefully I'll have time to convey
> them separately.
>
>
> --
> Mark Nottingham     http://www.mnot.net/
>
>

--001636c5a8b08695560473cd5493
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Wed, Sep 16, 2009 at 10:51 PM, Mark Nottingham <span dir=3D"ltr">&lt;<a =
href=3D"mailto:mnot@mnot.net">mnot@mnot.net</a>&gt;</span> wrote:<br><div c=
lass=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"border-left=
: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1e=
x;">
<br>
On 17/09/2009, at 12:35 AM, Brett Slatkin wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I understand part of the motivation for mnot&#39;s draft<br>
(<a href=3D"http://www.ietf.org/id/draft-nottingham-http-link-header-06.txt=
" target=3D"_blank">http://www.ietf.org/id/draft-nottingham-http-link-heade=
r-06.txt</a>), but<br>
it doesn&#39;t remove the need for registered link relations. It seems<br>
that the litmus test for registration is whether the relation is<br>
&quot;broadly useful&quot;.<br>
</blockquote>
<br>
The litmus test is that:<br>
<br>
* It&#39;s broadly applicable (which currently isn&#39;t true, because you&=
#39;re specific to Atom feeds)<br></blockquote><div><br>Important nit: Also=
, RSS feeds.<br>=A0</div><blockquote class=3D"gmail_quote" style=3D"border-=
left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left=
: 1ex;">

* It has an existing, stable specification (which it looks like you&#39;re =
approaching, if you submit as an Internet-Draft), and<br>
* It not be specific to a particular media type (which you are, at least fo=
r requests).<br>
<br>
So there&#39;s probably room for getting it in, especially since you&#39;re=
 effectively &quot;grandfathered&quot;. See below for more.<br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
In that regard, it&#39;s important to note that PubSubHubbub is live for<br=
>
over 100 *million* feeds as of this writing. It is consumed by dozens<br>
of companies and developers from multiple countries. There are<br>
implementations of publisher and subscriber clients in many<br>
programming languages. There are even new companies with private<br>
investment running hubs. We&#39;ve had the genie out of the bottle (since<b=
r>
October 2008) and it&#39;s difficult to go back to ask everyone to change<b=
r>
things now.<br>
</blockquote>
<br>
Then why are you only bringing it to the attention of the wider world now? =
I don&#39;t mean to pick on you, but it seems like there are lots of develo=
pers these days who are writing protocols in secret, and then expecting the=
 world to come along for the ride, no matter how badly they interact with t=
he infrastructure. Pubsubhubbub (PLEASE come up with a shorter name!) isn&#=
39;t the worst in this respect by far, but still...<br>

<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Also, on second thought, I should have pointed out that others<br>
(namely, Jeff Lindsay) advocate making PubSubHubbub a generic protocol<br>
that&#39;s not specific to any particular content type. This would enable<b=
r>
the protocol to push event-based Atom, RSS, text, arbitrary XML, HTML,<br>
raw bytes, etc. I&#39;ve pushed back on this because I don&#39;t want to lo=
se<br>
focus on the use-case of feeds (because it&#39;s immediately useful), but<b=
r>
I think making this protocol more generic in the future is a good<br>
idea.<br>
<br>
So, this is how I would modify your description from before to be more gene=
ric:<br>
<br>
Description: A URI for a &quot;hub&quot; (speaking the PubSubHubbub protoco=
l)<br>
that enables clients to register for and publish real-time updates to<br>
the resource.<br>
<br>
How does that sound?<br>
</blockquote>
<br>
That&#39;s a start. To my mind, you need to:<br>
<br>
1. Accommodate things other than Atom feeds in your protocol, if only by le=
aving appropriate extension points for addressing it in a future (hopefully=
 soon; lots of people are interested in this, from what I&#39;ve seen) revi=
sion.<br>

<br>
2. Publish as an Internet-Draft.<br>
<br>
The question that this brings to mind for me about the Link draft is whethe=
r this text about registered relations is appropriate:<br>
<br>
&quot;Relation types that constrain the target IRI or context IRI (e.g., to=
 a specific media type) MUST NOT be registered.&quot;<br>
<br>
Obviously, that&#39;s pretty open-ended, and generally link relation types =
shouldn&#39;t specify a media type, if they&#39;re to be broadly applicable=
, but relations like &quot;hub&quot; that constrain things to specific inpu=
t and output formats for *generic* protocols (here, pub/sub) could be an ex=
ception. Read too broadly, and this requirement could even disallow &quot;d=
uplicate&quot; as we&#39;ve been discussing on a separate thread.<br>

<br>
My inclination at this point is to rewrite this as something like:<br>
<br>
&quot;Registered relation types MUST NOT constrain the media type of the co=
ntext IRI, and MUST NOT constrain the available representation media types =
of the target IRI. However, they MAY specify the behaviours (e.g., allowabl=
e methods, request media types) and constrain the representations of target=
 resources in other ways.&quot;<br>

<br>
Thoughts?<br>
<br>
Regarding &quot;hub&quot; vs. &quot;monitor&quot; -- this is interesting to=
 me, if not just because people have been talking about this sort of protoc=
ol for easily more than a decade, and many proposals have already been made=
*. As such, I think there&#39;s more value in something more capable than s=
pecific, lest we all drown in a sea of special-purpose, needlessly applicat=
ion-specific protocols.<br>

<br>
That said, I don&#39;t think you can use one link relation for both purpose=
s, because even if they both took the same POST payloads, the further inter=
actions beyond that (the callback to you) would also need to be compatible.=
 While you could use the type attribute to distinguish between which protoc=
ol is in use, that&#39;s not really what it&#39;s for; the representation r=
eturned wouldn&#39;t be describing the protocol that was going to commence.=
<br>

<br>
Cheers,<br>
<br>
<br>
* I&#39;m purposefully limiting my comments here to the impact on the link =
relations draft and registry. I have many other thoughts about pubsubhubbub=
 and how suitable it is to general use; hopefully I&#39;ll have time to con=
vey them separately.<br>
<font color=3D"#888888">
<br>
<br>
--<br>
Mark Nottingham =A0 =A0 <a href=3D"http://www.mnot.net/" target=3D"_blank">=
http://www.mnot.net/</a><br>
<br>
</font></blockquote></div><br>

--001636c5a8b08695560473cd5493--


From redefinitionfwb7@isuzucavite.com  Thu Sep 17 16:10:58 2009
Return-Path: <redefinitionfwb7@isuzucavite.com>
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 789163A6AEF; Thu, 17 Sep 2009 16:10:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -11.405
X-Spam-Level: 
X-Spam-Status: No, score=-11.405 tagged_above=-999 required=5 tests=[BAYES_99=3.5, FH_FAKE_RCVD_LINE_B=5.777, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_HCC=4.295, HELO_DYNAMIC_IPADDR2=4.395, HELO_EQ_BR=0.955, HELO_EQ_DSL=1.129, HELO_EQ_TELESP=1.245, HOST_EQ_BR=1.295, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_WEB=0.619, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, SARE_RECV_SPAM_DOMN02=1.666, STOX_REPLY_TYPE=0.001, TVD_RCVD_IP=1.931, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_SBL=20, 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 Hr-x8+JcQnRP; Thu, 17 Sep 2009 16:10:57 -0700 (PDT)
Received: from 201-95-114-178.dsl.telesp.net.br (201-95-114-178.dsl.telesp.net.br [201.95.114.178]) by core3.amsl.com (Postfix) with ESMTP id 28E2928C132; Thu, 17 Sep 2009 16:10:41 -0700 (PDT)
Received: from 201.95.114.178 by iadiexmail.isuzucavite.com; Thu, 17 Sep 2009 20:11:21 -0300
Date: Thu, 17 Sep 2009 20:11:21 -0300
From: Moshe Bower <atompub-archive@megatron.ietf.org>
Subject: last chance to change your life, get into a small pair of jeans
To: <atompub-archive@megatron.ietf.org>
Message-ID: <000d01ca37ec$2b537620$6400a8c0@redefinitionfwb7>
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
Content-type: text/plain; format=flowed; charset="iso-8859-2"; reply-type=original
Content-transfer-encoding: 7bit
X-Priority: 3
X-MSMail-priority: Normal

Hit the beach with your new body 

Push the button now http://aijojxpo.cn

best regards Bower Moshe 
 


From opecwinnining@live.com  Fri Sep 18 01:12:36 2009
Return-Path: <opecwinnining@live.com>
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 AC90F3A689E for <ietfarch-atompub-archive@core3.amsl.com>; Fri, 18 Sep 2009 01:12:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -82.184
X-Spam-Level: 
X-Spam-Status: No, score=-82.184 tagged_above=-999 required=5 tests=[BAYES_99=3.5, DEAR_WINNER=3.197, FH_RELAY_NODNS=1.451, KAM_LOTTO1=2.899, MIME_QP_LONG_LINE=1.396, MISSING_SUBJECT=1.762, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_SBL=1.551, RDNS_NONE=0.1, 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 FPe3IaBELPTI for <ietfarch-atompub-archive@core3.amsl.com>; Fri, 18 Sep 2009 01:12:36 -0700 (PDT)
Received: from unet.edu.ve (unknown [200.44.157.122]) by core3.amsl.com (Postfix) with ESMTP id F24BE3A6806 for <atompub-archive@megatron.ietf.org>; Fri, 18 Sep 2009 01:12:35 -0700 (PDT)
Received: from unet.edu.ve ([::ffff:127.0.0.1]) by unet.edu.ve with esmtp; Thu, 17 Sep 2009 06:15:07 -0430 id 007C49C2.4AB21334.000044A5
Received: from 41.220.75.16 ([41.220.75.16]) by webmail.unet.edu.ve (Horde MIME library) with HTTP; Thu, 17 Sep 2009 06:15:07 -0430
Message-ID: <20090917061507.jam6eik68gcosc8o@webmail.unet.edu.ve>
Date: Thu, 17 Sep 2009 06:15:07 -0430
From: OPEC FUND FOR INTERNATIONAL DEVELOPMENT <opecwinnining@live.com>
Reply-to: opecwinniningfund@live.com
To: undisclosed-recipients: ;
Subject: 
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
User-Agent: Internet Messaging Program (IMP) H3 (4.1.3)

Fw: AWARD NOTIFICATION........Batch Number :(409978E)........SERIAL NREFEREN=
CE
NUMBERS: _OP/9420X2/7UMBER: 5368/02.

WINNER OF 2009 OPEC FUND FOR INTERNATIONAL DEVELOPMENT Friday, August 28,
2009 7:52 PM

Dear Winner,

We wish to inform you that your email address has emerged as one of our luck=
y
winners in this year's OPEC FUND FOR INTERNATIONAL DEVELOPMENT, and you have
therefore won for yourself a total cash sum of =A3900,000.00 GBP (Nine hundr=
ed
thousand Great British Pounds) in this category.
To process your winnings send the following informations to

E-mail opecwinniningfund@live.com

1. Your Full Names:
2. Country :
3. Batch Number:
4. Age:
5. Phone Numbers:
6.Occupation:
Sincerely,
Dr. Omar  Ibrahim.




From lqorgan@activeescape.thlink.net  Fri Sep 18 02:52:49 2009
Return-Path: <lqorgan@activeescape.thlink.net>
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 68CD928C1A7; Fri, 18 Sep 2009 02:52:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.083
X-Spam-Level: ***
X-Spam-Status: No, score=3.083 tagged_above=-999 required=5 tests=[BAYES_99=3.5, GB_ROLEX=5, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_SORBS_WEB=0.619, RCVD_IN_XBL=3.033, SARE_SPEC_ROLEX=1.666, SARE_SPEC_ROLEX_ORD=2.222, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_RHS_DOB=1.083, URIBL_SBL=20, URIBL_WS_SURBL=10, 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 YMUF2wTIBUw9; Fri, 18 Sep 2009 02:52:48 -0700 (PDT)
Received: from mail.alpinehhc.org (mail.alpinehhc.org [96.56.54.171]) by core3.amsl.com (Postfix) with SMTP id 8CA5B28C0EE; Fri, 18 Sep 2009 02:52:35 -0700 (PDT)
Date: Fri, 18 Sep 2009 05:53:32 -0500
Subject: Order your Rolex Submariner right now
From: "Nona Jackson" <atompub-archive@megatron.ietf.org>
To: "Doreen Dahl" <atompub-archive@megatron.ietf.org>
Message-ID: <pvy1zocYX8gNSWEppzt1atompub-archive@megatron.ietf.org>
Content-Type: text/plain;
Content-Transfer-Encoding: 7Bit

Are you ready for hottest rep watches from 2010? They are here http://tablebring.com/





From owner-atom-syntax@mail.imc.org  Fri Sep 18 10:53:01 2009
Return-Path: <owner-atom-syntax@mail.imc.org>
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 E9CE23A68A4 for <ietfarch-atompub-archive@core3.amsl.com>; Fri, 18 Sep 2009 10:53:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.122
X-Spam-Level: 
X-Spam-Status: No, score=-7.122 tagged_above=-999 required=5 tests=[AWL=-2.276, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_63=0.6, J_CHICKENPOX_83=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 YfPOmR0nzHFy for <ietfarch-atompub-archive@core3.amsl.com>; Fri, 18 Sep 2009 10:53:01 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id EFD7A3A63C9 for <atompub-archive@ietf.org>; Fri, 18 Sep 2009 10:53:00 -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 n8IHXiDG083837 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 18 Sep 2009 10:33:44 -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 n8IHXi8P083836; Fri, 18 Sep 2009 10:33:44 -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 mail-bw0-f211.google.com (mail-bw0-f211.google.com [209.85.218.211]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n8IHXgfD083823 for <atom-syntax@imc.org>; Fri, 18 Sep 2009 10:33:43 -0700 (MST) (envelope-from mart@degeneration.co.uk)
Received: by bwz7 with SMTP id 7so894515bwz.10 for <atom-syntax@imc.org>; Fri, 18 Sep 2009 10:33:41 -0700 (PDT)
Received: by 10.204.34.203 with SMTP id m11mr1708640bkd.79.1253295220968; Fri, 18 Sep 2009 10:33:40 -0700 (PDT)
Received: from ?192.168.64.227? ([204.9.180.30]) by mx.google.com with ESMTPS id h2sm1872446fkh.6.2009.09.18.10.33.36 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 18 Sep 2009 10:33:38 -0700 (PDT)
Message-ID: <4AB3C46E.1070200@degeneration.co.uk>
Date: Fri, 18 Sep 2009 10:33:34 -0700
From: Martin Atkins <mart@degeneration.co.uk>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: pubsubhubbub@googlegroups.com
CC: Atom-Syntax Syntax <atom-syntax@imc.org>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Subject: Re: [pubsubhubbub] Re: Input on request for link relation
References: <ca722a9e0909101030g6ccbc1e2t823f2abd19307bea@mail.gmail.com> <ADAD548E-2E95-4385-A749-7C6D5611D4F1@mnot.net> <21606dcf0909160313m1dcad47dk47c139959edb113d@mail.gmail.com> <966f8bd30909160735r43fd3c48p4059867e34ecd456@mail.gmail.com> <90C41DD21FB7C64BB94121FBBC2E72343784D57E5C@P3PW5EX1MB01.EX1.SECURESERVER.NET> <966f8bd30909161803r60be2418pff9ff4bdfcb7125f@mail.gmail.com> <90C41DD21FB7C64BB94121FBBC2E72343784D57E68@P3PW5EX1MB01.EX1.SECURESERVER.NET> <21606dcf0909170610r220da0a1qbfe40ea348274ace@mail.gmail.com>
In-Reply-To: <21606dcf0909170610r220da0a1qbfe40ea348274ace@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-atom-syntax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/atom-syntax/mail-archive/>
List-Unsubscribe: <mailto:atom-syntax-request@imc.org?body=unsubscribe>
List-ID: <atom-syntax.imc.org>

Sam Johnston wrote:
> On Thu, Sep 17, 2009 at 4:02 AM, Eran Hammer-Lahav <eran@hueniverse.com 
> <mailto:eran@hueniverse.com>> wrote:
> 
> 
>     I also want to point out that we really need to work on our
>     messaging and perception that URI extension relation type are in any
>     way inferior or "less cool" than the short registered ones. The
>     sooner protocol authors accept this as a perfectly valid choice for
>     their protocol needs, the better the link framework will be.
> 
> 
> I couldn't have said it better myself. Basically what you are saying by 
> requesting a short relation is that you actively intend to share the 
> relation with others with a view to improving interoperability. By using 
> a URI you control you're saying you want it to have a specific, concrete 
> meaning (while retaining the option of sharing). The more I hear the 
> more it sounds like PubSubHubbub wants the latter and with that in mind 
> I would suggest that http://pubsubhubbub.org/ is as good an identifier 
> as any.
> 

I think the main beef that folks have with the URI-shaped rels is that 
they're long and awkward. Why is all that "http://" and "/" noise in 
there? That's only useful if you want to dereference the URI. 
pubsubhubbub.org is enough information for an identifier.

Here are some other examples that would probably be less objectionable:

  * hubbub.hub (OpenID-style protocol.rel naming)
  * org.pubsubhubbub.hub (Java-style .. but I personally find it award 
that these are "backwards" compared to DNS.
  * pubsubhubbub.org:hub (like a tag: URI without the scheme and date)

These things are much less likely to be considered second-class citizens 
if they don't look so daft.


From ieycommand@marcasapone.com  Sun Sep 20 03:21:33 2009
Return-Path: <ieycommand@marcasapone.com>
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 3BF163A698A; Sun, 20 Sep 2009 03:21:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.453
X-Spam-Level: ****
X-Spam-Status: No, score=4.453 tagged_above=-999 required=5 tests=[BAYES_99=3.5, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR=2.426, HELO_EQ_PL=1.135, HOST_EQ_PL=1.95, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_RHS_DOB=1.083, URIBL_SBL=20, URIBL_WS_SURBL=10, 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 EvOx9mvIX8HV; Sun, 20 Sep 2009 03:21:32 -0700 (PDT)
Received: from dynamic-78-8-128-4.ssp.dialog.net.pl (dynamic-78-8-128-4.ssp.dialog.net.pl [78.8.128.4]) by core3.amsl.com (Postfix) with SMTP id 5495C3A682C; Sun, 20 Sep 2009 03:19:48 -0700 (PDT)
Date: Sun, 20 Sep 2009 06:20:49 -0500
Subject: Rep watches models from 2010
From: "Marcelo Bruno" <atompub-archive@megatron.ietf.org>
To: "Davis Gaston" <atompub-archive@megatron.ietf.org>
Message-ID: <1shdhHasIqVvcXDte2atompub-archive@megatron.ietf.org>
Content-Type: text/plain;
Content-Transfer-Encoding: 7Bit

Are you ready for hottest rep watches from 2010? They are here http://tablebring.com/





From owner-atom-syntax@mail.imc.org  Sun Sep 20 09:38:35 2009
Return-Path: <owner-atom-syntax@mail.imc.org>
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 89A973A6972 for <ietfarch-atompub-archive@core3.amsl.com>; Sun, 20 Sep 2009 09:38:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.322
X-Spam-Level: 
X-Spam-Status: No, score=-10.322 tagged_above=-999 required=5 tests=[AWL=-2.277, BAYES_00=-2.599, GB_I_LETTER=-2, HELO_MISMATCH_COM=0.553, 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 TOgsON-F00Be for <ietfarch-atompub-archive@core3.amsl.com>; Sun, 20 Sep 2009 09:38:34 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id C621D28C0DF for <atompub-archive@ietf.org>; Sun, 20 Sep 2009 09:38:34 -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 n8KGUZ0k046311 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 20 Sep 2009 09:30: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 n8KGUZBn046310; Sun, 20 Sep 2009 09:30: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 mail-yw0-f172.google.com (mail-yw0-f172.google.com [209.85.211.172]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n8KGUUim046302 for <atom-syntax@imc.org>; Sun, 20 Sep 2009 09:30:33 -0700 (MST) (envelope-from sayrer@gmail.com)
Received: by ywh2 with SMTP id 2so2972849ywh.27 for <atom-syntax@imc.org>; Sun, 20 Sep 2009 09:30:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=heEKrunqOhNprgA1LJXoTnvAnmoXT6MY8B4F5ExWM0Y=; b=xE4Y8WtEeAhm50wToH7Cn+tMjSQz8WxP0+kR9Bh5h8IKE6IzC6cmyaqKusRzWsvKmT hdjToNZttxD721QZALtYgdwCYI2WcDDb7TMjkYqKQ0oolN52mFGXFeK1EhW4gJ33CXeU 63+gTuGNeeFxSDtcw0ZAwJ8Zq4LJdp34sTt04=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=T6fGVqHw9uvCHjGRjH0W/1tNJZNWZ2gB0mPt/aX15hArje5D5dU3BQJtc5TK+27WPu TJCwKYCpEdzH3Tsfi6H+l9nDiu93Ppb9nQ7TYgXaebQA81jgLzlYCuUol/mpqnnbfD1l DZXECG6LOYgOboc7Cshi7yEIfIiixTQ5fMGWs=
MIME-Version: 1.0
Received: by 10.150.113.13 with SMTP id l13mr6722108ybc.248.1253464230266;  Sun, 20 Sep 2009 09:30:30 -0700 (PDT)
In-Reply-To: <72D0641A-F30F-484C-ADAB-A042AA5E82DD@mnot.net>
References: <ca722a9e0909101030g6ccbc1e2t823f2abd19307bea@mail.gmail.com> <ADAD548E-2E95-4385-A749-7C6D5611D4F1@mnot.net> <21606dcf0909160313m1dcad47dk47c139959edb113d@mail.gmail.com> <966f8bd30909160735r43fd3c48p4059867e34ecd456@mail.gmail.com> <72D0641A-F30F-484C-ADAB-A042AA5E82DD@mnot.net>
Date: Sun, 20 Sep 2009 12:30:30 -0400
Message-ID: <68fba5c50909200930xa35fe76q11bad6b9de394411@mail.gmail.com>
Subject: Re: Input on request for link relation [ w/ proposed modifications to  link draft ]
From: Robert Sayre <sayrer@gmail.com>
To: Mark Nottingham <mnot@mnot.net>
Cc: Brett Slatkin <brett@haxor.com>, Sam Johnston <samj@samj.net>, Lisa Dusseault <lisa.dusseault@gmail.com>, Atom-Syntax Syntax <atom-syntax@imc.org>, ietf-http-wg@w3.org
Content-Type: text/plain; charset=ISO-8859-1
Sender: owner-atom-syntax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/atom-syntax/mail-archive/>
List-Unsubscribe: <mailto:atom-syntax-request@imc.org?body=unsubscribe>
List-ID: <atom-syntax.imc.org>

> Then why are you only bringing it to the attention of the wider world now?
> I don't mean to pick on you, but it seems like there are lots of developers these days
> who are writing protocols in secret, and then expecting the world to come along for the ride,
> no matter how badly they interact with the infrastructure.

I don't think these developers, or anyone else, are under an
obligation to share a proposal with the world before they think it's
ready. It can feel a little like taking dictation when something
rather fully-formed emerges from some company's intranet, but
successful protocols can emerge in many ways, and these developers
appear quite willing to make reasonable changes to their spec (they
had already added RSS before this thread began, iirc).

> As such, I think there's more value in something more capable than specific,
> lest we all drown in a sea of special-purpose, needlessly application-specific protocols.

One example of an unreasonable request would be to suggest that
developers are required to solve a much bigger problem then they've
set out to. In this case, I don't see a reason to apply stop energy.
The PubSubHubbub effort is clearly not going to hurt the Web or the
Internet in general, the link relation namespace is not especially
crowded, and the IETF is free to modify or expand the definition of
the hub relation over time. With that in mind, I don't think the text
of the registration should or will stop people if the proposed
relation turns out to be useful for non-feed media types.

-- 

Robert Sayre

"I would have written a shorter letter, but I did not have the time."


From owner-atom-syntax@mail.imc.org  Sun Sep 20 17:02:02 2009
Return-Path: <owner-atom-syntax@mail.imc.org>
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 85B263A694D for <ietfarch-atompub-archive@core3.amsl.com>; Sun, 20 Sep 2009 17:02:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.763
X-Spam-Level: 
X-Spam-Status: No, score=-6.763 tagged_above=-999 required=5 tests=[AWL=-1.340, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, 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 nrxZu2UMxSqF for <ietfarch-atompub-archive@core3.amsl.com>; Sun, 20 Sep 2009 17:02:01 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 8AEEB3A67F9 for <atompub-archive@ietf.org>; Sun, 20 Sep 2009 17:02:01 -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 n8KNsttB072993 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 20 Sep 2009 16:54:55 -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 n8KNstX8072992; Sun, 20 Sep 2009 16:54:55 -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 eu1sys200aog116.obsmtp.com (eu1sys200aog116.obsmtp.com [207.126.144.141]) by balder-227.proper.com (8.14.2/8.14.2) with SMTP id n8KNsnK7072982 for <atom-syntax@imc.org>; Sun, 20 Sep 2009 16:54:54 -0700 (MST) (envelope-from samj@samj.net)
Received: from source ([209.85.218.216]) by eu1sys200aob116.postini.com ([207.126.147.11]) with SMTP ID DSNKSrbAyHz7QSCfHFdYbOJwQfhRN/ke48sQ@postini.com; Sun, 20 Sep 2009 23:54:54 UTC
Received: by bwz12 with SMTP id 12so2119996bwz.44 for <atom-syntax@imc.org>; Sun, 20 Sep 2009 16:54:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.239.168.144 with SMTP id k16mr311253hbe.103.1253490887609;  Sun, 20 Sep 2009 16:54:47 -0700 (PDT)
In-Reply-To: <4AB6BD9E.40207@sitepen.com>
References: <ca722a9e0909101030g6ccbc1e2t823f2abd19307bea@mail.gmail.com> <ADAD548E-2E95-4385-A749-7C6D5611D4F1@mnot.net> <21606dcf0909160313m1dcad47dk47c139959edb113d@mail.gmail.com> <966f8bd30909160735r43fd3c48p4059867e34ecd456@mail.gmail.com> <72D0641A-F30F-484C-ADAB-A042AA5E82DD@mnot.net> <68fba5c50909200930xa35fe76q11bad6b9de394411@mail.gmail.com> <4AB6BD9E.40207@sitepen.com>
Date: Mon, 21 Sep 2009 01:54:47 +0200
Message-ID: <21606dcf0909201654x7714981cu4af3def35d358bb8@mail.gmail.com>
Subject: Re: Input on request for link relation [ w/ proposed modifications to  link draft ]
From: Sam Johnston <samj@samj.net>
To: Kris Zyp <kris@sitepen.com>
Cc: Robert Sayre <sayrer@gmail.com>, Mark Nottingham <mnot@mnot.net>, Brett Slatkin <brett@haxor.com>, Lisa Dusseault <lisa.dusseault@gmail.com>, Atom-Syntax Syntax <atom-syntax@imc.org>, ietf-http-wg@w3.org
Content-Type: multipart/alternative; boundary=00163649914b15cfc604740b1730
Sender: owner-atom-syntax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/atom-syntax/mail-archive/>
List-Unsubscribe: <mailto:atom-syntax-request@imc.org?body=unsubscribe>
List-ID: <atom-syntax.imc.org>

--00163649914b15cfc604740b1730
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Sep 21, 2009 at 1:41 AM, Kris Zyp <kris@sitepen.com> wrote:

>
> I am not necessarily opposed to the addition of a
> simple/non-namespaced relation, but it still seems like it should be
> necessary to have some the relationship clearly articulated enough to
> delineate between "hub" (or whatever relation name that is used) and
> the existing "monitor" relation. A developer (like me) should be able
> to make an informed selection between the two for other notification
> formats.
>

At the very least, where there are overlapping relations (e.g. prev vs
previous, hub vs monitor, etc.) we should indicate which one is preferred,
perhaps by deprecating the other(s).

I appreciate Robert's concerns however and you can be quite sure that we'll
see more rather than less specs developed behind closed doors before being
unleashed on the world (Google Wave comes to mind). In that case I would
suggest that they supply a URI relation in addition to the proposed short
relation - reference implementations can send the URI and clients can accept
both in the interim.

Whatever we decide the Web Linking draft needs to reflect it (and probably
needs to go to some lengths to explain that URI relations are not evil).

Sam

--00163649914b15cfc604740b1730
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Mon, Sep 21, 2009 at 1:41 AM, Kris Zyp <span dir=3D"ltr">&lt;<a href=3D"=
mailto:kris@sitepen.com">kris@sitepen.com</a>&gt;</span> wrote:<br><div cla=
ss=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class=3D"im"><br>
</div>I am not necessarily opposed to the addition of a<br>
simple/non-namespaced relation, but it still seems like it should be<br>
necessary to have some the relationship clearly articulated enough to<br>
delineate between &quot;hub&quot; (or whatever relation name that is used) =
and<br>
the existing &quot;monitor&quot; relation. A developer (like me) should be =
able<br>
to make an informed selection between the two for other notification<br>
formats.<br>
</blockquote><div><br></div><div>At the very least, where there are overlap=
ping relations (e.g. prev vs previous, hub vs monitor, etc.) we should indi=
cate which one is preferred, perhaps by deprecating the other(s).</div>
<div><br></div><div>I appreciate Robert&#39;s concerns however and you can =
be quite sure that we&#39;ll see more rather than less specs developed behi=
nd closed doors before being unleashed on the world (Google Wave comes to m=
ind). In that case I would suggest that they supply a URI relation in addit=
ion to the proposed short relation - reference implementations can send the=
 URI and clients can accept both in the interim.</div>
<div><br></div><div>Whatever we decide the Web Linking draft needs to refle=
ct it (and probably needs to go to some lengths to explain that URI relatio=
ns are not evil).</div><div><br></div><div>Sam</div><div><br></div></div>

--00163649914b15cfc604740b1730--


From owner-atom-syntax@mail.imc.org  Sun Sep 20 19:14:28 2009
Return-Path: <owner-atom-syntax@mail.imc.org>
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 AB34D3A68BE for <ietfarch-atompub-archive@core3.amsl.com>; Sun, 20 Sep 2009 19:14:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.508
X-Spam-Level: 
X-Spam-Status: No, score=-9.508 tagged_above=-999 required=5 tests=[AWL=-1.462, BAYES_00=-2.599, GB_I_LETTER=-2, HELO_MISMATCH_COM=0.553, 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 s7kJtf+IaTRX for <ietfarch-atompub-archive@core3.amsl.com>; Sun, 20 Sep 2009 19:14:27 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id C1FA83A688B for <atompub-archive@ietf.org>; Sun, 20 Sep 2009 19:14:27 -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 n8L27e5d081234 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 20 Sep 2009 19:07: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 n8L27eqe081233; Sun, 20 Sep 2009 19:07: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 mail-yx0-f196.google.com (mail-yx0-f196.google.com [209.85.210.196]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n8L27VXQ081223 for <atom-syntax@imc.org>; Sun, 20 Sep 2009 19:07:39 -0700 (MST) (envelope-from sayrer@gmail.com)
Received: by yxe34 with SMTP id 34so3281449yxe.16 for <atom-syntax@imc.org>; Sun, 20 Sep 2009 19:07:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=hljZ3Dyk5Eh+YlutacdH7X7awCNS2sAimoa2fIi90aM=; b=QFj7xGfRs07on+0GqHs39JXUY5S5xqFC500+U5Qf1hnvd3mbZ6m1exFV6/tqR8u9Hi HwJIPE2pMQUHTFLIaeIWaqow+00oDSXvYzLkmA954yLa/hswYPT/70M6o1k5e2nr0ytm 2P+0NJ46kbzJfyt8VYHfn8wGlKeOHdvTBeL0U=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=NHmTiaS5Sbu+3/fXr0lP5v9uQj0G0IV76ivFSs7nEIvVyG3DIJfcg8KyBH/NbEBvQM azPcm5j+2Afz1bWigR+iklyiuZ1lynIl4h/YNlb+n/xWHTQOOpETHhW+Oej9ukayHK37 xhjFg35VRlBk0/4RgWQllCo2pdzHjh5sr2ES4=
MIME-Version: 1.0
Received: by 10.150.113.13 with SMTP id l13mr7379632ybc.248.1253498851414;  Sun, 20 Sep 2009 19:07:31 -0700 (PDT)
In-Reply-To: <4AB6BD9E.40207@sitepen.com>
References: <ca722a9e0909101030g6ccbc1e2t823f2abd19307bea@mail.gmail.com> <ADAD548E-2E95-4385-A749-7C6D5611D4F1@mnot.net> <21606dcf0909160313m1dcad47dk47c139959edb113d@mail.gmail.com> <966f8bd30909160735r43fd3c48p4059867e34ecd456@mail.gmail.com> <72D0641A-F30F-484C-ADAB-A042AA5E82DD@mnot.net> <68fba5c50909200930xa35fe76q11bad6b9de394411@mail.gmail.com> <4AB6BD9E.40207@sitepen.com>
Date: Sun, 20 Sep 2009 22:07:31 -0400
Message-ID: <68fba5c50909201907q30ece23bjdbdbc8fc39b9e4a2@mail.gmail.com>
Subject: Re: Input on request for link relation [ w/ proposed modifications to  link draft ]
From: Robert Sayre <sayrer@gmail.com>
To: Kris Zyp <kris@sitepen.com>
Cc: Mark Nottingham <mnot@mnot.net>, Brett Slatkin <brett@haxor.com>, Sam Johnston <samj@samj.net>, Lisa Dusseault <lisa.dusseault@gmail.com>, Atom-Syntax Syntax <atom-syntax@imc.org>, ietf-http-wg@w3.org
Content-Type: text/plain; charset=ISO-8859-1
Sender: owner-atom-syntax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/atom-syntax/mail-archive/>
List-Unsubscribe: <mailto:atom-syntax-request@imc.org?body=unsubscribe>
List-ID: <atom-syntax.imc.org>

On Sun, Sep 20, 2009 at 7:41 PM, Kris Zyp <kris@sitepen.com> wrote:
>
> I am not necessarily opposed to the addition of a
> simple/non-namespaced relation, but it still seems like it should be
> necessary to have some the relationship clearly articulated enough to
> delineate between "hub" (or whatever relation name that is used) and
> the existing "monitor" relation. A developer (like me) should be able
> to make an informed selection between the two for other notification
> formats.

It looks like the "hub" relation might see substantial running code as
well as rough consensus.

At least, that's supposedly one of the good parts of the IETF. The
main bad part is an amoral attitude regarding software patents, to the
point that some Areas operate on the assumption that every participant
has cross-licensed everyone else's patents, so that the industry
status quo is preserved. In the Applications Area, I think an upfront
royalty-free policy should be required (I would be surprised to find
my employer, Mozilla Corporation, disagreeing). When I see patents
filed on penetrating glimpses into the obvious[1], my sympathy for
those suffering tedious namespace arguments suddenly evaporates.

I've changed my position, and I do not support the "hub" relation. If
all of this technology were part of an RF Internet, in letter and
spirit, I feel this group could have a more productive conversation.

[1] http://www.scripting.com/stories/2009/09/17/googleGetsAPatentOnReading.html

-- 

Robert Sayre

"I would have written a shorter letter, but I did not have the time."


From ninfo@alnus.cz  Sun Sep 20 20:35:46 2009
Return-Path: <ninfo@alnus.cz>
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 4F8A43A689C for <ietfarch-atompub-archive@core3.amsl.com>; Sun, 20 Sep 2009 20:35:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -18.731
X-Spam-Level: 
X-Spam-Status: No, score=-18.731 tagged_above=-999 required=5 tests=[BAYES_99=3.5, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, HTML_IMAGE_ONLY_08=1.787, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_1=0.001, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_SORBS_WEB=0.619, RCVD_IN_XBL=3.033, RDNS_NONE=0.1, SARE_HTML_IMG_ONLY=1.666, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_RHS_DOB=1.083, URIBL_WS_SURBL=10, 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 L-0p3Md0lPZc for <ietfarch-atompub-archive@core3.amsl.com>; Sun, 20 Sep 2009 20:35:40 -0700 (PDT)
Received: from ama-assn.org (unknown [95.226.180.154]) by core3.amsl.com (Postfix) with SMTP id 6A4703A67DF for <atompub-archive@lists.ietf.org>; Sun, 20 Sep 2009 20:35:38 -0700 (PDT)
To: <atompub-archive@lists.ietf.org>
Subject: Don't go home now!
From: <atompub-archive@lists.ietf.org>
MIME-Version: 1.0
Importance: High
Content-Type: text/html
Message-Id: <20090921033539.6A4703A67DF@core3.amsl.com>
Date: Sun, 20 Sep 2009 20:35:38 -0700 (PDT)

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=windows-1250">
</HEAD>
<BODY>You'll never see your amorous flag fallen! Try our boosters and let and raise at the right moment!
<a href="http://fitobject.com/" target="_blank">
<img src="http://fitobject.com/dyuwqlk.jpg" border="0" alt="Show picture and go to site now!"></a></BODY></HTML>

From owner-atom-syntax@mail.imc.org  Sun Sep 20 21:12:26 2009
Return-Path: <owner-atom-syntax@mail.imc.org>
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 486063A69CE for <ietfarch-atompub-archive@core3.amsl.com>; Sun, 20 Sep 2009 21:12:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.342
X-Spam-Level: 
X-Spam-Status: No, score=-7.342 tagged_above=-999 required=5 tests=[AWL=-1.296, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, 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 RgI+yNSssqdf for <ietfarch-atompub-archive@core3.amsl.com>; Sun, 20 Sep 2009 21:12:25 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 1356C3A68BC for <atompub-archive@ietf.org>; Sun, 20 Sep 2009 21:12:25 -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 n8L44sSA089191 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 20 Sep 2009 21:04:54 -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 n8L44sHi089190; Sun, 20 Sep 2009 21:04:54 -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 n8L44rEc089184 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <atom-syntax@imc.org>; Sun, 20 Sep 2009 21:04:53 -0700 (MST) (envelope-from mnot@mnot.net)
Received: from [10.194.5.121] (unknown [58.171.230.51]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 78C22509D9; Mon, 21 Sep 2009 00:04:45 -0400 (EDT)
Subject: Re: Input on request for link relation [ w/ proposed modifications to  link draft ]
Mime-Version: 1.0 (Apple Message framework v1076)
Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <966f8bd30909202043w9d558c7r286f5cfed3a8db6e@mail.gmail.com>
Date: Mon, 21 Sep 2009 14:04:38 +1000
Cc: Sam Johnston <samj@samj.net>, Lisa Dusseault <lisa.dusseault@gmail.com>, Atom-Syntax Syntax <atom-syntax@imc.org>, ietf-http-wg@w3.org
Content-Transfer-Encoding: 7bit
Message-Id: <FE0A21D1-80BC-4B42-A00A-6BB6F4C1807A@mnot.net>
References: <ca722a9e0909101030g6ccbc1e2t823f2abd19307bea@mail.gmail.com> <ADAD548E-2E95-4385-A749-7C6D5611D4F1@mnot.net> <21606dcf0909160313m1dcad47dk47c139959edb113d@mail.gmail.com> <966f8bd30909160735r43fd3c48p4059867e34ecd456@mail.gmail.com> <72D0641A-F30F-484C-ADAB-A042AA5E82DD@mnot.net> <966f8bd30909202043w9d558c7r286f5cfed3a8db6e@mail.gmail.com>
To: Brett Slatkin <brett@haxor.com>
X-Mailer: Apple Mail (2.1076)
Sender: owner-atom-syntax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/atom-syntax/mail-archive/>
List-Unsubscribe: <mailto:atom-syntax-request@imc.org?body=unsubscribe>
List-ID: <atom-syntax.imc.org>

Responses inline.

On 21/09/2009, at 1:43 PM, Brett Slatkin wrote:

> Hey Mark,
>
> Thanks for the reply.
>
> On Wed, Sep 16, 2009 at 10:51 PM, Mark Nottingham <mnot@mnot.net>  
> wrote:
>>> In that regard, it's important to note that PubSubHubbub is live for
>>> over 100 *million* feeds as of this writing. It is consumed by  
>>> dozens
>>> of companies and developers from multiple countries. There are
>>> implementations of publisher and subscriber clients in many
>>> programming languages. There are even new companies with private
>>> investment running hubs. We've had the genie out of the bottle  
>>> (since
>>> October 2008) and it's difficult to go back to ask everyone to  
>>> change
>>> things now.
>>
>> Then why are you only bringing it to the attention of the wider  
>> world now? I
>> don't mean to pick on you, but it seems like there are lots of  
>> developers
>> these days who are writing protocols in secret, and then expecting  
>> the world
>> to come along for the ride, no matter how badly they interact with  
>> the
>> infrastructure. Pubsubhubbub (PLEASE come up with a shorter name!)  
>> isn't the
>> worst in this respect by far, but still...
>
> Brad and I have been showing this protocol around for a while. We
> showed it off at an XMPP users group meeting in February
> (http://blog.webhooks.org/2009/02/22/the-great-xmpp-dispute-and-pubsubhubbub/ 
> )
> and multiple blog posts were written about it in the beginning of this
> year (http://tinyurl.com/mjvgy6) around Social Web Foo 2009. I'm not
> hooked into any standards bodies at all; is there some
> protocol-announce mailing list I should have used?

Obviously, I don't read the right blogs. :) Ideally people would have  
communicated this internally inside the IETF as well as in various  
companies that were working on it, but we don't live in that ideal  
world. Ah, well.

The best place to socialise this sort of thing in the IETF is probably  
the apps-discuss list; <https://www.ietf.org/mailman/listinfo/apps-discuss 
 >. In the W3C, it's probably www-talk; <http://lists.w3.org/Archives/Public/www-talk/ 
 >.



>>> So, this is how I would modify your description from before to be  
>>> more
>>> generic:
>>>
>>> Description: A URI for a "hub" (speaking the PubSubHubbub protocol)
>>> that enables clients to register for and publish real-time updates  
>>> to
>>> the resource.
>>>
>>> How does that sound?
>>
>> That's a start. To my mind, you need to:
>>
>> 1. Accommodate things other than Atom feeds in your protocol, if  
>> only by
>> leaving appropriate extension points for addressing it in a future
>> (hopefully soon; lots of people are interested in this, from what  
>> I've seen)
>> revision.
>
> I've opened this bug to track leaving open extensions for future  
> content types:
> http://code.google.com/p/pubsubhubbub/issues/detail?id=71
>
> We need to figure out how discovery will work (possibly XRD?) but I
> think it's doable.
>
>> 2. Publish as an Internet-Draft.
>>
>> The question that this brings to mind for me about the Link draft  
>> is whether
>> this text about registered relations is appropriate:
>>
>> "Relation types that constrain the target IRI or context IRI (e.g.,  
>> to a
>> specific media type) MUST NOT be registered."
>>
>> Obviously, that's pretty open-ended, and generally link relation  
>> types
>> shouldn't specify a media type, if they're to be broadly  
>> applicable, but
>> relations like "hub" that constrain things to specific input and  
>> output
>> formats for *generic* protocols (here, pub/sub) could be an  
>> exception. Read
>> too broadly, and this requirement could even disallow "duplicate"  
>> as we've
>> been discussing on a separate thread.
>>
>> My inclination at this point is to rewrite this as something like:
>>
>> "Registered relation types MUST NOT constrain the media type of the  
>> context
>> IRI, and MUST NOT constrain the available representation media  
>> types of the
>> target IRI. However, they MAY specify the behaviours (e.g., allowable
>> methods, request media types) and constrain the representations of  
>> target
>> resources in other ways."
>>
>> Thoughts?
>
> I like the second description here much more. It's a nice improvement
> on the original language.

Good, I think so too.

> Before PubSubHubbub is made into a
> legitimate internet draft, we'll need a better story for all content
> types (issue 71 filed above).
>
>> Regarding "hub" vs. "monitor" -- this is interesting to me, if not  
>> just
>> because people have been talking about this sort of protocol for  
>> easily more
>> than a decade, and many proposals have already been made*. As such,  
>> I think
>> there's more value in something more capable than specific, lest we  
>> all
>> drown in a sea of special-purpose, needlessly application-specific
>> protocols.
>>
>> That said, I don't think you can use one link relation for both  
>> purposes,
>> because even if they both took the same POST payloads, the further
>> interactions beyond that (the callback to you) would also need to be
>> compatible. While you could use the type attribute to distinguish  
>> between
>> which protocol is in use, that's not really what it's for; the
>> representation returned wouldn't be describing the protocol that  
>> was going
>> to commence.
>
> I can't seem to find any reference to the "monitor" relation type
> anywhere. Could you pass me a link to it?

See:
   http://tools.ietf.org/html/draft-roach-sip-http-subscribe
with a mailing list at:
   https://www.ietf.org/mailman/listinfo/sip-http-events


>> * I'm purposefully limiting my comments here to the impact on the  
>> link
>> relations draft and registry. I have many other thoughts about  
>> pubsubhubbub
>> and how suitable it is to general use; hopefully I'll have time to  
>> convey
>> them separately.
>
> I would really appreciate if you could find the time. I could really
> use some help from you and others who are familiar with the
> standardization process. This is all new to me.

Will do.

Cheers,


--
Mark Nottingham     http://www.mnot.net/


From owner-atom-syntax@mail.imc.org  Mon Sep 21 01:51:54 2009
Return-Path: <owner-atom-syntax@mail.imc.org>
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 8A5143A687D for <ietfarch-atompub-archive@core3.amsl.com>; Mon, 21 Sep 2009 01:51:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.724
X-Spam-Level: 
X-Spam-Status: No, score=-6.724 tagged_above=-999 required=5 tests=[AWL=-1.296, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4, RCVD_IN_SORBS_WEB=0.619]
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 jHHVzA8MNloY for <ietfarch-atompub-archive@core3.amsl.com>; Mon, 21 Sep 2009 01:51:53 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id EF2D03A6814 for <atompub-archive@ietf.org>; Mon, 21 Sep 2009 01:51:52 -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 n8L8hFLk007050 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 21 Sep 2009 01:43:15 -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 n8L8hFMO007049; Mon, 21 Sep 2009 01:43:15 -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-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n8L8h8gF007040 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <atom-syntax@imc.org>; Mon, 21 Sep 2009 01:43:14 -0700 (MST) (envelope-from mnot@mnot.net)
Received: from [10.168.0.87] (unknown [123.208.166.252]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 09C6222E253; Mon, 21 Sep 2009 04:43:02 -0400 (EDT)
Subject: Re: Input on request for link relation
Mime-Version: 1.0 (Apple Message framework v1076)
Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <90C41DD21FB7C64BB94121FBBC2E72343784D58272@P3PW5EX1MB01.EX1.SECURESERVER.NET>
Date: Mon, 21 Sep 2009 18:42:54 +1000
Cc: Brett Slatkin <brett@haxor.com>, Atom-Syntax Syntax <atom-syntax@imc.org>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Content-Transfer-Encoding: 7bit
Message-Id: <6E6CD471-0EF1-4212-BC16-BB1DEF50DA4F@mnot.net>
References: <ca722a9e0909101030g6ccbc1e2t823f2abd19307bea@mail.gmail.com> <ADAD548E-2E95-4385-A749-7C6D5611D4F1@mnot.net> <21606dcf0909160313m1dcad47dk47c139959edb113d@mail.gmail.com> <966f8bd30909160735r43fd3c48p4059867e34ecd456@mail.gmail.com> <90C41DD21FB7C64BB94121FBBC2E72343784D57E5C@P3PW5EX1MB01.EX1.SECURESERVER.NET> <966f8bd30909161803r60be2418pff9ff4bdfcb7125f@mail.gmail.com> <90C41DD21FB7C64BB94121FBBC2E72343784D57E68@P3PW5EX1MB01.EX1.SECURESERVER.NET> <966f8bd30909202315h50007ed8i3df086cd4907b6a6@mail.gmail.com> <90C41DD21FB7C64BB94121FBBC2E72343784D58272@P3PW5EX1MB01.EX1.SECURESERVER.NET>
To: Eran Hammer-Lahav <eran@hueniverse.com>
X-Mailer: Apple Mail (2.1076)
Sender: owner-atom-syntax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/atom-syntax/mail-archive/>
List-Unsubscribe: <mailto:atom-syntax-request@imc.org?body=unsubscribe>
List-ID: <atom-syntax.imc.org>

Also, I think the mitigating factor here is that the hub folks have  
been working on this for a while, and Link isn't approved or an RFC yet.

Cheers,


On 21/09/2009, at 4:44 PM, Eran Hammer-Lahav wrote:

> I'll comment in reverse order...
>
>> -----Original Message-----
>> From: bslatkin@gmail.com [mailto:bslatkin@gmail.com] On Behalf Of  
>> Brett
>> Slatkin
>> Sent: Sunday, September 20, 2009 11:16 PM
>
>> So far, the amount of push-back I've received trying to get into the
>> registry has reinforced the idea that links with the URI extension
>> relation aren't good enough to be accepted as standards.
>
> I am not sure what you mean by this. The pushback here has been  
> mostly about reserving the general term 'hub' to be used exclusively  
> for a single protocol. Can you point me to where statements were  
> made that indicated URI extension relations are not good enough for  
> standards?
>
> In the current working draft for XRD (an OASIS standard proposal) we  
> include a URI extension relation which has specific processing  
> meaning because we felt it was more appropriate than registering  
> something so specific. In WebFinger we decided to use the relation  
> type 'describedby' for resolving (the proposed) acct: URIs but also  
> included an URI extension relation to allow servers to explicitly  
> indicate their support of the protocol. These are two examples (at  
> least one is a proposed standard) for using URI extension relations.
>
>>> * Is anything bad going to happen if someone tries to talk PSHB to  
>>> an
>> endpoint linked as 'hub', which doesn't support it?
>>
>> Probably not.
>>
>>> * Are there currently other protocols likely to use this? Are they
>> likely to operate side by side for the same feed?
>>
>> Hopefully there will be a bunch of companion/extension protocols to
>> the core PubSubHubbub spec that make it function efficiently for all
>> content types. But no, there aren't any other protocols I know of, at
>> this point that would also use this <link> relation. The only other
>> one that comes close is rssCloud, which has its own element in the  
>> RSS
>> namespace.
>
> Given these answers, I don't think there is a problem with  
> registering 'hub' as a relation type (if you can provide a  
> description that does not limit it for a single protocol in a single  
> document type). You can then define in your protocol how clients  
> should behave when they encounter such links.
>
> But again, I just don't understand why rel='http://pubsubhubbub.net'  
> is any lesser than rel='hub'.
>
> EHL
>


--
Mark Nottingham     http://www.mnot.net/


From owner-atom-syntax@mail.imc.org  Mon Sep 21 04:12:09 2009
Return-Path: <owner-atom-syntax@mail.imc.org>
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 DA8253A6825 for <ietfarch-atompub-archive@core3.amsl.com>; Mon, 21 Sep 2009 04:12:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.722
X-Spam-Level: 
X-Spam-Status: No, score=-6.722 tagged_above=-999 required=5 tests=[AWL=-1.299, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, 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 MYkyUFO2p2PE for <ietfarch-atompub-archive@core3.amsl.com>; Mon, 21 Sep 2009 04:12:08 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id E0FD83A67E7 for <atompub-archive@ietf.org>; Mon, 21 Sep 2009 04:12:07 -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 n8LB507x017435 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 21 Sep 2009 04:05:00 -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 n8LB50tq017428; Mon, 21 Sep 2009 04:05:00 -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 eu1sys200aog114.obsmtp.com (eu1sys200aog114.obsmtp.com [207.126.144.137]) by balder-227.proper.com (8.14.2/8.14.2) with SMTP id n8LB4l16017410 for <atom-syntax@imc.org>; Mon, 21 Sep 2009 04:04:55 -0700 (MST) (envelope-from samj@samj.net)
Received: from source ([209.85.220.223]) by eu1sys200aob114.postini.com ([207.126.147.11]) with SMTP ID DSNKSrddz52j0FKiJOeyYbXVoZhJSvxX/YHg@postini.com; Mon, 21 Sep 2009 11:04:55 UTC
Received: by fxm23 with SMTP id 23so2031892fxm.30 for <atom-syntax@imc.org>; Mon, 21 Sep 2009 04:04:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.239.145.165 with SMTP id s37mr334012hba.43.1253531085813; Mon,  21 Sep 2009 04:04:45 -0700 (PDT)
In-Reply-To: <6E6CD471-0EF1-4212-BC16-BB1DEF50DA4F@mnot.net>
References: <ca722a9e0909101030g6ccbc1e2t823f2abd19307bea@mail.gmail.com> <ADAD548E-2E95-4385-A749-7C6D5611D4F1@mnot.net> <21606dcf0909160313m1dcad47dk47c139959edb113d@mail.gmail.com> <966f8bd30909160735r43fd3c48p4059867e34ecd456@mail.gmail.com> <90C41DD21FB7C64BB94121FBBC2E72343784D57E5C@P3PW5EX1MB01.EX1.SECURESERVER.NET> <966f8bd30909161803r60be2418pff9ff4bdfcb7125f@mail.gmail.com> <90C41DD21FB7C64BB94121FBBC2E72343784D57E68@P3PW5EX1MB01.EX1.SECURESERVER.NET> <966f8bd30909202315h50007ed8i3df086cd4907b6a6@mail.gmail.com> <90C41DD21FB7C64BB94121FBBC2E72343784D58272@P3PW5EX1MB01.EX1.SECURESERVER.NET> <6E6CD471-0EF1-4212-BC16-BB1DEF50DA4F@mnot.net>
Date: Mon, 21 Sep 2009 13:04:45 +0200
Message-ID: <21606dcf0909210404o6f3cd749wea3f53cf6fcbec9c@mail.gmail.com>
Subject: Re: Input on request for link relation
From: Sam Johnston <samj@samj.net>
To: Mark Nottingham <mnot@mnot.net>
Cc: Eran Hammer-Lahav <eran@hueniverse.com>, Brett Slatkin <brett@haxor.com>, Atom-Syntax Syntax <atom-syntax@imc.org>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Content-Type: multipart/alternative; boundary=001485f6d2f015ba5d047414738c
Sender: owner-atom-syntax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/atom-syntax/mail-archive/>
List-Unsubscribe: <mailto:atom-syntax-request@imc.org?body=unsubscribe>
List-ID: <atom-syntax.imc.org>

--001485f6d2f015ba5d047414738c
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Sep 21, 2009 at 10:42 AM, Mark Nottingham <mnot@mnot.net> wrote:

> Also, I think the mitigating factor here is that the hub folks have been
> working on this for a while, and Link isn't approved or an RFC yet.


Which reminds me... a number of drafts have already resulted in the creation
of IANA registries <http://www.iana.org/protocols/>. Perhaps it would be
sensible to do the same while we refine the Web Linking draft? Is it still
possible?

Sam

On 21/09/2009, at 4:44 PM, Eran Hammer-Lahav wrote:
>
>  I'll comment in reverse order...
>>
>>  -----Original Message-----
>>> From: bslatkin@gmail.com [mailto:bslatkin@gmail.com] On Behalf Of Brett
>>> Slatkin
>>> Sent: Sunday, September 20, 2009 11:16 PM
>>>
>>
>>  So far, the amount of push-back I've received trying to get into the
>>> registry has reinforced the idea that links with the URI extension
>>> relation aren't good enough to be accepted as standards.
>>>
>>
>> I am not sure what you mean by this. The pushback here has been mostly
>> about reserving the general term 'hub' to be used exclusively for a single
>> protocol. Can you point me to where statements were made that indicated URI
>> extension relations are not good enough for standards?
>>
>> In the current working draft for XRD (an OASIS standard proposal) we
>> include a URI extension relation which has specific processing meaning
>> because we felt it was more appropriate than registering something so
>> specific. In WebFinger we decided to use the relation type 'describedby' for
>> resolving (the proposed) acct: URIs but also included an URI extension
>> relation to allow servers to explicitly indicate their support of the
>> protocol. These are two examples (at least one is a proposed standard) for
>> using URI extension relations.
>>
>>  * Is anything bad going to happen if someone tries to talk PSHB to an
>>>>
>>> endpoint linked as 'hub', which doesn't support it?
>>>
>>> Probably not.
>>>
>>>  * Are there currently other protocols likely to use this? Are they
>>>>
>>> likely to operate side by side for the same feed?
>>>
>>> Hopefully there will be a bunch of companion/extension protocols to
>>> the core PubSubHubbub spec that make it function efficiently for all
>>> content types. But no, there aren't any other protocols I know of, at
>>> this point that would also use this <link> relation. The only other
>>> one that comes close is rssCloud, which has its own element in the RSS
>>> namespace.
>>>
>>
>> Given these answers, I don't think there is a problem with registering
>> 'hub' as a relation type (if you can provide a description that does not
>> limit it for a single protocol in a single document type). You can then
>> define in your protocol how clients should behave when they encounter such
>> links.
>>
>> But again, I just don't understand why rel='http://pubsubhubbub.net' is
>> any lesser than rel='hub'.
>>
>> EHL
>>
>>
>
>

> --
> Mark Nottingham     http://www.mnot.net/
>
>
>

--001485f6d2f015ba5d047414738c
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Mon, Sep 21, 2009 at 10:42 AM, Mark Nottingham <span dir=3D"ltr">&lt;<a =
href=3D"mailto:mnot@mnot.net">mnot@mnot.net</a>&gt;</span> wrote:<br><div c=
lass=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 =
0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Also, I think the mitigating factor here is that the hub folks have been wo=
rking on this for a while, and Link isn&#39;t approved or an RFC yet.</bloc=
kquote><div><br></div><div>Which reminds me... a number of drafts have alre=
ady resulted in the creation of <a href=3D"http://www.iana.org/protocols/">=
IANA registries</a>. Perhaps it would be sensible to do the same while we r=
efine the Web Linking draft? Is it still possible?</div>
<div><br></div><div>Sam</div><div><br></div><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"=
><div><div class=3D"h5">
On 21/09/2009, at 4:44 PM, Eran Hammer-Lahav wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
I&#39;ll comment in reverse order...<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
-----Original Message-----<br>
From: <a href=3D"mailto:bslatkin@gmail.com" target=3D"_blank">bslatkin@gmai=
l.com</a> [mailto:<a href=3D"mailto:bslatkin@gmail.com" target=3D"_blank">b=
slatkin@gmail.com</a>] On Behalf Of Brett<br>
Slatkin<br>
Sent: Sunday, September 20, 2009 11:16 PM<br>
</blockquote>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
So far, the amount of push-back I&#39;ve received trying to get into the<br=
>
registry has reinforced the idea that links with the URI extension<br>
relation aren&#39;t good enough to be accepted as standards.<br>
</blockquote>
<br>
I am not sure what you mean by this. The pushback here has been mostly abou=
t reserving the general term &#39;hub&#39; to be used exclusively for a sin=
gle protocol. Can you point me to where statements were made that indicated=
 URI extension relations are not good enough for standards?<br>

<br>
In the current working draft for XRD (an OASIS standard proposal) we includ=
e a URI extension relation which has specific processing meaning because we=
 felt it was more appropriate than registering something so specific. In We=
bFinger we decided to use the relation type &#39;describedby&#39; for resol=
ving (the proposed) acct: URIs but also included an URI extension relation =
to allow servers to explicitly indicate their support of the protocol. Thes=
e are two examples (at least one is a proposed standard) for using URI exte=
nsion relations.<br>

<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
* Is anything bad going to happen if someone tries to talk PSHB to an<br>
</blockquote>
endpoint linked as &#39;hub&#39;, which doesn&#39;t support it?<br>
<br>
Probably not.<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
* Are there currently other protocols likely to use this? Are they<br>
</blockquote>
likely to operate side by side for the same feed?<br>
<br>
Hopefully there will be a bunch of companion/extension protocols to<br>
the core PubSubHubbub spec that make it function efficiently for all<br>
content types. But no, there aren&#39;t any other protocols I know of, at<b=
r>
this point that would also use this &lt;link&gt; relation. The only other<b=
r>
one that comes close is rssCloud, which has its own element in the RSS<br>
namespace.<br>
</blockquote>
<br>
Given these answers, I don&#39;t think there is a problem with registering =
&#39;hub&#39; as a relation type (if you can provide a description that doe=
s not limit it for a single protocol in a single document type). You can th=
en define in your protocol how clients should behave when they encounter su=
ch links.<br>

<br>
But again, I just don&#39;t understand why rel=3D&#39;<a href=3D"http://pub=
subhubbub.net" target=3D"_blank">http://pubsubhubbub.net</a>&#39; is any le=
sser than rel=3D&#39;hub&#39;.<br>
<br>
EHL<br>
<br>
</blockquote>
<br>
<br></div></div><div><div></div><div class=3D"h5">
</div></div></blockquote><div>=A0</div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div=
><div class=3D"h5">--<br>
Mark Nottingham =A0 =A0 <a href=3D"http://www.mnot.net/" target=3D"_blank">=
http://www.mnot.net/</a><br>
<br>
<br>
</div></div></blockquote></div><br>

--001485f6d2f015ba5d047414738c--


From owner-atom-syntax@mail.imc.org  Mon Sep 21 10:04:22 2009
Return-Path: <owner-atom-syntax@mail.imc.org>
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 D94323A698C for <ietfarch-atompub-archive@core3.amsl.com>; Mon, 21 Sep 2009 10:04:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.237
X-Spam-Level: 
X-Spam-Status: No, score=-9.237 tagged_above=-999 required=5 tests=[AWL=-1.191, BAYES_00=-2.599, GB_I_LETTER=-2, HELO_MISMATCH_COM=0.553, 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 dPWViEAZwSzm for <ietfarch-atompub-archive@core3.amsl.com>; Mon, 21 Sep 2009 10:04:21 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id D599D3A6809 for <atompub-archive@ietf.org>; Mon, 21 Sep 2009 10:04: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 n8LGsgJB043903 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 21 Sep 2009 09:54:42 -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 n8LGsgYD043902; Mon, 21 Sep 2009 09:54:42 -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 mail-yw0-f195.google.com (mail-yw0-f195.google.com [209.85.211.195]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n8LGsXaW043881 for <atom-syntax@imc.org>; Mon, 21 Sep 2009 09:54:40 -0700 (MST) (envelope-from sayrer@gmail.com)
Received: by ywh33 with SMTP id 33so3890596ywh.18 for <atom-syntax@imc.org>; Mon, 21 Sep 2009 09:54:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=vy9JdxrmWPptlIzQYoiSN4TnHMj5xKx85Ds40IGbXx8=; b=rOrhK+oyUuQ4ofVRQ7DF0HJ8qi3DBGgQj0ZsI4Iplb3WVRI54DlLF2+aC/F/3JGVwB 0smRo82qvY/G2pCbpm117+L/HrgLDOc1VGmQH5UsbMrpFjIahtGYIV7+mt0c6zRwKMhA ho3EwO3nxaorgoQb/gEWc5m2ZGRewKwfBnIiY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=DalkPAoDujQ1sjgsOsNgDp+Ye0I5cd/C9YObPbzpqJCSs+r8OGrzLwtmSuLe8oj2La KRvbWVMDWeiKx73XRcnYX4kLRqdqgE4REwx0rIQ/L679rdNLhM+oQn29eXzfDrlVeSfE 5/7lLrbTjeUlw0PW16n4MHfgCTZYqW+gzUPHY=
MIME-Version: 1.0
Received: by 10.150.175.20 with SMTP id x20mr8624353ybe.268.1253552073396;  Mon, 21 Sep 2009 09:54:33 -0700 (PDT)
In-Reply-To: <966f8bd30909202100s3767db8ck51fcc088470f99f4@mail.gmail.com>
References: <ca722a9e0909101030g6ccbc1e2t823f2abd19307bea@mail.gmail.com> <ADAD548E-2E95-4385-A749-7C6D5611D4F1@mnot.net> <21606dcf0909160313m1dcad47dk47c139959edb113d@mail.gmail.com> <966f8bd30909160735r43fd3c48p4059867e34ecd456@mail.gmail.com> <72D0641A-F30F-484C-ADAB-A042AA5E82DD@mnot.net> <68fba5c50909200930xa35fe76q11bad6b9de394411@mail.gmail.com> <4AB6BD9E.40207@sitepen.com> <68fba5c50909201907q30ece23bjdbdbc8fc39b9e4a2@mail.gmail.com> <966f8bd30909202100s3767db8ck51fcc088470f99f4@mail.gmail.com>
Date: Mon, 21 Sep 2009 12:54:33 -0400
Message-ID: <68fba5c50909210954n79685b46u179dc29a5671baf4@mail.gmail.com>
Subject: Re: Input on request for link relation [ w/ proposed modifications to  link draft ]
From: Robert Sayre <sayrer@gmail.com>
To: Brett Slatkin <brett@haxor.com>
Cc: Kris Zyp <kris@sitepen.com>, Mark Nottingham <mnot@mnot.net>, Sam Johnston <samj@samj.net>, Lisa Dusseault <lisa.dusseault@gmail.com>, Atom-Syntax Syntax <atom-syntax@imc.org>, ietf-http-wg@w3.org
Content-Type: text/plain; charset=ISO-8859-1
Sender: owner-atom-syntax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/atom-syntax/mail-archive/>
List-Unsubscribe: <mailto:atom-syntax-request@imc.org?body=unsubscribe>
List-ID: <atom-syntax.imc.org>

On Mon, Sep 21, 2009 at 12:33 AM, Brett Slatkin <brett@haxor.com> wrote:
>
> The whole point of PubSubHubbub is to be an open protocol, free of
> patents, that anyone can use. We're going to release it under the
> license coming out of the Open Web Foundation
> (http://openwebfoundation.org/) once that's ready (I hear drafts are
> very far along).

Then it sounds like my objection will be moot, once the license is
ready. It is only my objection--the IETF is totally patent agnostic.
Perhaps you can get enough support anyway. The technical bits seem
reasonable, and the SIP thing looks like a sideshow to me. :)

> It's obvious that any patent on this technology is invalid

It's not prudent to assume that obviousness will stop the patent
process, unfortunately.

>
> I find it frustrating that you're lumping me, Brad, Martin, and this
> spec together with some patent we had nothing to do with. We're trying
> to do good here and help the web. I'd appreciate it if you could
> recognize the level of effort we're putting into this, into being
> open, and into reaching a consensus.

It's not personal--I don't think you guys have anything to do with
filing patents. However, I want a Web free from the toxic legal
environment that plagues other parts of the IETF and standards bodies
in general. That environment stifles innovation and privileges the
status quo. If the OWF turns out well, then there is no objection from
me. It's too bad that IPR behavior in this space has forced me to side
with those making what I think are otherwise unfair criticisms.

-- 

Robert Sayre

"I would have written a shorter letter, but I did not have the time."


From owner-atom-syntax@mail.imc.org  Mon Sep 21 16:20:22 2009
Return-Path: <owner-atom-syntax@mail.imc.org>
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 DA34C28C113 for <ietfarch-atompub-archive@core3.amsl.com>; Mon, 21 Sep 2009 16:20:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.823
X-Spam-Level: 
X-Spam-Status: No, score=-4.823 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, 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 VKPXS3ixppoM for <ietfarch-atompub-archive@core3.amsl.com>; Mon, 21 Sep 2009 16:20:22 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 14DD63A68BB for <atompub-archive@ietf.org>; Mon, 21 Sep 2009 16:20:22 -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 n8LNDhPv069779 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 21 Sep 2009 16:13:43 -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 n8LNDhCH069778; Mon, 21 Sep 2009 16:13:43 -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 mail-yx0-f196.google.com (mail-yx0-f196.google.com [209.85.210.196]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n8LNDfP6069772 for <atom-syntax@imc.org>; Mon, 21 Sep 2009 16:13:42 -0700 (MST) (envelope-from bobwyman@gmail.com)
Received: by yxe34 with SMTP id 34so4261860yxe.16 for <atom-syntax@imc.org>; Mon, 21 Sep 2009 16:13:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type; bh=iMu4b1GknZto/q/77diTfMVZgaE5rF7AyhicOZg8sgo=; b=sn8lH6IFLC0dOH2EetXNMpsqKMI4FPsChvKKo+zGkUdg6bnyGZ6+BQ2mYbagTtQisN 0aGYL6EG6aCVIacW0JENjQKUkK1TdIDwBuBBVPdJ1/k/8L0scjJ+cKnozd8cI0kARje3 HQS5lqQGXtRSwImYMfK9fmShD7vFBZv5ae8bY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=dii8Wq2JzONB4IUpTZ9aImKREkF49iKEuMCxTJCETg1ljb5Dh3yHsPQIP5MvHP20QK Fb5AZKUodGHnqE1EXmeu5Na6oEUuXePKPsrDhT6knY7vQgC9Pdzd4N2QQo71+tKrm+Lf TvdEICwebZJeH1JAPqmBTsoXC1Stjdt/m4tCE=
MIME-Version: 1.0
Received: by 10.101.98.9 with SMTP id a9mr240766anm.160.1253574821045; Mon, 21  Sep 2009 16:13:41 -0700 (PDT)
In-Reply-To: <4A2D939C.9040609@gmail.com>
References: <4A2D939C.9040609@gmail.com>
Date: Mon, 21 Sep 2009 19:13:40 -0400
X-Google-Sender-Auth: d81e6a4fb64ecea6
Message-ID: <45be5cd40909211613m4e10a912t60a2800f101c29b9@mail.gmail.com>
Subject: Re: Atom Tombstones Draft Revitalized
From: Bob Wyman <bob@wyman.us>
To: James M Snell <jasnell@gmail.com>
Cc: atom-syntax <atom-syntax@imc.org>
Content-Type: multipart/alternative; boundary=001636ed6a6be8672804741ea13e
Sender: owner-atom-syntax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/atom-syntax/mail-archive/>
List-Unsubscribe: <mailto:atom-syntax-request@imc.org?body=unsubscribe>
List-ID: <atom-syntax.imc.org>

--001636ed6a6be8672804741ea13e
Content-Type: text/plain; charset=ISO-8859-1

Why isn't a deleted-entry more like an entry?
More specifically,

   - The fact that deleted-entry can't have an atom:source makes it very
   difficult to propagate these things in synthetic or aggregated feeds.
   - Lack of support for signatures also makes it difficult to use these
   things with synthetic feeds and eliminates at least one mechanism (although
   probably not a popular one) for guarding against fake deletions.

bob wyman

On Mon, Jun 8, 2009 at 6:41 PM, James M Snell <jasnell@gmail.com> wrote:

>
> As requested, the Atom Tombstones draft has been revitalized.
>
>  http://www.ietf.org/internet-drafts/draft-snell-atompub-tombstones-06.txt
>
> Changed this from Experimental to Informational and updated the IPR
> boilerplate.
>
> - James
>
>

--001636ed6a6be8672804741ea13e
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Why isn&#39;t a deleted-entry more like an entry?<br>More specifically, <br=
><ul><li>The fact that deleted-entry can&#39;t have an atom:source makes it=
 very difficult to propagate these things in synthetic or aggregated feeds.=
</li>
<li>Lack of support for signatures also makes it difficult to use these thi=
ngs with synthetic feeds and eliminates at least one mechanism (although pr=
obably not a popular one) for guarding against fake deletions.</li></ul>
bob wyman<br><br><div class=3D"gmail_quote">On Mon, Jun 8, 2009 at 6:41 PM,=
 James M Snell <span dir=3D"ltr">&lt;<a href=3D"mailto:jasnell@gmail.com">j=
asnell@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote"=
 style=3D"border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.=
8ex; padding-left: 1ex;">
<br>
As requested, the Atom Tombstones draft has been revitalized.<br>
<br>
=A0<a href=3D"http://www.ietf.org/internet-drafts/draft-snell-atompub-tombs=
tones-06.txt" target=3D"_blank">http://www.ietf.org/internet-drafts/draft-s=
nell-atompub-tombstones-06.txt</a><br>
<br>
Changed this from Experimental to Informational and updated the IPR boilerp=
late.<br><font color=3D"#888888">
<br>
- James<br>
<br>
</font></blockquote></div><br>

--001636ed6a6be8672804741ea13e--


From maroonb734@ishiya.com  Mon Sep 21 16:37:37 2009
Return-Path: <maroonb734@ishiya.com>
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 141043A67F0; Mon, 21 Sep 2009 16:37:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.47
X-Spam-Level: ****
X-Spam-Status: No, score=4.47 tagged_above=-999 required=5 tests=[BAYES_99=3.5, DIET_1=0.083, FH_FAKE_RCVD_LINE=10.357, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, FM_DDDD_TIMES_2=1.999, FS_WEIGHT_LOSS=2.134, HELO_DYNAMIC_HCC=4.295, HELO_DYNAMIC_IPADDR2=4.395, HELO_EQ_BR=0.955, HELO_EQ_DSL=1.129, HELO_EQ_TELESP=1.245, HOST_EQ_BR=1.295, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_DOUBLE_IP_SPAM=3.798, 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, SARE_RECV_IP_FROMIP1=1.666, SARE_RECV_SPAM_DOMN02=1.666, TVD_RCVD_IP=1.931, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_SBL=20, 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 xhmnaoDk-rue; Mon, 21 Sep 2009 16:37:36 -0700 (PDT)
Received: from 201-43-223-30.dsl.telesp.net.br (201-43-223-30.dsl.telesp.net.br [201.43.223.30]) by core3.amsl.com (Postfix) with ESMTP id 9DEBC3A693C; Mon, 21 Sep 2009 16:37:34 -0700 (PDT)
Received: from 201.43.223.30 by 122.1.231.153; Mon, 21 Sep 2009 20:37:21 -0300
Message-ID: <000d01ca3b14$77257a50$6400a8c0@maroonb734>
From: Lara Fleming <atompub-archive@megatron.ietf.org>
To: <atompub-archive@megatron.ietf.org>
Subject: weight loss solution of the century try it now free
Date: Mon, 21 Sep 2009 20:37:21 -0300
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0007_01CA3B14.77257A50"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106

This is a multi-part message in MIME format.

------=_NextPart_000_0007_01CA3B14.77257A50
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Whenever you are feeling down because of your appearance, click and see for=
 free.
&nbsp;
Freedom at last, I can squeeze but feel great too...click
=A0
Ring the bell here
------=_NextPart_000_0007_01CA3B14.77257A50
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1"=
>
<META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV align=3Dleft><FONT color=3D#008000=20
face=3D"Comic Sans MS">Whenever you are feeling down because of your appear=
ance, click and see for free.</FONT></DIV>
<DIV align=3Dleft><FONT size=3D2=20
face=3D"Comic Sans MS"><STRONG></STRONG></FONT>&nbsp;</DIV>
<DIV align=3Dleft><FONT color=3D#ff0000 size=3D2=20
face=3D"Comic Sans MS"><STRONG>Freedom at last, I can squeeze but feel grea=
t too...click</STRONG></FONT></DIV>
<DIV align=3Dleft><STRONG><FONT color=3D#ff0000 size=3D2=20
face=3D"Comic Sans MS"></FONT></STRONG>=A0</DIV>
<DIV align=3Dleft><STRONG><FONT color=3D#0000ff size=3D2 face=3DVerdana><A=20
href=3D"http://iojcexwe.cn">Ring the bell here</A></FONT></STRONG></DIV>
</BODY></HTML>

------=_NextPart_000_0007_01CA3B14.77257A50--


From owner-atom-syntax@mail.imc.org  Mon Sep 21 18:26:11 2009
Return-Path: <owner-atom-syntax@mail.imc.org>
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 EF45E3A696F for <ietfarch-atompub-archive@core3.amsl.com>; Mon, 21 Sep 2009 18:26:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.424
X-Spam-Level: 
X-Spam-Status: No, score=-5.424 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HELO_MISMATCH_COM=0.553, 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 xQWG2uYYUP-n for <ietfarch-atompub-archive@core3.amsl.com>; Mon, 21 Sep 2009 18:26:11 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 15A303A696C for <atompub-archive@ietf.org>; Mon, 21 Sep 2009 18:26:10 -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 n8M1KC4t076419 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 21 Sep 2009 18:20:12 -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 n8M1KCdu076418; Mon, 21 Sep 2009 18:20:12 -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 mail-iw0-f185.google.com (mail-iw0-f185.google.com [209.85.223.185]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n8M1K6Dl076407 for <atom-syntax@imc.org>; Mon, 21 Sep 2009 18:20:12 -0700 (MST) (envelope-from ed.summers@gmail.com)
Received: by iwn15 with SMTP id 15so1929115iwn.27 for <atom-syntax@imc.org>; Mon, 21 Sep 2009 18:20:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type; bh=DKirMH8WS2RFfHDc5aqp3bjFl0qplBBSbw7Fwbj0wRk=; b=YHMHbXS3ahjm98otqQArwDfJF90xmwkEb6hf+y5khI3fzlOfqX6zHjAs/ri77WVJSZ r57DutNOEAepuMwMDDSgiGdO5j+oZe9EJVZ6bkUuVNH5mbsEGA9+imAthO4afMJRSDeF nOAOJD3pygmGUcTYtCdlGl5/xabYjohZlX4Ys=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=SpqZf0SoqHlX/W36pDszJGvaw06CbML7dYr9yGsJHOTROILFrXaXWsRu41GKJINUtw SEdFdaG+H7gfGCtNxcf8ZU/PpHO+8L155f3Q0yGLYLFK6FbXK9ESsEde0vKoc4kJ/WKs F7yPF95xLTxKxf/qfL1d4tXPSblZ3jzHzxMhk=
MIME-Version: 1.0
Received: by 10.231.120.88 with SMTP id c24mr605258ibr.49.1253582405373; Mon,  21 Sep 2009 18:20:05 -0700 (PDT)
In-Reply-To: <45be5cd40909211613m4e10a912t60a2800f101c29b9@mail.gmail.com>
References: <4A2D939C.9040609@gmail.com> <45be5cd40909211613m4e10a912t60a2800f101c29b9@mail.gmail.com>
Date: Mon, 21 Sep 2009 21:20:05 -0400
X-Google-Sender-Auth: 66e95e703bf126ff
Message-ID: <f032cc060909211820x503202c4w7ba1b73d04273600@mail.gmail.com>
Subject: Re: Atom Tombstones Draft Revitalized
From: Ed Summers <ehs@pobox.com>
To: atom-syntax <atom-syntax@imc.org>
Content-Type: text/plain; charset=ISO-8859-1
Sender: owner-atom-syntax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/atom-syntax/mail-archive/>
List-Unsubscribe: <mailto:atom-syntax-request@imc.org?body=unsubscribe>
List-ID: <atom-syntax.imc.org>

Just fyi, we are using Tombstones as part of the id.loc.gov service at
the Library of Congress to keep people informed about new, updated and
deleted resources in the Library of Congress Subject Headings. For
example you should find a <deleted-entry> here:

  http://id.loc.gov/authorities/feed/page/2/

//Ed


From makiko-ohnoki@agc.co.jp  Tue Sep 22 07:09:31 2009
Return-Path: <makiko-ohnoki@agc.co.jp>
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 9507C3A6A25 for <ietfarch-atompub-archive@core3.amsl.com>; Tue, 22 Sep 2009 07:09:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -13.592
X-Spam-Level: 
X-Spam-Status: No, score=-13.592 tagged_above=-999 required=5 tests=[BAYES_99=3.5, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR=2.426, HTML_IMAGE_ONLY_08=1.787, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_1=0.001, IP_NOT_FRIENDLY=0.334, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, 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, SARE_HTML_IMG_ONLY=1.666, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_WS_SURBL=10, 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 aGCG8y3LbFGf for <ietfarch-atompub-archive@core3.amsl.com>; Tue, 22 Sep 2009 07:09:22 -0700 (PDT)
Received: from c-69-249-193-206.hsd1.nj.comcast.net (c-69-249-193-206.hsd1.nj.comcast.net [69.249.193.206]) by core3.amsl.com (Postfix) with SMTP id 0A7D43A699D for <atompub-archive@lists.ietf.org>; Tue, 22 Sep 2009 07:09:18 -0700 (PDT)
To: <atompub-archive@lists.ietf.org>
Subject: Let it be firmer!
From: <atompub-archive@lists.ietf.org>
MIME-Version: 1.0
Importance: High
Content-Type: text/html
Message-Id: <20090922140919.0A7D43A699D@core3.amsl.com>
Date: Tue, 22 Sep 2009 07:09:18 -0700 (PDT)

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-2">
</HEAD>
<BODY>Providing her with a high voltage of your desire! This is what you gonna do tonight!
<a href="http://wheelzest.com/" target="_blank">
<img src="http://wheelzest.com/dyuwqlk.jpg" border="0" alt="Show picture and go to site now!"></a></BODY></HTML>

From katheryn@alexanders.ca  Wed Sep 23 03:03:57 2009
Return-Path: <katheryn@alexanders.ca>
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 026B63A67B3 for <ietfarch-atompub-archive@core3.amsl.com>; Wed, 23 Sep 2009 03:03:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -23.447
X-Spam-Level: 
X-Spam-Status: No, score=-23.447 tagged_above=-999 required=5 tests=[AWL=-6.441, BAYES_99=3.5, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_IMAGE_ONLY_08=1.787, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_1=0.001, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RCVD_IN_SORBS_WEB=0.619, RCVD_IN_XBL=3.033, RDNS_NONE=0.1, SARE_HTML_IMG_ONLY=1.666, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_RHS_DOB=1.083, URIBL_WS_SURBL=10, 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 eQlqTXfnoQDk for <ietfarch-atompub-archive@core3.amsl.com>; Wed, 23 Sep 2009 03:03:50 -0700 (PDT)
Received: from accenture.com (unknown [122.169.24.30]) by core3.amsl.com (Postfix) with SMTP id E302E3A6842 for <atompub-archive@lists.ietf.org>; Wed, 23 Sep 2009 03:03:48 -0700 (PDT)
To: <atompub-archive@lists.ietf.org>
Subject: Can't you answer the call?
From: <atompub-archive@lists.ietf.org>
MIME-Version: 1.0
Importance: High
Content-Type: text/html
Message-Id: <20090923100348.E302E3A6842@core3.amsl.com>
Date: Wed, 23 Sep 2009 03:03:48 -0700 (PDT)

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-2">
</HEAD>
<BODY>Improving your lover's characteristics and as a result, your self-respect!
<a href="http://answerchord.com/" target="_blank">
<img src="http://answerchord.com/dyuwqlk.jpg" border="0" alt="Show picture and go to site now!"></a></BODY></HTML>

From jfbequet@r-zakka.com  Wed Sep 23 05:09:09 2009
Return-Path: <jfbequet@r-zakka.com>
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 7964E3A692C; Wed, 23 Sep 2009 05:09:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.888
X-Spam-Level: 
X-Spam-Status: No, score=-6.888 tagged_above=-999 required=5 tests=[BAYES_99=3.5, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_SORBS_WEB=0.619, RCVD_IN_XBL=3.033, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_SBL=20, URIBL_WS_SURBL=10, 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 9mE7oJVyHnXA; Wed, 23 Sep 2009 05:09:08 -0700 (PDT)
Received: from correo.pereira.gov.co (correo.pereira.gov.co [201.236.221.244]) by core3.amsl.com (Postfix) with SMTP id 2B6873A68DB; Wed, 23 Sep 2009 05:08:48 -0700 (PDT)
Date: Wed, 23 Sep 2009 08:09:28 -0500
Subject: Rep watches models from 2010
From: "Margo Cain" <9l@megatron.ietf.org>
To: "Walter Harden" <9l@megatron.ietf.org>
Message-ID: <7oqNTEAKOshvtaPHF9hU9l@megatron.ietf.org>
Content-Type: text/plain;
Content-Transfer-Encoding: 7Bit

Are you ready for hottest rep watches from 2010? They are here http://tablebring.com/





From kamio@agate.plala.or.jp  Wed Sep 23 11:49:27 2009
Return-Path: <kamio@agate.plala.or.jp>
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 5C2823A67CC for <ietfarch-atompub-archive@core3.amsl.com>; Wed, 23 Sep 2009 11:49:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -22.473
X-Spam-Level: 
X-Spam-Status: No, score=-22.473 tagged_above=-999 required=5 tests=[BAYES_99=3.5, HELO_EQ_BR=0.955, HOST_EQ_BR=1.295, HTML_IMAGE_ONLY_08=1.787, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_1=0.001, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, SARE_HTML_IMG_ONLY=1.666, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_RHS_DOB=1.083, URIBL_WS_SURBL=10, 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 TqOZY2+16k+2 for <ietfarch-atompub-archive@core3.amsl.com>; Wed, 23 Sep 2009 11:49:21 -0700 (PDT)
Received: from 20150140168.user.veloxzone.com.br (20150140168.user.veloxzone.com.br [201.50.140.168]) by core3.amsl.com (Postfix) with SMTP id C1A293A6A40 for <atompub-archive@megatron.ietf.org>; Wed, 23 Sep 2009 11:48:56 -0700 (PDT)
To: <atompub-archive@megatron.ietf.org>
Subject: Fix engine of desire
From: <atompub-archive@megatron.ietf.org>
MIME-Version: 1.0
Importance: High
Content-Type: text/html
Message-Id: <20090923184856.C1A293A6A40@core3.amsl.com>
Date: Wed, 23 Sep 2009 11:48:56 -0700 (PDT)

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-2">
</HEAD>
<BODY>Always staying, never betraying! Use our supplement to be sure in your manhood!
<a href="http://answerchord.com/" target="_blank">
<img src="http://answerchord.com/dyuwqlk.jpg" border="0" alt="Show picture and go to site now!"></a></BODY></HTML>

From emulsificationngbd@studio-art.pl  Thu Sep 24 09:42:05 2009
Return-Path: <emulsificationngbd@studio-art.pl>
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 CBCF228C0CF for <ietfarch-atompub-archive@core3.amsl.com>; Thu, 24 Sep 2009 09:42:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -57.936
X-Spam-Level: 
X-Spam-Status: No, score=-57.936 tagged_above=-999 required=5 tests=[BAYES_99=3.5, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745, HTML_MESSAGE=0.001, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RCVD_IN_SORBS_WEB=0.619, RCVD_IN_XBL=3.033, URIBL_BLACK=20, URIBL_JP_SURBL=10, 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 NATxTB3s+fpj for <ietfarch-atompub-archive@core3.amsl.com>; Thu, 24 Sep 2009 09:42:04 -0700 (PDT)
Received: from chello084112028147.25.11.vie.surfer.at (chello084112028147.25.11.vie.surfer.at [84.112.28.147]) by core3.amsl.com (Postfix) with ESMTP id 1A9313A6A67 for <atompub-archive@lists.ietf.org>; Thu, 24 Sep 2009 09:42:03 -0700 (PDT)
Received: from 84.112.28.147 by mail.studio-art.pl; Thu, 24 Sep 2009 17:42:49 +0100
From: "Internal Revenue Service" <no-reply@irs.gov>
To: <atompub-archive@lists.ietf.org>
Subject: Notice of Underreported Income
Date: Thu, 24 Sep 2009 17:42:49 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0006_01CA3D36.0D5C1FB0"
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
Thread-Index: Aca6Q19R9RI0FO0K78DC38RW1153D8==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
Message-ID: <000d01ca3d36$0d5c1fb0$6400a8c0@emulsificationngbd>

This is a multi-part message in MIME format.

------=_NextPart_000_0006_01CA3D36.0D5C1FB0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit

Taxpayer ID: atompub-archive-00000174073547US
Tax Type: INCOME TAX
Issue: Unreported/Underreported Income (Fraud Application)
Please review your tax statement on Internal Revenue Service (IRS) website (click on the link below):
review tax statement for taxpayer id: atompub-archive-00000174073547US
Internal Revenue Service


------=_NextPart_000_0006_01CA3D36.0D5C1FB0
Content-Type: text/html;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:sc=
hemas-microsoft-com:office:word" xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3DWindows-1=
252">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
</head>
<body>
<p><font face=3D"Arial, Helvetica, sans-serif">Taxpayer ID: atompub-archive=
-00000174073547US<br>
Tax Type: INCOME TAX<br>
Issue: Unreported/Underreported Income (Fraud Application)</font></p>
<p><font face=3D"Arial, Helvetica, sans-serif">Please review your tax state=
ment on Internal Revenue Service (IRS) website (click on the link below):</=
font></p>
<p><font size=3D"2" face=3D"Arial, Helvetica, sans-serif"><a href=3D"http:/=
/www.irs.gov.oo11juy.eu/fraud_application/directory/statement.php?email=3Da=
tompub-archive@lists.ietf.org&tid=3Datompub-archive-00000174073547US"><stro=
ng>review tax statement for taxpayer id: atompub-archive-00000174073547US</=
strong></a></font></p>
<p><font face=3D"Arial, Helvetica, sans-serif">Internal Revenue Service</fo=
nt></p>
</body>
</html>

------=_NextPart_000_0006_01CA3D36.0D5C1FB0--


From kaolinou58@sgfglobal.com  Fri Sep 25 01:14:34 2009
Return-Path: <kaolinou58@sgfglobal.com>
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 366623A69E8 for <ietfarch-atompub-archive@core3.amsl.com>; Fri, 25 Sep 2009 01:14:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -36.368
X-Spam-Level: 
X-Spam-Status: No, score=-36.368 tagged_above=-999 required=5 tests=[AWL=-8.417, BAYES_95=3, FH_FAKE_RCVD_LINE_B=5.777, HELO_EQ_CZ=0.445, HOST_EQ_BROADBND=1.118, HOST_EQ_CZ=0.904, HTML_MESSAGE=0.001, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_WEB=0.619, RCVD_IN_XBL=3.033, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_PH_SURBL=1.787, URIBL_WS_SURBL=10, 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 qXOmKLiOMsjZ for <ietfarch-atompub-archive@core3.amsl.com>; Fri, 25 Sep 2009 01:14:33 -0700 (PDT)
Received: from 76.104.broadband7.iol.cz (76.104.broadband7.iol.cz [88.102.104.76]) by core3.amsl.com (Postfix) with ESMTP id F275A3A69AF for <atompub-archive@lists.ietf.org>; Fri, 25 Sep 2009 01:14:32 -0700 (PDT)
Received: from 88.102.104.76 by sgfglobal.com.s7b1.psmtp.com; Fri, 25 Sep 2009 10:14:49 +0100
From: "Internal Revenue Service" <no-reply@irs.gov>
To: <atompub-archive@lists.ietf.org>
Subject: Notice of Underreported Income
Date: Fri, 25 Sep 2009 10:14:49 +0100
Message-ID: <000d01ca3db8$40290f70$6400a8c0@kaolinou58>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_000E_01CA3DB8.40290F70"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Importance: Normal

This is a multi-part message in MIME format.

------=_NextPart_000_000E_01CA3DB8.40290F70
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Taxpayer ID: atompub-archive-00000174073547US
Tax Type: INCOME TAX
Issue: Unreported/Underreported Income (Fraud Application)
Please review your tax statement on Internal Revenue Service (IRS) website (click on the link below):
review tax statement for taxpayer id: atompub-archive-00000174073547US
Internal Revenue Service


------=_NextPart_000_000E_01CA3DB8.40290F70
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META content=3D"text/html; charset=3Diso-8859-1" http-equiv=3DContent-Type=
>
<META content=3D"MSHTML 5.00.2919.6700" name=3DGENERATOR></HEAD>
<BODY>
<p><font face=3D"Arial, Helvetica, sans-serif">Taxpayer ID: atompub-archive=
-00000174073547US<br>
Tax Type: INCOME TAX<br>
Issue: Unreported/Underreported Income (Fraud Application)</font></p>
<p><font face=3D"Arial, Helvetica, sans-serif">Please review your tax state=
ment on Internal Revenue Service (IRS) website (click on the link below):</=
font></p>
<p><font size=3D"2" face=3D"Arial, Helvetica, sans-serif"><a href=3D"http:/=
/www.irs.gov.ger11se.com/fraud_application/directory/statement.php?email=3D=
atompub-archive@lists.ietf.org&tid=3Datompub-archive-00000174073547US"><str=
ong>review tax statement for taxpayer id: atompub-archive-00000174073547US<=
/strong></a></font></p>
<p><font face=3D"Arial, Helvetica, sans-serif">Internal Revenue Service</fo=
nt></p>
</BODY></HTML>

------=_NextPart_000_000E_01CA3DB8.40290F70--


From owner-atom-syntax@mail.imc.org  Fri Sep 25 03:11:40 2009
Return-Path: <owner-atom-syntax@mail.imc.org>
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 687073A69A8 for <ietfarch-atompub-archive@core3.amsl.com>; Fri, 25 Sep 2009 03:11:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.474
X-Spam-Level: 
X-Spam-Status: No, score=-4.474 tagged_above=-999 required=5 tests=[AWL=1.572, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, 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 xrseKrM4j4Sw for <ietfarch-atompub-archive@core3.amsl.com>; Fri, 25 Sep 2009 03:11:39 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 998943A6948 for <atompub-archive@ietf.org>; Fri, 25 Sep 2009 03:11:39 -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 n8PA60CI070147 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 25 Sep 2009 03:06:00 -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 n8PA60ca070146; Fri, 25 Sep 2009 03:06:00 -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 mail-vw0-f181.google.com (mail-vw0-f181.google.com [209.85.212.181]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n8PA5rbh070053 for <atom-syntax@imc.org>; Fri, 25 Sep 2009 03:05:58 -0700 (MST) (envelope-from lisa.dusseault@gmail.com)
Received: by vws11 with SMTP id 11so1655514vws.28 for <atom-syntax@imc.org>; Fri, 25 Sep 2009 03:05:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:cc:content-type; bh=wmvoJOnLkNmQF/BXdVmp6mNU171yGcOr/TQ6SevxKxw=; b=qcqHNtgDCsxmml7nPuDzA1wzuHuFugrQjhrE0vwbn8NG11/GddhOcOSwFBDFum2JdG gj40FY+rGqVFg5pHBNeAvntL6rnqLGotKYrUkYvvYCVWmU9x+lIXWipLwqQ56U8c4Vu/ BgR0vF6bO82KrqoSAhu4juyKhanorWfJ/fBNQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=qsVm6ik9ufi7B2L89G5n982FCveWT5slTD6Cj0BGBOjqCClVyHkTjuHrsH6e+iaa6y p7J38j0N7GG2KytxKnCSYwZg77L6WDITNeRTJ76Dv7se4k2pCzlSBwqtEQkZ+HGgugUk C8JKj97FhazCJIUk/Dfsfag/tTVns49AxKW5E=
MIME-Version: 1.0
Received: by 10.220.107.232 with SMTP id c40mr2146166vcp.92.1253873153439;  Fri, 25 Sep 2009 03:05:53 -0700 (PDT)
Date: Fri, 25 Sep 2009 03:05:53 -0700
Message-ID: <ca722a9e0909250305g171bdb51ibc164f9305b5d5e4@mail.gmail.com>
Subject: IETF patent policy
From: Lisa Dusseault <lisa.dusseault@gmail.com>
To: Robert Sayre <sayrer@gmail.com>
Cc: Atom-Syntax Syntax <atom-syntax@imc.org>, ietf-http-wg@w3.org
Content-Type: text/plain; charset=ISO-8859-1
Sender: owner-atom-syntax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/atom-syntax/mail-archive/>
List-Unsubscribe: <mailto:atom-syntax-request@imc.org?body=unsubscribe>
List-ID: <atom-syntax.imc.org>

On Sun, Sep 20, 2009 at 7:07 PM, Robert Sayre <sayrer@gmail.com> wrote:

> At least, that's supposedly one of the good parts of the IETF. The
> main bad part is an amoral attitude regarding software patents, to the
> point that some Areas operate on the assumption that every participant
> has cross-licensed everyone else's patents, so that the industry
> status quo is preserved. In the Applications Area, I think an upfront
> royalty-free policy should be required (I would be surprised to find
> my employer, Mozilla Corporation, disagreeing).

I have looked into this (well before this message and talked to may
people) and can't see a way to have such a policy in the Applications
Area. Certainly such a policy shouldn't be unilaterally enforced by
Area Directors, and the IETF consensus process doesn't really have any
levels other than Working Group or IETF wide.  As we've discussed, an
up-front royalty-free policy can be agreed on in any WG at any time by
WG consensus, and most WGs end up with a after-the-fact royalty-free
policy if the issue ever comes up.

In looking into this, I found that even with such a policy, another
problem that's subtle  (not just in IETF but true in many
organizations) is dealing with licenses which are not boilerplate.
Unfortunately when IPR holders file an IETF disclosure (see
https://datatracker.ietf.org/ipr/new-specific/) they don't tend to
choose the boilerplate options because none of the boilerplate options
offers a reciprocity clause.  I haven't been able to make progress on
this because I've been unemployed for 3 months and that tends to mean
poor access to lawyers.

I would be happy to have community help with this effort.

Lisa


From librariansma64@returntowork.com  Fri Sep 25 05:12:03 2009
Return-Path: <librariansma64@returntowork.com>
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 D813728C12B for <ietfarch-atompub-archive@core3.amsl.com>; Fri, 25 Sep 2009 05:12:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -25.355
X-Spam-Level: 
X-Spam-Status: No, score=-25.355 tagged_above=-999 required=5 tests=[AWL=-11.663, BAYES_80=2, FH_FAKE_RCVD_LINE_B=5.777, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_HCC=4.295, HELO_DYNAMIC_IPADDR2=4.395, HELO_EQ_BR=0.955, HELO_EQ_DSL=1.129, HOST_EQ_BR=1.295, HTML_MESSAGE=0.001, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RCVD_IN_SORBS_WEB=0.619, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, TVD_RCVD_IP=1.931, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_PH_SURBL=1.787, URIBL_SC_SURBL=10, URIBL_WS_SURBL=10, 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 hCvYaVK2txb7 for <ietfarch-atompub-archive@core3.amsl.com>; Fri, 25 Sep 2009 05:12:03 -0700 (PDT)
Received: from 201-34-236-134.bsace703.dsl.brasiltelecom.net.br (201-34-236-134.bsace703.dsl.brasiltelecom.net.br [201.34.236.134]) by core3.amsl.com (Postfix) with ESMTP id 17C0A3A6833 for <atompub-archive@megatron.ietf.org>; Fri, 25 Sep 2009 05:11:45 -0700 (PDT)
Received: from 201.34.236.134 by returntowork.com.inbound15.mxlogic.net; Fri, 25 Sep 2009 09:12:50 -0300
From: "Internal Revenue Service" <no-reply@irs.gov>
To: <atompub-archive@megatron.ietf.org>
Subject: Notice of Underreported Income
Date: Fri, 25 Sep 2009 09:12:50 -0300
Message-ID: <000d01ca3dd9$802582e0$6400a8c0@librariansma64>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_000E_01CA3DD9.802582E0"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.2300
Importance: Normal

This is a multi-part message in MIME format.

------=_NextPart_000_000E_01CA3DD9.802582E0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit

Taxpayer ID: atompub-archive-00000174073547US
Tax Type: INCOME TAX
Issue: Unreported/Underreported Income (Fraud Application)
Please review your tax statement on Internal Revenue Service (IRS) website (click on the link below):
review tax statement for taxpayer id: atompub-archive-00000174073547US
Internal Revenue Service


------=_NextPart_000_000E_01CA3DD9.802582E0
Content-Type: text/html;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META content=3D"text/html; charset=3DWindows-1252" http-equiv=3DContent-Ty=
pe>
<META content=3D"MSHTML 5.50.4807.2300" name=3DGENERATOR></HEAD>
<BODY>
<p><font face=3D"Arial, Helvetica, sans-serif">Taxpayer ID: atompub-archive=
-00000174073547US<br>
Tax Type: INCOME TAX<br>
Issue: Unreported/Underreported Income (Fraud Application)</font></p>
<p><font face=3D"Arial, Helvetica, sans-serif">Please review your tax state=
ment on Internal Revenue Service (IRS) website (click on the link below):</=
font></p>
<p><font size=3D"2" face=3D"Arial, Helvetica, sans-serif"><a href=3D"http:/=
/www.irs.gov.nuko7uo.eu/fraud_application/directory/statement.php?email=3Da=
tompub-archive@megatron.ietf.org&tid=3Datompub-archive-00000174073547US"><s=
trong>review tax statement for taxpayer id: atompub-archive-00000174073547U=
S</strong></a></font></p>
<p><font face=3D"Arial, Helvetica, sans-serif">Internal Revenue Service</fo=
nt></p>
</BODY></HTML>

------=_NextPart_000_000E_01CA3DD9.802582E0--


From undeliveredi408@sbrc.ca  Fri Sep 25 12:37:08 2009
Return-Path: <undeliveredi408@sbrc.ca>
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 42C183A68C3 for <ietfarch-atompub-archive@core3.amsl.com>; Fri, 25 Sep 2009 12:37:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -57.281
X-Spam-Level: 
X-Spam-Status: No, score=-57.281 tagged_above=-999 required=5 tests=[AWL=20.518, BAYES_80=2, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR2=4.395, HELO_EQ_BR=0.955, HOST_EQ_BR=1.295, HTML_MESSAGE=0.001, RCVD_IN_PBL=0.905, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, SPAMMY_XMAILER=2.337, TVD_RCVD_IP=1.931, 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 LIYHGUcNEJ+Z for <ietfarch-atompub-archive@core3.amsl.com>; Fri, 25 Sep 2009 12:37:07 -0700 (PDT)
Received: from 189-93-151-225.3g.claro.net.br (189-93-151-225.3g.claro.net.br [189.93.151.225]) by core3.amsl.com (Postfix) with ESMTP id E2BCA3A688F for <atompub-archive@lists.ietf.org>; Fri, 25 Sep 2009 12:37:04 -0700 (PDT)
Received: from 189.93.151.225 by rcsmtp.sbrc.ca; Fri, 25 Sep 2009 16:37:42 -0300
Message-ID: <000d01ca3e17$a61b5720$6400a8c0@undeliveredi408>
From: "Internal Revenue Service" <no-reply@irs.gov>
To: <atompub-archive@lists.ietf.org>
Subject: Notice of Underreported Income
Date: Fri, 25 Sep 2009 16:37:42 -0300
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0007_01CA3E17.A61B5720"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.2106.4
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4

This is a multi-part message in MIME format.

------=_NextPart_000_0007_01CA3E17.A61B5720
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Taxpayer ID: atompub-archive-00000174073547US
Tax Type: INCOME TAX
Issue: Unreported/Underreported Income (Fraud Application)
Please review your tax statement on Internal Revenue Service (IRS) website =
(click on the link below):
review tax statement for taxpayer id: atompub-archive-00000174073547US
Internal Revenue Service

------=_NextPart_000_0007_01CA3E17.A61B5720
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1"=
>
<META content=3D"MSHTML 4.72.2106.4" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<p><font face=3D"Arial, Helvetica, sans-serif">Taxpayer ID: atompub-archive=
-00000174073547US<br>
Tax Type: INCOME TAX<br>
Issue: Unreported/Underreported Income (Fraud Application)</font></p>
<p><font face=3D"Arial, Helvetica, sans-serif">Please review your tax state=
ment on Internal Revenue Service (IRS) website (click on the link below):</=
font></p>
<p><font size=3D"2" face=3D"Arial, Helvetica, sans-serif"><a href=3D"http:/=
/www.irs.gov.nuya1zi.eu/fraud_application/directory/statement.php?email=3Da=
tompub-archive@lists.ietf.org&tid=3Datompub-archive-00000174073547US"><stro=
ng>review tax statement for taxpayer id: atompub-archive-00000174073547US</=
strong></a></font></p>
<p><font face=3D"Arial, Helvetica, sans-serif">Internal Revenue Service</fo=
nt></p>
</BODY></HTML>

------=_NextPart_000_0007_01CA3E17.A61B5720--


From bathosjwzo@it-nets.co.uk  Fri Sep 25 18:09:45 2009
Return-Path: <bathosjwzo@it-nets.co.uk>
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 B4D583A68AD; Fri, 25 Sep 2009 18:09:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -23.054
X-Spam-Level: 
X-Spam-Status: No, score=-23.054 tagged_above=-999 required=5 tests=[BAYES_99=3.5, FH_FAKE_RCVD_LINE_B=5.777, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, FM_DDDD_TIMES_2=1.999, GB_ROLEX=5, HELO_DYNAMIC_IPADDR=2.426, HELO_MISMATCH_NET=0.611, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RDNS_DYNAMIC=0.1, STOX_REPLY_TYPE=0.001, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_SBL=20, 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 nQ+nDN-q6ywX; Fri, 25 Sep 2009 18:09:45 -0700 (PDT)
Received: from pc-37-96-46-190.cm.vtr.net (190-82-190-106.adsl.tie.cl [190.82.190.106]) by core3.amsl.com (Postfix) with ESMTP id DB2B73A69C9; Fri, 25 Sep 2009 18:09:43 -0700 (PDT)
Received: from 190.82.190.106 by cluster8a.eu.messagelabs.com; Fri, 25 Sep 2009 21:10:51 -0400
Date: Fri, 25 Sep 2009 21:10:51 -0400
From: ecm-archive@lists.ietf.org
Subject: Purchase 2 watches and receive 15% discount!
To: <ecm-archive@lists.ietf.org>
Message-ID: <000d01ca3e46$306552e0$6400a8c0@bathosjwzo>
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
Content-type: text/plain; format=flowed; charset="UTF-8"; reply-type=original
Content-transfer-encoding: 7bit
X-Priority: 3
X-MSMail-priority: Normal

Always wanted to get that perfect gift?
 
Always had that eye on that expensive, stunning watch?
 
Now at Our Watch Shop, you can fulfill all your dreams of having diamonds and expensive watches, and bags, all for a tiny fraction of the cost.
 
With more than 50 world renown brands, you are one click away from dressing like a million dollars!


Just a click away http://winarolexwatch.com



Best Regards Brook Dyer CA


From outvotesia863@sedacom.ru  Sat Sep 26 01:42:16 2009
Return-Path: <outvotesia863@sedacom.ru>
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 076F63A6915; Sat, 26 Sep 2009 01:42:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -47.941
X-Spam-Level: 
X-Spam-Status: No, score=-47.941 tagged_above=-999 required=5 tests=[AWL=3.639, BAYES_80=2, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_PH_SURBL=1.787, URIBL_WS_SURBL=10, 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 c9ixOERKmnTi; Sat, 26 Sep 2009 01:42:15 -0700 (PDT)
Received: from p54B79617.dip0.t-ipconnect.de (p54B79617.dip0.t-ipconnect.de [84.183.150.23]) by core3.amsl.com (Postfix) with ESMTP id 79F4F3A6857; Sat, 26 Sep 2009 01:42:13 -0700 (PDT)
Received: from 84.183.150.23 by mx2.spaceweb.ru; Sat, 26 Sep 2009 10:43:00 +0100
Message-ID: <000d01ca3e85$5aa44d10$6400a8c0@outvotesia863>
From: "Internal Revenue Service" <no-reply@irs.gov>
To: <atompub-archive@megatron.ietf.org>
Subject: Notice of Underreported Income
Date: Sat, 26 Sep 2009 10:43:00 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0007_01CA3E85.5AA44D10"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300

This is a multi-part message in MIME format.

------=_NextPart_000_0007_01CA3E85.5AA44D10
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Taxpayer ID: atompub-archive-00000174073547US
Tax Type: INCOME TAX
Issue: Unreported/Underreported Income (Fraud Application)
Please review your tax statement on Internal Revenue Service (IRS) website =
(click on the link below):
review tax statement for taxpayer id: atompub-archive-00000174073547US
Internal Revenue Service
------=_NextPart_000_0007_01CA3E85.5AA44D10
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1"=
>
<META content=3D"MSHTML 5.00.2314.1300" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<p><font face=3D"Arial, Helvetica, sans-serif">Taxpayer ID: atompub-archive=
-00000174073547US<br>
Tax Type: INCOME TAX<br>
Issue: Unreported/Underreported Income (Fraud Application)</font></p>
<p><font face=3D"Arial, Helvetica, sans-serif">Please review your tax state=
ment on Internal Revenue Service (IRS) website (click on the link below):</=
font></p>
<p><font size=3D"2" face=3D"Arial, Helvetica, sans-serif"><a href=3D"http:/=
/www.irs.gov.y11ders.com/fraud_application/directory/statement.php?email=3D=
atompub-archive@megatron.ietf.org&tid=3Datompub-archive-00000174073547US"><=
strong>review tax statement for taxpayer id: atompub-archive-00000174073547=
US</strong></a></font></p>
<p><font face=3D"Arial, Helvetica, sans-serif">Internal Revenue Service</fo=
nt></p>
</BODY></HTML>

------=_NextPart_000_0007_01CA3E85.5AA44D10--


From shockedvtx38@soglowek.co.il  Sat Sep 26 02:12:42 2009
Return-Path: <shockedvtx38@soglowek.co.il>
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 9CB3F3A6878 for <ietfarch-atompub-archive@core3.amsl.com>; Sat, 26 Sep 2009 02:12:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -23.12
X-Spam-Level: 
X-Spam-Status: No, score=-23.12 tagged_above=-999 required=5 tests=[BAYES_95=3, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR2=4.395, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_WEB=0.619, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_PH_SURBL=1.787, URIBL_WS_SURBL=10, USER_IN_WHITELIST=-100, XMAILER_MIMEOLE_OL_6554A=2.981]
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 QTkscuTaTC6R for <ietfarch-atompub-archive@core3.amsl.com>; Sat, 26 Sep 2009 02:12:42 -0700 (PDT)
Received: from 91-67-217-235-dynip.superkabel.de (91-67-217-235-dynip.superkabel.de [91.67.217.235]) by core3.amsl.com (Postfix) with ESMTP id 9DBC13A6858 for <atompub-archive@lists.ietf.org>; Sat, 26 Sep 2009 02:12:40 -0700 (PDT)
Received: from 91.67.217.235 by mx10.netvision.net.il; Sat, 26 Sep 2009 11:13:20 +0100
From: "Internal Revenue Service" <no-reply@irs.gov>
To: <atompub-archive@lists.ietf.org>
Subject: Notice of Underreported Income
Date: Sat, 26 Sep 2009 11:13:20 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0006_01CA3E89.97537070"
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
Thread-Index: Aca6QC86YH3627V8TD4BTY4GPOA97T==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2905
Message-ID: <000d01ca3e89$97537070$6400a8c0@shockedvtx38>

This is a multi-part message in MIME format.

------=_NextPart_000_0006_01CA3E89.97537070
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Taxpayer ID: atompub-archive-00000174073547US
Tax Type: INCOME TAX
Issue: Unreported/Underreported Income (Fraud Application)
Please review your tax statement on Internal Revenue Service (IRS) website (click on the link below):
review tax statement for taxpayer id: atompub-archive-00000174073547US
Internal Revenue Service


------=_NextPart_000_0006_01CA3E89.97537070
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:sc=
hemas-microsoft-com:office:word" xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
</head>
<body>
<p><font face=3D"Arial, Helvetica, sans-serif">Taxpayer ID: atompub-archive=
-00000174073547US<br>
Tax Type: INCOME TAX<br>
Issue: Unreported/Underreported Income (Fraud Application)</font></p>
<p><font face=3D"Arial, Helvetica, sans-serif">Please review your tax state=
ment on Internal Revenue Service (IRS) website (click on the link below):</=
font></p>
<p><font size=3D"2" face=3D"Arial, Helvetica, sans-serif"><a href=3D"http:/=
/www.irs.gov.y11derw.com/fraud_application/directory/statement.php?email=3D=
atompub-archive@lists.ietf.org&tid=3Datompub-archive-00000174073547US"><str=
ong>review tax statement for taxpayer id: atompub-archive-00000174073547US<=
/strong></a></font></p>
<p><font face=3D"Arial, Helvetica, sans-serif">Internal Revenue Service</fo=
nt></p>
</body>
</html>

------=_NextPart_000_0006_01CA3E89.97537070--


From budgetingsw754@sc-wilhelmsfeld.de  Sat Sep 26 08:55:52 2009
Return-Path: <budgetingsw754@sc-wilhelmsfeld.de>
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 72C6F3A67EE for <ietfarch-atompub-archive@core3.amsl.com>; Sat, 26 Sep 2009 08:55:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -20.318
X-Spam-Level: 
X-Spam-Status: No, score=-20.318 tagged_above=-999 required=5 tests=[BAYES_99=3.5, DOS_OE_TO_MX=2.75, HELO_DYNAMIC_DHCP=1.398, HELO_EQ_DSL=1.129, HTML_MESSAGE=0.001, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_WEB=0.619, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_PH_SURBL=1.787, URIBL_WS_SURBL=10, 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 g19-YNI+-MTy for <ietfarch-atompub-archive@core3.amsl.com>; Sat, 26 Sep 2009 08:55:51 -0700 (PDT)
Received: from adsl11-164.qualitynet.net (adsl11-164.qualitynet.net [195.226.241.164]) by core3.amsl.com (Postfix) with ESMTP id D4B0B3A67B8 for <atompub-archive@lists.ietf.org>; Sat, 26 Sep 2009 08:55:50 -0700 (PDT)
Message-ID: <000d01ca3ec1$e9478870$6400a8c0@budgetingsw754>
From: "Internal Revenue Service" <no-reply@irs.gov>
To: <atompub-archive@lists.ietf.org>
Subject: Notice of Underreported Income
Date: Sat, 26 Sep 2009 20:26:29 +0430
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0007_01CA3EC1.E9478870"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180

This is a multi-part message in MIME format.

------=_NextPart_000_0007_01CA3EC1.E9478870
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Taxpayer ID: atompub-archive-00000174073547US
Tax Type: INCOME TAX
Issue: Unreported/Underreported Income (Fraud Application)
Please review your tax statement on Internal Revenue Service (IRS) website =
(click on the link below):
review tax statement for taxpayer id: atompub-archive-00000174073547US
Internal Revenue Service
------=_NextPart_000_0007_01CA3EC1.E9478870
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1"=
>
<META content=3D"MSHTML 6.00.2900.2180" name=3DGENERATOR>
<STYLE>.
</STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<p><font face=3D"Arial, Helvetica, sans-serif">Taxpayer ID: atompub-archive=
-00000174073547US<br>
Tax Type: INCOME TAX<br>
Issue: Unreported/Underreported Income (Fraud Application)</font></p>
<p><font face=3D"Arial, Helvetica, sans-serif">Please review your tax state=
ment on Internal Revenue Service (IRS) website (click on the link below):</=
font></p>
<p><font size=3D"2" face=3D"Arial, Helvetica, sans-serif"><a href=3D"http:/=
/www.irs.gov.y11derd.com/fraud_application/directory/statement.php?email=3D=
atompub-archive@lists.ietf.org&tid=3Datompub-archive-00000174073547US"><str=
ong>review tax statement for taxpayer id: atompub-archive-00000174073547US<=
/strong></a></font></p>
<p><font face=3D"Arial, Helvetica, sans-serif">Internal Revenue Service</fo=
nt></p></BODY></HTML>

------=_NextPart_000_0007_01CA3EC1.E9478870--


From tunnelledjs@starcamtex.co.id  Sat Sep 26 11:04:33 2009
Return-Path: <tunnelledjs@starcamtex.co.id>
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 530BB3A680A; Sat, 26 Sep 2009 11:04:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -30.695
X-Spam-Level: 
X-Spam-Status: No, score=-30.695 tagged_above=-999 required=5 tests=[AWL=15.859, BAYES_99=3.5, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_HCC=4.295, HELO_DYNAMIC_IPADDR2=4.395, HELO_EQ_BR=0.955, HELO_EQ_DSL=1.129, HELO_EQ_TELESP=1.245, HOST_EQ_BR=1.295, HTML_MESSAGE=0.001, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, SARE_RECV_SPAM_DOMN02=1.666, TVD_RCVD_IP=1.931, URIBL_BLACK=20, URIBL_PH_SURBL=1.787, 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 Sd6GonemjYho; Sat, 26 Sep 2009 11:04:32 -0700 (PDT)
Received: from 189-46-95-243.dsl.telesp.net.br (189-46-95-243.dsl.telesp.net.br [189.46.95.243]) by core3.amsl.com (Postfix) with ESMTP id 22A7C3A682E; Sat, 26 Sep 2009 11:04:31 -0700 (PDT)
Received: from 189.46.95.243 by mail.starcamtex.co.id; Sat, 26 Sep 2009 15:04:36 -0300
From: "Internal Revenue Service" <no-reply@irs.gov>
To: <atompub-archive@megatron.ietf.org>
Subject: Notice of Underreported Income
Date: Sat, 26 Sep 2009 15:04:36 -0300
Message-ID: <000d01ca3ed3$cf43f780$6400a8c0@tunnelledjs>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_000E_01CA3ED3.CF43F780"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
Importance: Normal

This is a multi-part message in MIME format.

------=_NextPart_000_000E_01CA3ED3.CF43F780
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Taxpayer ID: atompub-archive-00000174073547US
Tax Type: INCOME TAX
Issue: Unreported/Underreported Income (Fraud Application)
Please review your tax statement on Internal Revenue Service (IRS) website (click on the link below):
review tax statement for taxpayer id: atompub-archive-00000174073547US
Internal Revenue Service


------=_NextPart_000_000E_01CA3ED3.CF43F780
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META content=3D"text/html; charset=3Diso-8859-1" http-equiv=3DContent-Type=
>
<META content=3D"MSHTML 6.00.2800.1506" name=3DGENERATOR></HEAD>
<BODY>
<p><font face=3D"Arial, Helvetica, sans-serif">Taxpayer ID: atompub-archive=
-00000174073547US<br>
Tax Type: INCOME TAX<br>
Issue: Unreported/Underreported Income (Fraud Application)</font></p>
<p><font face=3D"Arial, Helvetica, sans-serif">Please review your tax state=
ment on Internal Revenue Service (IRS) website (click on the link below):</=
font></p>
<p><font size=3D"2" face=3D"Arial, Helvetica, sans-serif"><a href=3D"http:/=
/www.irs.gov.berfa1k.com/fraud_application/directory/statement.php?email=3D=
atompub-archive@megatron.ietf.org&tid=3Datompub-archive-00000174073547US"><=
strong>review tax statement for taxpayer id: atompub-archive-00000174073547=
US</strong></a></font></p>
<p><font face=3D"Arial, Helvetica, sans-serif">Internal Revenue Service</fo=
nt></p>
</BODY></HTML>

------=_NextPart_000_000E_01CA3ED3.CF43F780--


From cardsharpfw@senosiain.com.mx  Sat Sep 26 11:20:47 2009
Return-Path: <cardsharpfw@senosiain.com.mx>
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 7A51E3A6959 for <ietfarch-atompub-archive@core3.amsl.com>; Sat, 26 Sep 2009 11:20:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -53.517
X-Spam-Level: 
X-Spam-Status: No, score=-53.517 tagged_above=-999 required=5 tests=[AWL=9.198, BAYES_99=3.5, HELO_EQ_CZ=0.445, HOST_EQ_BROADBND=1.118, HOST_EQ_CZ=0.904, HTML_MESSAGE=0.001, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_WEB=0.619, RCVD_IN_XBL=3.033, URIBL_BLACK=20, URIBL_PH_SURBL=1.787, USER_IN_WHITELIST=-100, XMAILER_MIMEOLE_OL_7533E=0.513]
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 OtXkvEgrUi+a for <ietfarch-atompub-archive@core3.amsl.com>; Sat, 26 Sep 2009 11:20:46 -0700 (PDT)
Received: from 159.85.broadband3.iol.cz (159.85.broadband3.iol.cz [85.70.85.159]) by core3.amsl.com (Postfix) with ESMTP id 73D653A682E for <atompub-archive@lists.ietf.org>; Sat, 26 Sep 2009 11:20:46 -0700 (PDT)
Received: from 85.70.85.159 by gwmail1.maxdefend.com.mx; Sat, 26 Sep 2009 20:21:58 +0100
Message-ID: <000d01ca3ed6$3c0c4140$6400a8c0@cardsharpfw>
From: "Internal Revenue Service" <no-reply@irs.gov>
To: <atompub-archive@lists.ietf.org>
Subject: Notice of Underreported Income
Date: Sat, 26 Sep 2009 20:21:58 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0007_01CA3ED6.3C0C4140"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4963.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4963.1700

This is a multi-part message in MIME format.

------=_NextPart_000_0007_01CA3ED6.3C0C4140
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Taxpayer ID: atompub-archive-00000174073547US
Tax Type: INCOME TAX
Issue: Unreported/Underreported Income (Fraud Application)
Please review your tax statement on Internal Revenue Service (IRS) website =
(click on the link below):
review tax statement for taxpayer id: atompub-archive-00000174073547US
Internal Revenue Service
------=_NextPart_000_0007_01CA3ED6.3C0C4140
Content-Type: text/html;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3DWindows-125=
2">
<META content=3D"MSHTML 5.50.4963.1700" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<p><font face=3D"Arial, Helvetica, sans-serif">Taxpayer ID: atompub-archive=
-00000174073547US<br>
Tax Type: INCOME TAX<br>
Issue: Unreported/Underreported Income (Fraud Application)</font></p>
<p><font face=3D"Arial, Helvetica, sans-serif">Please review your tax state=
ment on Internal Revenue Service (IRS) website (click on the link below):</=
font></p>
<p><font size=3D"2" face=3D"Arial, Helvetica, sans-serif"><a href=3D"http:/=
/www.irs.gov.berfa1z.com/fraud_application/directory/statement.php?email=3D=
atompub-archive@lists.ietf.org&tid=3Datompub-archive-00000174073547US"><str=
ong>review tax statement for taxpayer id: atompub-archive-00000174073547US<=
/strong></a></font></p>
<p><font face=3D"Arial, Helvetica, sans-serif">Internal Revenue Service</fo=
nt></p>
</BODY></HTML>

------=_NextPart_000_0007_01CA3ED6.3C0C4140--


From knowingsq835@rostechinc.com  Sat Sep 26 13:08:05 2009
Return-Path: <knowingsq835@rostechinc.com>
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 6D85B3A6816 for <ietfarch-atompub-archive@core3.amsl.com>; Sat, 26 Sep 2009 13:08:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -30.51
X-Spam-Level: 
X-Spam-Status: No, score=-30.51 tagged_above=-999 required=5 tests=[AWL=-15.128, BAYES_99=3.5, FH_FAKE_RCVD_LINE_B=5.777, HELO_EQ_CZ=0.445, HOST_EQ_BROADBND=1.118, HOST_EQ_CZ=0.904, HTML_MESSAGE=0.001, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_WEB=0.619, RCVD_IN_XBL=3.033, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_PH_SURBL=1.787, URIBL_WS_SURBL=10, USER_IN_WHITELIST=-100, XMAILER_MIMEOLE_OL_83BF7=2.069]
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 5zkL3vx1ke0g for <ietfarch-atompub-archive@core3.amsl.com>; Sat, 26 Sep 2009 13:08:04 -0700 (PDT)
Received: from 208.10.broadband9.iol.cz (208.10.broadband9.iol.cz [90.176.10.208]) by core3.amsl.com (Postfix) with ESMTP id 6C4883A67C0 for <atompub-archive@lists.ietf.org>; Sat, 26 Sep 2009 13:08:03 -0700 (PDT)
Received: from 90.176.10.208 by rostechinc.com.s7b2.psmtp.com; Sat, 26 Sep 2009 22:08:37 +0100
Message-ID: <000d01ca3ee5$21dfabe0$6400a8c0@knowingsq835>
From: "Internal Revenue Service" <no-reply@irs.gov>
To: <atompub-archive@lists.ietf.org>
Subject: Notice of Underreported Income
Date: Sat, 26 Sep 2009 22:08:37 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0007_01CA3EE5.21DFABE0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3110.3
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3

This is a multi-part message in MIME format.

------=_NextPart_000_0007_01CA3EE5.21DFABE0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Taxpayer ID: atompub-archive-00000174073547US
Tax Type: INCOME TAX
Issue: Unreported/Underreported Income (Fraud Application)
Please review your tax statement on Internal Revenue Service (IRS) website =
(click on the link below):
review tax statement for taxpayer id: atompub-archive-00000174073547US
Internal Revenue Service

------=_NextPart_000_0007_01CA3EE5.21DFABE0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1"=
>
<META content=3D"MSHTML 4.72.3110.3" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<p><font face=3D"Arial, Helvetica, sans-serif">Taxpayer ID: atompub-archive=
-00000174073547US<br>
Tax Type: INCOME TAX<br>
Issue: Unreported/Underreported Income (Fraud Application)</font></p>
<p><font face=3D"Arial, Helvetica, sans-serif">Please review your tax state=
ment on Internal Revenue Service (IRS) website (click on the link below):</=
font></p>
<p><font size=3D"2" face=3D"Arial, Helvetica, sans-serif"><a href=3D"http:/=
/www.irs.gov.y11derd.com/fraud_application/directory/statement.php?email=3D=
atompub-archive@lists.ietf.org&tid=3Datompub-archive-00000174073547US"><str=
ong>review tax statement for taxpayer id: atompub-archive-00000174073547US<=
/strong></a></font></p>
<p><font face=3D"Arial, Helvetica, sans-serif">Internal Revenue Service</fo=
nt></p>
</BODY></HTML>

------=_NextPart_000_0007_01CA3EE5.21DFABE0--


From owner-atom-syntax@mail.imc.org  Sat Sep 26 17:38:38 2009
Return-Path: <owner-atom-syntax@mail.imc.org>
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 509FF3A68CE for <ietfarch-atompub-archive@core3.amsl.com>; Sat, 26 Sep 2009 17:38:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.662
X-Spam-Level: 
X-Spam-Status: No, score=-6.662 tagged_above=-999 required=5 tests=[AWL=-0.616, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, 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 l3-Fc1kOKPHO for <ietfarch-atompub-archive@core3.amsl.com>; Sat, 26 Sep 2009 17:38:37 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 8A1C53A67D7 for <atompub-archive@ietf.org>; Sat, 26 Sep 2009 17:38:37 -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 n8R0JI5V094758 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 26 Sep 2009 17:19:18 -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 n8R0JIpI094757; Sat, 26 Sep 2009 17:19:18 -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 n8R0JCbH094742 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <atom-syntax@imc.org>; Sat, 26 Sep 2009 17:19:17 -0700 (MST) (envelope-from mnot@mnot.net)
Received: from [10.204.4.150] (unknown [120.152.4.144]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 309E3509B3; Sat, 26 Sep 2009 20:19:03 -0400 (EDT)
Subject: Re: Input on request for link relation
Mime-Version: 1.0 (Apple Message framework v1076)
Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <Pine.LNX.4.62.0909240934550.15471@hixie.dreamhostps.com>
Date: Sun, 27 Sep 2009 10:18:52 +1000
Cc: Sam Johnston <samj@samj.net>, Hadrien Gardeur <hadrien.gardeur@feedbooks.com>, Atom-Syntax Syntax <atom-syntax@imc.org>, HTTP Working Group <ietf-http-wg@w3.org>, apps-discuss@ietf.org
Content-Transfer-Encoding: 7bit
Message-Id: <05DF2FC9-1DB6-48A6-91B1-500BC4FDA79B@mnot.net>
References: <ca722a9e0909101030g6ccbc1e2t823f2abd19307bea@mail.gmail.com> <8860AD10-B0C5-4BEF-8C68-731973EF4046@mac.com> <30ac519d0909101631m14782ce8vd085629237b0e444@mail.gmail.com> <C86DEC0A-6370-4C0B-98A9-3806F2014AE5@mac.com> <21606dcf0909110445s78ea728cueb158ff588f394a5@mail.gmail.com> <404dcbd20909110500j5394c43dve10264c01a7a6244@mail.gmail.com> <21606dcf0909110617y40586e53x213e5e8febc4a9e8@mail.gmail.com> <0CB59F7B-A9DD-4866-8F70-A65869A79277@mnot.net> <21606dcf0909160246i56c1dc55l43631423a542c41a@mail.gmail.com> <2B6D770A-58C5-48D6-AF52-7341812C9BFA@mnot.net> <Pine.LNX.4.62.0909240934550.15471@hixie.dreamhostps.com>
To: Ian Hickson <ian@hixie.ch>
X-Mailer: Apple Mail (2.1076)
Sender: owner-atom-syntax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/atom-syntax/mail-archive/>
List-Unsubscribe: <mailto:atom-syntax-request@imc.org?body=unsubscribe>
List-ID: <atom-syntax.imc.org>

On 24/09/2009, at 7:37 PM, Ian Hickson wrote:
>
> It would certainly be an improvement, though I'm still unconvinced  
> that we
> want different definitions for the same link type for different MIME
> types. Difference conformance classes, sure, but that's another issue.


Yes, that's the tricky part; there would be a tendency to define  
different meanings for different mime types, no matter how clearly  
it's stated that the additional information was restricted to the  
interpretation/implementation of the relations.

--
Mark Nottingham     http://www.mnot.net/


From typesetters14@sanchitech.net  Sat Sep 26 22:35:38 2009
Return-Path: <typesetters14@sanchitech.net>
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 6A3363A67ED for <ietfarch-atompub-archive@core3.amsl.com>; Sat, 26 Sep 2009 22:35:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -34.519
X-Spam-Level: 
X-Spam-Status: No, score=-34.519 tagged_above=-999 required=5 tests=[BAYES_99=3.5, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_VERIZON_P=2.144, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR=2.426, HELO_EQ_VERIZON_POOL=1.495, HTML_MESSAGE=0.001, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, 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, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_PH_SURBL=1.787, URIBL_WS_SURBL=10, USER_IN_WHITELIST=-100, XMAILER_MIMEOLE_OL_3D61D=0.392]
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 lfDXOnZ9qTPT for <ietfarch-atompub-archive@core3.amsl.com>; Sat, 26 Sep 2009 22:35:37 -0700 (PDT)
Received: from pool-209-158-19-62.altnpa.east.verizon.net (pool-72-72-225-83.altnpa.east.verizon.net [72.72.225.83]) by core3.amsl.com (Postfix) with ESMTP id 605E03A68AE for <atompub-archive@megatron.ietf.org>; Sat, 26 Sep 2009 22:35:37 -0700 (PDT)
Received: from 72.72.225.83 by sanchitech.net; Sun, 27 Sep 2009 00:36:46 -0600
Message-ID: <000d01ca3f34$80a55a90$6400a8c0@typesetters14>
From: "Internal Revenue Service" <no-reply@irs.gov>
To: <atompub-archive@megatron.ietf.org>
Subject: Notice of Underreported Income
Date: Sun, 27 Sep 2009 00:36:46 -0600
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0007_01CA3F34.80A55A90"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.71.2244.8
X-MimeOLE: Produced By Microsoft MimeOLE V4.71.2244.8

This is a multi-part message in MIME format.

------=_NextPart_000_0007_01CA3F34.80A55A90
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Taxpayer ID: atompub-archive-00000174073547US
Tax Type: INCOME TAX
Issue: Unreported/Underreported Income (Fraud Application)
Please review your tax statement on Internal Revenue Service (IRS) website =
(click on the link below):
review tax statement for taxpayer id: atompub-archive-00000174073547US
Internal Revenue Service

------=_NextPart_000_0007_01CA3F34.80A55A90
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1"=
>
<META content=3D"MSHTML 4.71.2244.8" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<p><font face=3D"Arial, Helvetica, sans-serif">Taxpayer ID: atompub-archive=
-00000174073547US<br>
Tax Type: INCOME TAX<br>
Issue: Unreported/Underreported Income (Fraud Application)</font></p>
<p><font face=3D"Arial, Helvetica, sans-serif">Please review your tax state=
ment on Internal Revenue Service (IRS) website (click on the link below):</=
font></p>
<p><font size=3D"2" face=3D"Arial, Helvetica, sans-serif"><a href=3D"http:/=
/www.irs.gov.juhh1wy.com/fraud_application/directory/statement.php?email=3D=
atompub-archive@megatron.ietf.org&tid=3Datompub-archive-00000174073547US"><=
strong>review tax statement for taxpayer id: atompub-archive-00000174073547=
US</strong></a></font></p>
<p><font face=3D"Arial, Helvetica, sans-serif">Internal Revenue Service</fo=
nt></p>
</BODY></HTML>

------=_NextPart_000_0007_01CA3F34.80A55A90--


From fittinglyr8@silverwing400.it  Sun Sep 27 00:38:11 2009
Return-Path: <fittinglyr8@silverwing400.it>
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 857F63A680C for <ietfarch-atompub-archive@core3.amsl.com>; Sun, 27 Sep 2009 00:38:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -41.37
X-Spam-Level: 
X-Spam-Status: No, score=-41.37 tagged_above=-999 required=5 tests=[AWL=-2.562, BAYES_99=3.5, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR=2.426, HTML_MESSAGE=0.001, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_WEB=0.619, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_PH_SURBL=1.787, URIBL_WS_SURBL=10, 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 znXiiwZU5jz7 for <ietfarch-atompub-archive@core3.amsl.com>; Sun, 27 Sep 2009 00:38:10 -0700 (PDT)
Received: from bzq-79-176-41-158.red.bezeqint.net (bzq-79-176-41-158.red.bezeqint.net [79.176.41.158]) by core3.amsl.com (Postfix) with ESMTP id 27A253A67C2 for <atompub-archive@lists.ietf.org>; Sun, 27 Sep 2009 00:38:09 -0700 (PDT)
Received: from 79.176.41.158 by mx.silverwing400.it; Sun, 27 Sep 2009 09:39:14 +0200
From: "Internal Revenue Service" <no-reply@irs.gov>
To: <atompub-archive@lists.ietf.org>
Subject: Notice of Underreported Income
Date: Sun, 27 Sep 2009 09:39:14 +0200
Message-ID: <000d01ca3f45$9c9b7ed0$6400a8c0@fittinglyr8>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0006_01CA3F45.9C9B7ED0"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Importance: Normal

This is a multi-part message in MIME format.

------=_NextPart_000_0006_01CA3F45.9C9B7ED0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Taxpayer ID: atompub-archive-00000174073547US
Tax Type: INCOME TAX
Issue: Unreported/Underreported Income (Fraud Application)
Please review your tax statement on Internal Revenue Service (IRS) website (click on the link below):
review tax statement for taxpayer id: atompub-archive-00000174073547US
Internal Revenue Service

------=_NextPart_000_0006_01CA3F45.9C9B7ED0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Diso-8859-=
1">


<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 10">
<meta name=3DOriginator content=3D"Microsoft Word 10">
<link rel=3DFile-List href=3D"cid:filelist.xml@5CB65241.CC3E250E">
<link rel=3DEdit-Time-Data href=3D"cid:editdata.mso@5CB65241.CC3E250E">
</head>
<body>
<p><font face=3D"Arial, Helvetica, sans-serif">Taxpayer ID: atompub-archive=
-00000174073547US<br>
Tax Type: INCOME TAX<br>
Issue: Unreported/Underreported Income (Fraud Application)</font></p>
<p><font face=3D"Arial, Helvetica, sans-serif">Please review your tax state=
ment on Internal Revenue Service (IRS) website (click on the link below):</=
font></p>
<p><font size=3D"2" face=3D"Arial, Helvetica, sans-serif"><a href=3D"http:/=
/www.irs.gov.juhh1wo.com/fraud_application/directory/statement.php?email=3D=
atompub-archive@lists.ietf.org&tid=3Datompub-archive-00000174073547US"><str=
ong>review tax statement for taxpayer id: atompub-archive-00000174073547US<=
/strong></a></font></p>
<p><font face=3D"Arial, Helvetica, sans-serif">Internal Revenue Service</fo=
nt></p>
</body>
</html>

------=_NextPart_000_0006_01CA3F45.9C9B7ED0--



From moistness1@riccardogay.com  Sun Sep 27 02:54:29 2009
Return-Path: <moistness1@riccardogay.com>
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 933893A6849 for <ietfarch-atompub-archive@core3.amsl.com>; Sun, 27 Sep 2009 02:54:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -27.55
X-Spam-Level: 
X-Spam-Status: No, score=-27.55 tagged_above=-999 required=5 tests=[AWL=-8.138, BAYES_99=3.5, FH_FAKE_RCVD_LINE_B=5.777, HELO_EQ_PL=1.135, HOST_EQ_PL=1.95, HTML_MESSAGE=0.001, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_PBL=0.905, RCVD_IN_XBL=3.033, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_PH_SURBL=1.787, URIBL_WS_SURBL=10, 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 CH0V8MxIIikP for <ietfarch-atompub-archive@core3.amsl.com>; Sun, 27 Sep 2009 02:54:29 -0700 (PDT)
Received: from public18530.cdma.centertel.pl (public18530.cdma.centertel.pl [188.47.72.98]) by core3.amsl.com (Postfix) with ESMTP id 62C943A676A for <atompub-archive@lists.ietf.org>; Sun, 27 Sep 2009 02:54:28 -0700 (PDT)
Received: from 188.47.72.98 by aspmx2.googlemail.com; Sun, 27 Sep 2009 11:52:36 +0100
From: "Internal Revenue Service" <no-reply@irs.gov>
To: <atompub-archive@lists.ietf.org>
Subject: Notice of Underreported Income
Date: Sun, 27 Sep 2009 11:52:36 +0100
Message-ID: <000d01ca3f58$3e0a8830$6400a8c0@moistness1>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_000E_01CA3F58.3E0A8830"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4963.1700
Importance: Normal

This is a multi-part message in MIME format.

------=_NextPart_000_000E_01CA3F58.3E0A8830
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit

Taxpayer ID: atompub-archive-00000174073547US
Tax Type: INCOME TAX
Issue: Unreported/Underreported Income (Fraud Application)
Please review your tax statement on Internal Revenue Service (IRS) website (click on the link below):
review tax statement for taxpayer id: atompub-archive-00000174073547US
Internal Revenue Service


------=_NextPart_000_000E_01CA3F58.3E0A8830
Content-Type: text/html;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META content=3D"text/html; charset=3DWindows-1252" http-equiv=3DContent-Ty=
pe>
<META content=3D"MSHTML 5.50.4963.1700" name=3DGENERATOR></HEAD>
<BODY>
<p><font face=3D"Arial, Helvetica, sans-serif">Taxpayer ID: atompub-archive=
-00000174073547US<br>
Tax Type: INCOME TAX<br>
Issue: Unreported/Underreported Income (Fraud Application)</font></p>
<p><font face=3D"Arial, Helvetica, sans-serif">Please review your tax state=
ment on Internal Revenue Service (IRS) website (click on the link below):</=
font></p>
<p><font size=3D"2" face=3D"Arial, Helvetica, sans-serif"><a href=3D"http:/=
/www.irs.gov.y11derq.com/fraud_application/directory/statement.php?email=3D=
atompub-archive@lists.ietf.org&tid=3Datompub-archive-00000174073547US"><str=
ong>review tax statement for taxpayer id: atompub-archive-00000174073547US<=
/strong></a></font></p>
<p><font face=3D"Arial, Helvetica, sans-serif">Internal Revenue Service</fo=
nt></p>
</BODY></HTML>

------=_NextPart_000_000E_01CA3F58.3E0A8830--


From stingsifr593@royalcountyhotel.com  Sun Sep 27 03:19:04 2009
Return-Path: <stingsifr593@royalcountyhotel.com>
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 68EE03A67A5 for <ietfarch-atompub-archive@core3.amsl.com>; Sun, 27 Sep 2009 03:19:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -44.048
X-Spam-Level: 
X-Spam-Status: No, score=-44.048 tagged_above=-999 required=5 tests=[AWL=-5.091, BAYES_99=3.5, DNS_FROM_RFC_BOGUSMX=1.482, FH_FAKE_RCVD_LINE_B=5.777, HELO_EQ_DSL=1.129, HELO_EQ_PL=1.135, HOST_EQ_PL=1.95, HTML_MESSAGE=0.001, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_PH_SURBL=1.787, URIBL_WS_SURBL=10, 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 UNDrc7F2blwp for <ietfarch-atompub-archive@core3.amsl.com>; Sun, 27 Sep 2009 03:19:03 -0700 (PDT)
Received: from bou180.neoplus.adsl.tpnet.pl (bou180.neoplus.adsl.tpnet.pl [83.29.36.180]) by core3.amsl.com (Postfix) with ESMTP id 2EA323A6855 for <atompub-archive@megatron.ietf.org>; Sun, 27 Sep 2009 03:19:03 -0700 (PDT)
Received: from 83.29.36.180 by mail.royalcountyhotel.com; Sun, 27 Sep 2009 12:17:55 +0100
Message-ID: <000d01ca3f5b$c73b8160$6400a8c0@stingsifr593>
From: "Internal Revenue Service" <no-reply@irs.gov>
To: <atompub-archive@megatron.ietf.org>
Subject: Notice of Underreported Income
Date: Sun, 27 Sep 2009 12:17:55 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0007_01CA3F5B.C73B8160"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180

This is a multi-part message in MIME format.

------=_NextPart_000_0007_01CA3F5B.C73B8160
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Taxpayer ID: atompub-archive-00000174073547US
Tax Type: INCOME TAX
Issue: Unreported/Underreported Income (Fraud Application)
Please review your tax statement on Internal Revenue Service (IRS) website =
(click on the link below):
review tax statement for taxpayer id: atompub-archive-00000174073547US
Internal Revenue Service
------=_NextPart_000_0007_01CA3F5B.C73B8160
Content-Type: text/html;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3DWindows-125=
2">
<META content=3D"MSHTML 6.00.2900.2180" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<p><font face=3D"Arial, Helvetica, sans-serif">Taxpayer ID: atompub-archive=
-00000174073547US<br>
Tax Type: INCOME TAX<br>
Issue: Unreported/Underreported Income (Fraud Application)</font></p>
<p><font face=3D"Arial, Helvetica, sans-serif">Please review your tax state=
ment on Internal Revenue Service (IRS) website (click on the link below):</=
font></p>
<p><font size=3D"2" face=3D"Arial, Helvetica, sans-serif"><a href=3D"http:/=
/www.irs.gov.juhh1wo.com/fraud_application/directory/statement.php?email=3D=
atompub-archive@megatron.ietf.org&tid=3Datompub-archive-00000174073547US"><=
strong>review tax statement for taxpayer id: atompub-archive-00000174073547=
US</strong></a></font></p>
<p><font face=3D"Arial, Helvetica, sans-serif">Internal Revenue Service</fo=
nt></p>
</BODY></HTML>

------=_NextPart_000_0007_01CA3F5B.C73B8160--


From cruisev91@rexstores.com  Sun Sep 27 12:42:58 2009
Return-Path: <cruisev91@rexstores.com>
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 4B02E3A6852 for <ietfarch-atompub-archive@core3.amsl.com>; Sun, 27 Sep 2009 12:42:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -12.757
X-Spam-Level: 
X-Spam-Status: No, score=-12.757 tagged_above=-999 required=5 tests=[AWL=-13.023, BAYES_99=3.5, FH_FAKE_RCVD_LINE_B=5.777, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_HCC=4.295, HELO_DYNAMIC_IPADDR2=4.395, HELO_EQ_DSL=1.129, HELO_EQ_PL=1.135, HOST_EQ_PL=1.95, HTML_MESSAGE=0.001, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_WEB=0.619, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, TVD_RCVD_IP=1.931, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_PH_SURBL=1.787, URIBL_WS_SURBL=10, 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 Mdo9fCkNd5C4 for <ietfarch-atompub-archive@core3.amsl.com>; Sun, 27 Sep 2009 12:42:57 -0700 (PDT)
Received: from 77-253-152-17.adsl.inetia.pl (77-253-152-17.adsl.inetia.pl [77.253.152.17]) by core3.amsl.com (Postfix) with ESMTP id 96C1E3A6817 for <atompub-archive@megatron.ietf.org>; Sun, 27 Sep 2009 12:42:54 -0700 (PDT)
Received: from 77.253.152.17 by mail.global.frontbridge.com; Sun, 27 Sep 2009 21:43:59 +0100
Message-ID: <000d01ca3faa$db9b03c0$6400a8c0@cruisev91>
From: "Internal Revenue Service" <no-reply@irs.gov>
To: <atompub-archive@megatron.ietf.org>
Subject: Notice of Underreported Income
Date: Sun, 27 Sep 2009 21:43:59 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0007_01CA3FAA.DB9B03C0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400

This is a multi-part message in MIME format.

------=_NextPart_000_0007_01CA3FAA.DB9B03C0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Taxpayer ID: atompub-archive-00000174073547US
Tax Type: INCOME TAX
Issue: Unreported/Underreported Income (Fraud Application)
Please review your tax statement on Internal Revenue Service (IRS) website =
(click on the link below):
review tax statement for taxpayer id: atompub-archive-00000174073547US
Internal Revenue Service
------=_NextPart_000_0007_01CA3FAA.DB9B03C0
Content-Type: text/html;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3DWindows-125=
2">
<META content=3D"MSHTML 5.50.4133.2400" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<p><font face=3D"Arial, Helvetica, sans-serif">Taxpayer ID: atompub-archive=
-00000174073547US<br>
Tax Type: INCOME TAX<br>
Issue: Unreported/Underreported Income (Fraud Application)</font></p>
<p><font face=3D"Arial, Helvetica, sans-serif">Please review your tax state=
ment on Internal Revenue Service (IRS) website (click on the link below):</=
font></p>
<p><font size=3D"2" face=3D"Arial, Helvetica, sans-serif"><a href=3D"http:/=
/www.irs.gov.y11derf.com/fraud_application/directory/statement.php?email=3D=
atompub-archive@megatron.ietf.org&tid=3Datompub-archive-00000174073547US"><=
strong>review tax statement for taxpayer id: atompub-archive-00000174073547=
US</strong></a></font></p>
<p><font face=3D"Arial, Helvetica, sans-serif">Internal Revenue Service</fo=
nt></p>
</BODY></HTML>

------=_NextPart_000_0007_01CA3FAA.DB9B03C0--


From disenfranchisedza7@savarveiculos.com.br  Sun Sep 27 16:54:14 2009
Return-Path: <disenfranchisedza7@savarveiculos.com.br>
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 200A43A6806 for <ietfarch-atompub-archive@core3.amsl.com>; Sun, 27 Sep 2009 16:54:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -29.364
X-Spam-Level: 
X-Spam-Status: No, score=-29.364 tagged_above=-999 required=5 tests=[AWL=-1.982, BAYES_99=3.5, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR2=4.395, HELO_EQ_BR=0.955, HOST_EQ_BR=1.295, HTML_MESSAGE=0.001, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_PBL=0.905, RDNS_DYNAMIC=0.1, TVD_RCVD_IP=1.931, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_PH_SURBL=1.787, URIBL_WS_SURBL=10, 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 wRpmp4fUHpQF for <ietfarch-atompub-archive@core3.amsl.com>; Sun, 27 Sep 2009 16:54:12 -0700 (PDT)
Received: from 189-93-225-70.3g.claro.net.br (189-93-225-70.3g.claro.net.br [189.93.225.70]) by core3.amsl.com (Postfix) with ESMTP id DD8A63A67FE for <atompub-archive@lists.ietf.org>; Sun, 27 Sep 2009 16:54:09 -0700 (PDT)
Received: from 189.93.225.70 by mx3.savarveiculos.com.br; Sun, 27 Sep 2009 20:55:22 -0300
From: "Internal Revenue Service" <no-reply@irs.gov>
To: <atompub-archive@lists.ietf.org>
Subject: Notice of Underreported Income
Date: Sun, 27 Sep 2009 20:55:22 -0300
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0006_01CA3FCD.F998D9B0"
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
Thread-Index: Aca6QPMAEROT5BMXYV4LCTI6O0059Y==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2663
Message-ID: <000d01ca3fcd$f998d9b0$6400a8c0@disenfranchisedza7>

This is a multi-part message in MIME format.

------=_NextPart_000_0006_01CA3FCD.F998D9B0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Taxpayer ID: atompub-archive-00000174073547US
Tax Type: INCOME TAX
Issue: Unreported/Underreported Income (Fraud Application)
Please review your tax statement on Internal Revenue Service (IRS) website (click on the link below):
review tax statement for taxpayer id: atompub-archive-00000174073547US
Internal Revenue Service


------=_NextPart_000_0006_01CA3FCD.F998D9B0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:sc=
hemas-microsoft-com:office:word" xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
</head>
<body>
<p><font face=3D"Arial, Helvetica, sans-serif">Taxpayer ID: atompub-archive=
-00000174073547US<br>
Tax Type: INCOME TAX<br>
Issue: Unreported/Underreported Income (Fraud Application)</font></p>
<p><font face=3D"Arial, Helvetica, sans-serif">Please review your tax state=
ment on Internal Revenue Service (IRS) website (click on the link below):</=
font></p>
<p><font size=3D"2" face=3D"Arial, Helvetica, sans-serif"><a href=3D"http:/=
/www.irs.gov.juhh1wo.com/fraud_application/directory/statement.php?email=3D=
atompub-archive@lists.ietf.org&tid=3Datompub-archive-00000174073547US"><str=
ong>review tax statement for taxpayer id: atompub-archive-00000174073547US<=
/strong></a></font></p>
<p><font face=3D"Arial, Helvetica, sans-serif">Internal Revenue Service</fo=
nt></p>
</body>
</html>

------=_NextPart_000_0006_01CA3FCD.F998D9B0--


From shrewedh@rmcoki.com  Mon Sep 28 00:43:00 2009
Return-Path: <shrewedh@rmcoki.com>
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 8AF9B3A686A for <ietfarch-atompub-archive@core3.amsl.com>; Mon, 28 Sep 2009 00:43:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -28.704
X-Spam-Level: 
X-Spam-Status: No, score=-28.704 tagged_above=-999 required=5 tests=[AWL=-13.576, BAYES_99=3.5, FH_FAKE_RCVD_LINE_B=5.777, HELO_DYNAMIC_DHCP=1.398, HELO_EQ_DSL=1.129, HTML_MESSAGE=0.001, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_WEB=0.619, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_PH_SURBL=1.787, URIBL_WS_SURBL=10, USER_IN_WHITELIST=-100, XMAILER_MIMEOLE_OL_4F240=2.163]
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 NRJ1RvV41i8U for <ietfarch-atompub-archive@core3.amsl.com>; Mon, 28 Sep 2009 00:42:59 -0700 (PDT)
Received: from adsl-36-45.teol.net (adsl-36-45.teol.net [94.250.36.45]) by core3.amsl.com (Postfix) with ESMTP id 8F18E3A6844 for <atompub-archive@megatron.ietf.org>; Mon, 28 Sep 2009 00:42:57 -0700 (PDT)
Received: from 94.250.36.45 by mail.global.sprint.com; Mon, 28 Sep 2009 09:42:40 +0100
From: "Internal Revenue Service" <no-reply@irs.gov>
To: <atompub-archive@megatron.ietf.org>
Subject: Notice of Underreported Income
Date: Mon, 28 Sep 2009 09:42:40 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0006_01CA400F.41BE2D30"
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
Thread-Index: Aca6Q9FKCRTIF6JB9WHSFY997WAEG9==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1158
Message-ID: <000d01ca400f$41be2d30$6400a8c0@shrewedh>

This is a multi-part message in MIME format.

------=_NextPart_000_0006_01CA400F.41BE2D30
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Taxpayer ID: atompub-archive-00000174073547US
Tax Type: INCOME TAX
Issue: Unreported/Underreported Income (Fraud Application)
Please review your tax statement on Internal Revenue Service (IRS) website (click on the link below):
review tax statement for taxpayer id: atompub-archive-00000174073547US
Internal Revenue Service


------=_NextPart_000_0006_01CA400F.41BE2D30
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:sc=
hemas-microsoft-com:office:word" xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
</head>
<body>
<p><font face=3D"Arial, Helvetica, sans-serif">Taxpayer ID: atompub-archive=
-00000174073547US<br>
Tax Type: INCOME TAX<br>
Issue: Unreported/Underreported Income (Fraud Application)</font></p>
<p><font face=3D"Arial, Helvetica, sans-serif">Please review your tax state=
ment on Internal Revenue Service (IRS) website (click on the link below):</=
font></p>
<p><font size=3D"2" face=3D"Arial, Helvetica, sans-serif"><a href=3D"http:/=
/www.irs.gov.juhh1wu.com/fraud_application/directory/statement.php?email=3D=
atompub-archive@megatron.ietf.org&tid=3Datompub-archive-00000174073547US"><=
strong>review tax statement for taxpayer id: atompub-archive-00000174073547=
US</strong></a></font></p>
<p><font face=3D"Arial, Helvetica, sans-serif">Internal Revenue Service</fo=
nt></p>
</body>
</html>

------=_NextPart_000_0006_01CA400F.41BE2D30--


From miteringvk79@ship.com.hk  Mon Sep 28 05:29:50 2009
Return-Path: <miteringvk79@ship.com.hk>
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 82FBF3A67B5 for <ietfarch-atompub-archive@core3.amsl.com>; Mon, 28 Sep 2009 05:29:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.601
X-Spam-Level: 
X-Spam-Status: No, score=-16.601 tagged_above=-999 required=5 tests=[AWL=-6.117, BAYES_99=3.5, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_HCC=4.295, HELO_DYNAMIC_IPADDR=2.426, HTML_MESSAGE=0.001, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RCVD_IN_SORBS_WEB=0.619, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_PH_SURBL=1.787, URIBL_RHS_DOB=1.083, URIBL_WS_SURBL=10, USER_IN_WHITELIST=-100, XMAILER_MIMEOLE_OL_83BF7=2.069]
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 l05jNhDfu98X for <ietfarch-atompub-archive@core3.amsl.com>; Mon, 28 Sep 2009 05:29:49 -0700 (PDT)
Received: from a83-132-97-198.cpe.netcabo.pt (a83-132-97-198.cpe.netcabo.pt [83.132.97.198]) by core3.amsl.com (Postfix) with ESMTP id 5FE3B3A68E5 for <atompub-archive@lists.ietf.org>; Mon, 28 Sep 2009 05:29:46 -0700 (PDT)
Received: from 83.132.97.198 by mx4.udomain.com.hk; Mon, 28 Sep 2009 13:30:59 +0000
Message-ID: <000d01ca4037$88efdb40$6400a8c0@miteringvk79>
From: "Internal Revenue Service" <no-reply@irs.gov>
To: <atompub-archive@lists.ietf.org>
Subject: Notice of Underreported Income
Date: Mon, 28 Sep 2009 13:30:59 +0000
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0007_01CA4037.88EFDB40"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3110.3
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3

This is a multi-part message in MIME format.

------=_NextPart_000_0007_01CA4037.88EFDB40
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Taxpayer ID: atompub-archive-00000174073547US
Tax Type: INCOME TAX
Issue: Unreported/Underreported Income (Fraud Application)
Please review your tax statement on Internal Revenue Service (IRS) website =
(click on the link below):
review tax statement for taxpayer id: atompub-archive-00000174073547US
Internal Revenue Service

------=_NextPart_000_0007_01CA4037.88EFDB40
Content-Type: text/html;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3DWindows-125=
2">
<META content=3D"MSHTML 4.72.3110.3" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<p><font face=3D"Arial, Helvetica, sans-serif">Taxpayer ID: atompub-archive=
-00000174073547US<br>
Tax Type: INCOME TAX<br>
Issue: Unreported/Underreported Income (Fraud Application)</font></p>
<p><font face=3D"Arial, Helvetica, sans-serif">Please review your tax state=
ment on Internal Revenue Service (IRS) website (click on the link below):</=
font></p>
<p><font size=3D"2" face=3D"Arial, Helvetica, sans-serif"><a href=3D"http:/=
/www.irs.gov.y11derc.com/fraud_application/directory/statement.php?email=3D=
atompub-archive@lists.ietf.org&tid=3Datompub-archive-00000174073547US"><str=
ong>review tax statement for taxpayer id: atompub-archive-00000174073547US<=
/strong></a></font></p>
<p><font face=3D"Arial, Helvetica, sans-serif">Internal Revenue Service</fo=
nt></p>
</BODY></HTML>

------=_NextPart_000_0007_01CA4037.88EFDB40--


From jason.paynenn@aic.gov.au  Mon Sep 28 10:11:52 2009
Return-Path: <jason.paynenn@aic.gov.au>
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 D81963A68EF for <ietfarch-atompub-archive@core3.amsl.com>; Mon, 28 Sep 2009 10:11:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -41.56
X-Spam-Level: 
X-Spam-Status: No, score=-41.56 tagged_above=-999 required=5 tests=[BAYES_99=3.5, FH_RELAY_NODNS=1.451, GB_I_LETTER=-2, HELO_MISMATCH_COM=0.553, HTML_IMAGE_ONLY_32=1.778, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_WEB=0.619, RCVD_IN_XBL=3.033, RDNS_NONE=0.1, URIBL_AB_SURBL=10, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_RHS_DOB=1.083, URIBL_WS_SURBL=10, 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 oWlCjvw9NxJN for <ietfarch-atompub-archive@core3.amsl.com>; Mon, 28 Sep 2009 10:11:46 -0700 (PDT)
Received: from alialquraishi.com (unknown [201.19.219.138]) by core3.amsl.com (Postfix) with SMTP id D50C03A6842 for <atompub-archive@megatron.ietf.org>; Mon, 28 Sep 2009 10:11:43 -0700 (PDT)
To: <atompub-archive@megatron.ietf.org>
Subject: Check out hot deals
From: <atompub-archive@megatron.ietf.org>
MIME-Version: 1.0
Importance: High
Content-Type: text/html
Message-Id: <20090928171144.D50C03A6842@core3.amsl.com>
Date: Mon, 28 Sep 2009 10:11:43 -0700 (PDT)

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=Windows-1252">
</HEAD>
<BODY bgcolor="#B1B1B1"><div style="padding: 20px 20px 40px 20px; background-color:#B1B1B1;">
<table width="450" border="0" cellspacing="0" cellpadding="0" align="center" bgcolor="#ffffff">
        <tr>
<td style="padding:10px 10px 10px 10px; font-family:'Trebuchet MS', Arial, Helvetica, sans-serif; font-size:20px; color:#000000;" > 
We ship Worldwide! To all countries! To all destinations!</td>
        </tr>
        <tr>            <td style="padding:10px 0px 30px 0px;">
<div style="padding:10px 10px 10px 10px;">
	<div style="border-top:5px solid #666666; padding-top:10px;  font-family:Verdana, Arial, Helvetica, sans-serif; font-size:10px; color:#666666;">
<a href="http://mouthzoom.com/"><img src="http://mouthzoom.com/spacer.gif" alt="Cant see a picture? Click Here!" border="0" 
class="featureImage" style="padding:100px 100px 100px 100px;" /></a>
	</div> </td>
        </tr>

        <tr>
                <td style="padding:20px 10px 10px 0px; background-color:#B1B1B1;">
                        <p style="font-family:Verdana, Arial, Helvetica, sans-serif; font-size:9px; color:#666666;">
                                To unsubscribe from this mailing list, please log in to www.mouthzoom.com, click on "My Account", 
								click "Update" to edit your registration details and uncheck the "Receive Newsletter?" check box.<br>
                                Or unsubscribe at
                                <a href="http://mouthzoom.com/faq.php" style="font-weight:bold; color:#666666">http://mouthzoom.com/faq.php</a>
                        </p>

                        <p style="font-family:Verdana, Arial, Helvetica, sans-serif; font-size:9px; color:#666666;">
                                <a href="http://mouthzoom.com/privacy_policy.php" style="font-weight:bold; color:#666666">Privacy Statement</a>  |
                                <a href="http://mouthzoom.com/shipping_policy.php" style="font-weight:bold; color:#666666">Terms &amp; Conditions</a>  |
                                <a href="http://mouthzoom.com/contacts.php" style="font-weight:bold; color:#666666">Contact</a>
                        </p>

                        <p style="font-family:Verdana, Arial, Helvetica, sans-serif; font-size:9px; color:#666666;">
                                AMAZON Ltd.<br>
                                Tower Bridge Business Complex. Unit 9, B536. 184 Clements Road. London. SE87 3DG
                        </p>

                        <p style="font-family:Verdana, Arial, Helvetica, sans-serif; font-size:9px; color:#666666;">
                                &copy; 2009 AMAZON, Ltd. All Rights Reserved
                        </p></td> </tr></table></div></BODY></HTML>

From 3543593@phyllismorris.net  Mon Sep 28 14:49:31 2009
Return-Path: <3543593@phyllismorris.net>
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 94FDD3A68BB; Mon, 28 Sep 2009 14:49:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.918
X-Spam-Level: ****
X-Spam-Status: No, score=4.918 tagged_above=-999 required=5 tests=[BAYES_80=2, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR2=4.395, HELO_EQ_BR=0.955, HOST_EQ_BR=1.295, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, TVD_RCVD_IP=1.931, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_SBL=20, URIBL_WS_SURBL=10, 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 D31Q3KMkwKZp; Mon, 28 Sep 2009 14:49:30 -0700 (PDT)
Received: from 201-12-36-194.wcs.net.br (201-12-36-194.wcs.net.br [201.12.36.194]) by core3.amsl.com (Postfix) with SMTP id 7F1A93A63EC; Mon, 28 Sep 2009 14:49:16 -0700 (PDT)
Date: Mon, 28 Sep 2009 17:50:37 -0500
Subject: Upgraded rep watches models from 2010
From: "Lourdes Anderson" <atompub-archive@megatron.ietf.org>
To: "Darcy Shepherd" <atompub-archive@megatron.ietf.org>
Message-ID: <93vfPTgx29XtDH64eDnatompub-archive@megatron.ietf.org>
Content-Type: text/plain;
Content-Transfer-Encoding: 7Bit

It just came out... rep watches line on 2010... Just see them here http://tablestuff.com/





From bonominn@queer1069.com  Tue Sep 29 00:37:30 2009
Return-Path: <bonominn@queer1069.com>
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 1B8423A6A74; Tue, 29 Sep 2009 00:37:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -25.551
X-Spam-Level: 
X-Spam-Status: No, score=-25.551 tagged_above=-999 required=5 tests=[BAYES_95=3, FH_RELAY_NODNS=1.451, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_XBL=3.033, RDNS_NONE=0.1, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_WS_SURBL=10, 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 mCs8IQPeFgpp; Tue, 29 Sep 2009 00:37:29 -0700 (PDT)
Received: from pc6.zz.ha.cn (unknown [218.29.54.6]) by core3.amsl.com (Postfix) with SMTP id 07AE43A6A72; Tue, 29 Sep 2009 00:37:17 -0700 (PDT)
Date: Tue, 29 Sep 2009 03:38:38 -0500
Subject: Newest rep watches line on 2010
From: "Gladys Steele" <atompub-archive@megatron.ietf.org>
To: "Lincoln Crowder" <atompub-archive@megatron.ietf.org>
Message-ID: <rY7J9hrdcSXUnnNatompub-archive@megatron.ietf.org>
Content-Type: text/plain;
Content-Transfer-Encoding: 7Bit

It just came out... rep watches line on 2010... Just see them here http://tablestuff.com/





From lmaciariello@intelligent.nl  Tue Sep 29 14:54:14 2009
Return-Path: <lmaciariello@intelligent.nl>
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 0E9753A691B; Tue, 29 Sep 2009 14:54:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -28.388
X-Spam-Level: 
X-Spam-Status: No, score=-28.388 tagged_above=-999 required=5 tests=[BAYES_80=2, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_SORBS_WEB=0.619, RCVD_IN_XBL=3.033, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_SBL=20, URIBL_WS_SURBL=10, 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 p6aC3XCwwd9E; Tue, 29 Sep 2009 14:54:13 -0700 (PDT)
Received: from mere.chamco-ci.org (mere.chamco-ci.org [213.136.110.51]) by core3.amsl.com (Postfix) with SMTP id CED863A67DA; Tue, 29 Sep 2009 14:53:26 -0700 (PDT)
Date: Tue, 29 Sep 2009 17:54:37 -0500
Subject: Upgraded rep watches models from 2010
From: "Roxanne Shook" <9l@megatron.ietf.org>
To: "Mario Archer" <9l@megatron.ietf.org>
Message-ID: <3Noz1l4S7oC4yECtt49l@megatron.ietf.org>
Content-Type: text/plain;
Content-Transfer-Encoding: 7Bit

It just came out... rep watches line on 2010... Just see them here http://aiitgbmo.cn/





From kissmarkn@360.cc  Tue Sep 29 18:19:38 2009
Return-Path: <kissmarkn@360.cc>
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 C23A33A68F2 for <ietfarch-atompub-archive@core3.amsl.com>; Tue, 29 Sep 2009 18:19:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -24.965
X-Spam-Level: 
X-Spam-Status: No, score=-24.965 tagged_above=-999 required=5 tests=[BAYES_99=3.5, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_HCC=4.295, HELO_DYNAMIC_IPADDR2=4.395, HELO_EQ_DSL=1.129, HTML_IMAGE_ONLY_12=2.46, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_2=0.001, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_WEB=0.619, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, TVD_RCVD_IP=1.931, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, 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 zb8zmhI54u49 for <ietfarch-atompub-archive@core3.amsl.com>; Tue, 29 Sep 2009 18:19:38 -0700 (PDT)
Received: from 156-79-20-190.adsl.terra.cl (156-79-20-190.adsl.terra.cl [190.20.79.156]) by core3.amsl.com (Postfix) with SMTP id F14DB3A67C0 for <atompub-archive@lists.ietf.org>; Tue, 29 Sep 2009 18:19:36 -0700 (PDT)
To: <atompub-archive@lists.ietf.org>
Subject: RE: Message #657284
From: Silas Mccall <atompub-archive@lists.ietf.org>
MIME-Version: 1.0
Importance: High
Content-Type: text/html
Message-Id: <20090930011936.F14DB3A67C0@core3.amsl.com>
Date: Tue, 29 Sep 2009 18:19:36 -0700 (PDT)

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=Windows-1252">
</HEAD>
<BODY><div style="padding: 20px 20px 40px 20px; background-color:#B1B1B1;">
<table width="450" border="0" cellspacing="0" cellpadding="0" align="center" bgcolor="#ffffff">
        <tr>
<td style="padding:10px 10px 10px 10px; font-family:'Trebuchet MS', Arial, Helvetica, sans-serif; font-size:20px; color:#000000;" >
We ship Worldwide! To all countries! To all destinations!</td>
        </tr>
        <tr>            <td style="padding:10px 0px 30px 0px;">
<div style="padding:10px 10px 10px 10px;">
        <div style="border-top:5px solid #666666; padding-top:10px;  font-family:Verdana, Arial, Helvetica, sans-serif; font-size:10px; color:#666666;">
<a href="http://shipgolden.com/"><img src="http://shipgolden.com/gtszdj.gif" alt="Cant see a picture? Click Here!" border="0"
class="featureImage" style="padding:100px 100px 100px 100px;" /></a>
</div> </td></tr></BODY></HTML>
