Re: [lemonade] Extend URLAUTH to fetch MIME data for bodyparts?
Neil Cook <neil.cook@noware.co.uk> Thu, 10 May 2007 11:05 UTC
Return-path: <lemonade-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hm6Sg-0005Jv-IV; Thu, 10 May 2007 07:05:30 -0400
Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1Hm6Sf-0005Jq-CQ for lemonade-confirm+ok@megatron.ietf.org; Thu, 10 May 2007 07:05:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hm6Sf-0005Ji-2o for lemonade@ietf.org; Thu, 10 May 2007 07:05:29 -0400
Received: from noware.co.uk ([82.153.134.193] helo=mail.noware.co.uk) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hm6Sd-0001Re-Gl for lemonade@ietf.org; Thu, 10 May 2007 07:05:29 -0400
Received: by mail.noware.co.uk (Postfix, from userid 1008) id CE28337B3; Thu, 10 May 2007 11:58:52 +0100 (BST)
X-CMAE-Analysis: v=1.0 c=1 a=KWikpAkKAAAA:8 a=48vgC7mUAAAA:8 a=bfLuiRfvAAAA:8 a=mjAbWKXCTECz1lwAGbQA:9 a=Y1mpE3KigAs72KIzbKMA:7 a=xE8zCyERFSmN8Mt7AZRoiFQ4qroA:4
Received: from [192.168.0.111] (noware.co.uk [82.153.134.193]) by mail.noware.co.uk (Postfix) with ESMTP id CF26036EC; Thu, 10 May 2007 11:58:51 +0100 (BST)
In-Reply-To: <14903.1178787116.488136@peirce.dave.cridland.net>
References: <FAB9F608-6CFE-4D45-BD78-ACE6F41817BB@noware.co.uk> <14903.1178787116.488136@peirce.dave.cridland.net>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <25AE0E2A-D0FD-42F3-869F-CF0B9B6C4659@noware.co.uk>
Content-Transfer-Encoding: 7bit
From: Neil Cook <neil.cook@noware.co.uk>
Subject: Re: [lemonade] Extend URLAUTH to fetch MIME data for bodyparts?
Date: Thu, 10 May 2007 12:05:24 +0100
To: Dave Cridland <dave@cridland.net>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Cc: Enhancements to Internet email to support diverse service enivronments <lemonade@ietf.org>
X-BeenThere: lemonade@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Enhancements to Internet email to support diverse service enivronments <lemonade.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/lemonade>, <mailto:lemonade-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:lemonade@ietf.org>
List-Help: <mailto:lemonade-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/lemonade>, <mailto:lemonade-request@ietf.org?subject=subscribe>
Errors-To: lemonade-bounces@ietf.org
Dave,
that seems reasonable to me.
Presumably if you did the fetch without specifying binary, you'd get
the CTE in the BODYSTRUCTURE,and could thus decode it manually?
BTW, I think media servers are probably already used to dealing with
CTE, as they can already handle HTTP URLs, which may or may not
refer to c-t-e content. However, being able to download the content
without CTE is definitely a big plus imo.
Neil.
On 10 May 2007, at 09:51, Dave Cridland wrote:
> On Thu May 10 09:32:51 2007, Neil Cook wrote:
>> Now there has been a small amount of discussion in this group on
>> how to achieve that without updating those protocols. I've been
>> thinking about it, and it seems to me that the best (and most
>> generic) fix would be to update the URLAUTH RFC to include an
>> option that specifies that the MIME data associated with the
>> bodypart should be returned.
> You can, of course, pass a URL to the MIME header of the part.
> That's doable, but it means passing two URLs to the consumer.
>
> Otherwise, I'd personally be more interested in decoding the CTE at
> source (like BINARY does), and then appending a BODYSTRUCTURE
> fragment (or similar) describing MIME headers.
>
> For example:
>
> url-full = url-simple / url-extended
> ; Changed from RFC4467
> url-simple = astring
> ; Containing authimapurlfull
> url-extended = "(" url-simple *(SP url-additional) ")"
> url-additional = "STRUCTURE" / "BINARY" / iana-token
> urlfetch-data = "*" SP "URLFETCH" 1*(SP url-simple [SP "(" url-
> additional SP stuff ")"]
> SP nstring)
>
> Now we have the syntactic glue, we can do:
>
> C: D01 URLFETCH ("imap://[...]" STRUCTURE BINARY)
> S: * URLFETCH "imap://[...]" (STRUCTURE ("audio" "mp3" [...])) {~1234}
> S: [1234 octets of binary data, containing NUL octets]
> S: D01 OK Completed
>
> Does this seem reasonable? I think it gets the streaming servers
> what they need (and at lower impact, since presumably they never
> had to deal with CTE before).
>
> Dave.
> --
> Dave Cridland - mailto:dave@cridland.net - xmpp:dwd@jabber.org
> - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
> - http://dave.cridland.net/
> Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade
>
>
> _______________________________________________
> lemonade mailing list
> lemonade@ietf.org
> https://www1.ietf.org/mailman/listinfo/lemonade
> Supplemental Web Site:
> http://www.standardstrack.com/ietf/lemonade
>
_______________________________________________
lemonade mailing list
lemonade@ietf.org
https://www1.ietf.org/mailman/listinfo/lemonade
Supplemental Web Site:
http://www.standardstrack.com/ietf/lemonade
- [lemonade] Extend URLAUTH to fetch MIME data for … Neil Cook
- Re: [lemonade] Extend URLAUTH to fetch MIME data … Dave Cridland
- Re: [lemonade] Extend URLAUTH to fetch MIME data … Neil Cook
- Re: [lemonade] Extend URLAUTH to fetch MIME data … Dave Cridland
- Re: [lemonade] Extend URLAUTH to fetch MIME data … Neil Cook
- Re: [lemonade] Extend URLAUTH to fetch MIME data … Alexey Melnikov