Re: [secdir] SECDIR review of draft-ietf-lemonade-profile-bis-12.txt

["Hannes Tschofenig" <[e-mail]>]

Hi Dave, 

Thanks for your quick response. 


>> Section 5.7.1 only references another specification where this  
>> capability is
>> defined, at least that's my reading. This document only defines a  
>> profile
>> and does not require any IANA considerations.
>> 
>> Here is what Section 5.7.1 says:
>> 
>> "
>> 5.7.1.  Support for PARTIAL in CATENATE and URLAUTH
>> 
>>    [IMAP-URL] introduced a new syntactic element for referencing a  
>> byte
>>    range of a message/body part.  This is done using the ;PARTIAL=
>>    field.  If an IMAP server supports PARTIAL in IMAP URL used in
>>    CATENATE and URLAUTH extensions, then it MUST advertise the URL-
>>    PARTIAL capability in the CAPABILITY response/response code.
>> "
>> 
>> 
>[IMAP-URL] defines how to construct a URL which references a  
>byte-range within a body part, and this is newer than CATENATE or  
>URLAUTH. In particular, IMAP-URL only defines syntax, not protocol,  
>and doesn't define where the various URL forms can be used at all.
>
>CATENATE and URLAUTH are both defined with the assumption that they  
>only handle URLs without this newer parameter, so the Profile  
>document defines a new capability to signal that CATENATE and URLAUTH  
>can be used with byte-range URLs as well as whole-part URLs.
>
>So yes, the profile does need to define a new capability not defined  
>within any of the referenced specifications.
>
>I'll have a think about how this can be made clearer - if you've  
>suggestions, they'd be most welcome.

Ok. Now I believe I understood this better. 


[IMAP-URL] defines a URL scheme for referencing objects on an IMAP server.
It does not define how you actually use the URL in order to get the
referenced objects. In any case, the ABNF for the URL is defined in that
document and it contains tokens that refer to specifications that are used
in the IMAP context, for example URLAUTH specified in RFC 4467. As such,
they define the semantic for these tokens. 

So, now you would like to use the token PARTIAL with the IMAP-URL. There
isn't really a separate registry of parameters for usage with the IMAP-URL,
as far as I can tell from my quick read. Section 11 of RFC 5092 only says
"Elements not defined here can be found in [ABNF], [IMAP4], [IMAPABNF], or
[URI-GEN]." Hence, this seems to mean that the tokens have to be registered
in http://www.iana.org/assignments/imap4-capabilities in order to be usable
for the IMAP-URL. 

Hence, you have to register the URL-PARTIAL token in
http://www.iana.org/assignments/imap4-capabilities in order to get this to
work. 

Is this roughly a correct summary? 

What section in
http://tools.ietf.org/html/draft-ietf-lemonade-profile-bis-12 describes the
semantic of the URL-PARTIAL token? You refer to Section 5.7.1 in the IANA
consideration section but that section doesn't really say anything in that
regard. 

Btw, maybe you should replace
"5.7.1. Support for PARTIAL in CATENATE and URLAUTH"
with 
"5.7.1. Support for URL-PARTIAL in CATENATE and URLAUTH"

Ciao
Hannes

>
>Dave.
>