Re: [dispatch] (Fwd) New Version Notification for draft-tveretin-dispatch-remote-00.txt

Note, there was also this proposal (mbus) (going back to the last century)
in MMUSIC:

*Requirements:* draft-ietf-mmusic-mbus-req-00.txt
<http://www.mbus.org/drafts/draft-ietf-mmusic-mbus-req-00.txt>

*Mbus Guidelines:* draft-ietf-mmusic-mbus-guidelines-00.txt
<http://www.mbus.org/drafts/draft-ietf-mmusic-mbus-guidelines-00.txt> (html)
<http://www.mbus.org/drafts/draft-ietf-mmusic-mbus-guidelines-00.html>

*Mbus Profile for Call Control:* draft-ietf-mmusic-mbus-call-control-00.txt
<http://www.mbus.org/drafts/draft-ietf-mmusic-mbus-call-control-00.txt>
(html)
<http://www.mbus.org/drafts/draft-ietf-mmusic-mbus-call-control-00.html>

There are some later documents that were less ambitious that also were
never progressed.  Again, you can dig through mailing list archives as I
think MBUS came up a couple more times after the initial proposal.
Regards,
Mary.

On Thu, Feb 5, 2015 at 9:08 AM, Mary Barnes <mary.ietf.barnes@gmail.com>
wrote:

> This topic has been touched on a number of times in the past. You might
> want to google sip remote call control and more specifically SIP call
> pickup and you'll find several more comprehensive documents on this topic
> including these 2 documents:
> https://tools.ietf.org/html/draft-mahy-sip-remote-cc-05
> https://tools.ietf.org/html/draft-worley-sipping-pickup-01
>
> I know there was another even more comprehensive document in MMUSIC.
>
> I'd have to go spelunking through the archives and past meeting minutes 8+
> years back to remember exactly why we haven't specifically published
> anything (obviously, the 2nd document was clear that there was not an
> intent to publish) - someone might know right off.  You might that exercise
> informative.   I think basically it's because you can do this without core
> SIP changes which is consistent with the original intent of SIP to provide
> building blocks for services and not to define service specific methods,
> etc.
>
> Regards,
> Mary
>
> On Thu, Feb 5, 2015 at 4:29 AM, Anton Tveretin <fas_vm@surguttel.ru>
> wrote:
>
>> Dear all,
>> A long-awaited I-D is finally posted!
>> I've spent 25 years to make a telephone a telephone, not this annoying
>> box. ;)
>> Surely, there are still issues to discuss.
>> For instance, should Reason go to the body, or into header? Is NOTIFY an
>> appropriate
>> method there (or should be INFO)? There was a discussion for another I-D.
>> Regards,
>> Anton.
>>
>> ------- Forwarded message follows -------
>> From:   internet-drafts@ietf.org
>> To:     "Anton Tveretin" <fas_vm@surguttel.ru>,
>>         Anton Tveretin <fas_vm@surguttel.ru>
>> Subject:        New Version Notification for
>> draft-tveretin-dispatch-remote-00.txt
>> Date sent:      Thu, 05 Feb 2015 00:35:57 -0800
>>
>>
>>
>> A new version of I-D, draft-tveretin-dispatch-remote-00.txt
>> has been successfully submitted by Anton Tveretin and posted to the
>> IETF repository.
>>
>> Name:           draft-tveretin-dispatch-remote
>> Revision:       00
>> Title:          Remote Call Control and Call Pick-up in SIP
>> Document date:  2015-02-05
>> Group:          Individual Submission
>> Pages:          8
>> URL:
>> http://www.ietf.org/internet-drafts/draft-tveretin-dispatch-remote-00.txt
>> Status:
>> https://datatracker.ietf.org/doc/draft-tveretin-dispatch-remote/
>> Htmlized:
>> http://tools.ietf.org/html/draft-tveretin-dispatch-remote-00
>>
>>
>> Abstract:
>>    This memo defines a mechanism by which a SIP user agent could inspect
>>    calls at another user agent, and control a call, including picking up
>>    for itself.
>>
>>
>>
>>
>> Please note that it may take a couple of minutes from the time of
>> submission
>> until the htmlized version and diff are available at tools.ietf.org.
>>
>> The IETF Secretariat
>>
>> ------- End of forwarded message -------
>>
>> _______________________________________________
>> dispatch mailing list
>> dispatch@ietf.org
>> https://www.ietf.org/mailman/listinfo/dispatch
>>
>
>