Re: FW: I-D ACTION:draft-hansen-lemonade-msgctxt-videomsg-00.txt

At 11:36 16/06/04 -0400, Tony Hansen wrote:
>Graham, that bullet list was copied almost verbatim from RFC 3458. 
>(Starting from the words "As explained in RFC3458 [1]," up to "RFC 3458 
>then goes on".)
>
>And here I thought I could avoid issues by NOT changing the list. I guess 
>I was too optimistic. :-)

Hi Tony,

It's been a long time since I looked at that!  I recognize that "selecting 
a viewer" is not necessarily a problem.  I suppose that I was concerned 
that (in isolation) it reads a bit like the role of MIME content-type 
selection, which IIRC was a point of debate concerning the role of 
Message-context.

>I'll go by the concensus of the group.

Of course.  I don't think this is a big deal.

You also said, in another message:
>Also, if there are any additional message-contexts that need to be 
>defined, I think it would be worth doing it in one RFC rather than 
>multiple RFCs.

Other than the saving in documentation and approval effort, I wouldn't put 
too much weight on that;  the registry provides a place to collect things 
together.

#g
--

>         Tony Hansen
>         [email protected]
>
>Graham Klyne wrote:
>>Hi all,
>>The basic idea looks fine.
>>I'm just a little concerned that the introduction section may just 
>>slightly overplay the role of message-context:
>>[[
>>    Typical uses for this mechanism include:
>>    o  Selecting a special viewer for a given message.
>>    o  Selecting an icon indicating the kind of message in a displayed
>>       list of messages.
>>    o  Arranging messages in an inbox display.
>>    o  Filtering messages the UA presents when the user has limited
>>       access.
>>]]
>>It's the first item that has me twitching.  The primary means for 
>>selecting a viewer is, I think, the MIME content-type information.  In 
>>particular, the original Message-context design stipulated that 
>>mis-configuration of message context must not cause a failure that would 
>>not occur in its absence.
>>I'm not sure if it's really necessary to repeat this material which is 
>>really covered in the message-context spec, but if you choose to do so, 
>>I'd suggest the "selecting a special viewer" might be softened to 
>>something like "optimizing the choice of viewer".
>>Similarly, "Filtering messages the UA presents" might better be something 
>>like "Optimizing the presentation of messages".
>>#g
>>--
>>At 14:14 15/06/04 -0400, Glenn Parsons wrote:
>>
>>>Folks,
>>>
>>>Below is a proposed addition of 'video-message' to the current list of 
>>>message contexts (or hints) in RFC 3458.
>>>
>>>Let us know if you have any comments on this.
>>>
>>>If there are no comments it will proceed to IETF last call as an 
>>>individual draft.
>>>
>>>Cheers,
>>>Glenn.
>>>
>>>----------
>>>From:   [email protected]
>>>Reply To:       [email protected]
>>>Sent:   Friday, May 28, 2004 3:44 PM
>>>To:     [email protected]
>>>Subject:        I-D ACTION:draft-hansen-lemonade-msgctxt-videomsg-00.txt
>>>
>>><<...>> <<ATT4538944.txt>>
>>>A New Internet-Draft is available from the on-line Internet-Drafts 
>>>directories.
>>>
>>>         Title           : Video Message Message Context
>>>         Author(s)       : T. Hansen
>>>         Filename        : draft-hansen-lemonade-msgctxt-videomsg-00.txt
>>>         Pages           : 4
>>>         Date            : 2004-5-28
>>>
>>>The Message-Context header defined in RFC 3458 [1] describes the
>>>    context of a message (for example: fax-message or voice-message).
>>>    This specification extends the Message-Context header with one
>>>    additional context value: "video-message".
>>>
>>>    A receiving user agent (UA) may use this information as a hint to
>>>    optimally present the message.
>>>
>>>A URL for this Internet-Draft is:
>>><http://www.ietf.org/internet-drafts/draft-hansen-lemonade-msgctxt-videomsg-00.txt>http://www.ietf.org/internet-drafts/draft-hansen-lemonade-msgctxt-videomsg-00.txt 
>>>
>>>
>>>To remove yourself from the I-D Announcement list, send a message to
>>>[email protected] with the word unsubscribe in the body of 
>>>the message.
>>>You can also visit 
>>><https://www1.ietf.org/mailman/listinfo/I-D-announce>https://www1.ietf.org/mailman/listinfo/I-D-announce 
>>>
>>>to change your subscription settings.
>>>
>>>Internet-Drafts are also available by anonymous FTP. Login with the username
>>>"anonymous" and a password of your e-mail address. After logging in,
>>>type "cd internet-drafts" and then
>>>         "get draft-hansen-lemonade-msgctxt-videomsg-00.txt".
>>>
>>>A list of Internet-Drafts directories can be found in
>>><http://www.ietf.org/shadow.html>http://www.ietf.org/shadow.html
>>>or 
>>><ftp://ftp.ietf.org/ietf/1shadow-sites.txt>ftp://ftp.ietf.org/ietf/1shadow-sites.txt 
>>>
>>>
>>>Internet-Drafts can also be obtained by e-mail.
>>>
>>>Send a message to:
>>>         [email protected].
>>>In the body type:
>>>         "FILE 
>>> /internet-drafts/draft-hansen-lemonade-msgctxt-videomsg-00.txt".
>>>
>>>NOTE:   The mail server at ietf.org can return the document in
>>>         MIME-encoded form by using the "mpack" utility.  To use this
>>>         feature, insert the command "ENCODING mime" before the "FILE"
>>>         command.  To decode the response(s), you will need "munpack" or
>>>         a MIME-compliant mail reader.  Different MIME-compliant mail 
>>> readers
>>>         exhibit different behavior, especially when dealing with
>>>         "multipart" MIME messages (i.e. documents which have been split
>>>         up into multiple messages), so check your local documentation on
>>>         how to manipulate these messages.
>>>
>>>
>>>Below is the data which will enable a MIME compliant mail reader
>>>implementation to automatically retrieve the ASCII version of the
>>>Internet-Draft.
>>>
>>>To:
>>>Subject:
>>>Date: Fri, 28 May 2004 16:34:33 -0400
>>>MIME-Version: 1.0
>>>X-Mailer: Internet Mail Service (5.5.2653.19)
>>>Content-Type: multipart/mixed; 
>>>boundary="----_=_NextPart_002_01C45304.358BB5D4"
>>>
>>>
>>>
>>><ftp://internet-drafts>
>>>
>>>_______________________________________________
>>>VPIM mailing list
>>>[email protected]
>>>https://www1.ietf.org/mailman/listinfo/vpim
>>
>>------------
>>Graham Klyne
>>For email:
>>http://www.ninebynine.org/#Contact
>>
>>_______________________________________________
>>VPIM mailing list
>>[email protected]
>>https://www1.ietf.org/mailman/listinfo/vpim
>
>------------
>Graham Klyne
>For email:
>http://www.ninebynine.org/#Contact


_______________________________________________
VPIM mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/vpim