Re: [dispatch] New Version Notification for draft-bakker-dispatch-3gpp-ims-xml-body-handling-00.txt

Dean Willis <dean.willis@softarmor.com> Wed, 19 September 2012 04:03 UTC

Return-Path: <dean.willis@softarmor.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE8E821E8092 for <dispatch@ietfa.amsl.com>; Tue, 18 Sep 2012 21:03:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.976
X-Spam-Level:
X-Spam-Status: No, score=-102.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 21OnCDrrW3NG for <dispatch@ietfa.amsl.com>; Tue, 18 Sep 2012 21:03:01 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 9CD7D11E80E7 for <dispatch@ietf.org>; Tue, 18 Sep 2012 21:03:01 -0700 (PDT)
Received: by vbbfc26 with SMTP id fc26so745227vbb.31 for <dispatch@ietf.org>; Tue, 18 Sep 2012 21:03:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=softarmor.com; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Q3FkMUKwJyDiy/c6HXWEJ04tXIcrNHLmSxcUNHYPzIE=; b=SIFtjgU7ydCD+VC3dYllq4Hy99dae5hdZOjeoeaL5m8bWLV7z3TkIqoKi5wnaYbTgk iLwxRhpJUtrkLiNu9tiivndCrK+I/W96d8skqHsh2k1jR56+h7IpmWMs38nwEHFvq6jC LdYd9IVNdmwOMASyliHx0svjzaTsbik5RCjVY=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=Q3FkMUKwJyDiy/c6HXWEJ04tXIcrNHLmSxcUNHYPzIE=; b=MfHWjj2ua2mF9mbhq1PTCkiFzUOzpY+RXcgByyEYhH8QFVpTkDwAI4pVNV29lnU6IB XZQr5fAfajP9f6hWGRxQYxNT4suJ/V6XIFuwugipQd0cx1nQ6YhTqJIPGcT72v+DOMe2 qeE2LqIOAwBYWh4R79M80L2D/g4541iTha17aIrdmrToDdXpoJcVlsfPoHrx5SS1LuPr 31mN/UF4Qzl3+8WDRreaf+376fDarRvJj2w5r/Q51wawx/pB/4Rfy7njQg38ulhtmInn L1hfVECeNiRQxqcns0RVBT0jWbcvengQ5J2AqfrsLb2jtxK1EDYiKf/ggx/T4vgBSx8F xKug==
MIME-Version: 1.0
Received: by 10.52.74.6 with SMTP id p6mr963957vdv.124.1348027380865; Tue, 18 Sep 2012 21:03:00 -0700 (PDT)
Received: by 10.58.163.65 with HTTP; Tue, 18 Sep 2012 21:03:00 -0700 (PDT)
In-Reply-To: <CAOHm=4uveGfDggzxzqMdZgrG3OkH6=vt4kK-W+-iYX-Wdqq74w@mail.gmail.com>
References: <20120904152546.18420.91591.idtracker@ietfa.amsl.com> <155970D1DA8E174F9E46039E10E2AA351EA834@XMB104ADS.rim.net> <CAOHm=4uveGfDggzxzqMdZgrG3OkH6=vt4kK-W+-iYX-Wdqq74w@mail.gmail.com>
Date: Tue, 18 Sep 2012 23:03:00 -0500
Message-ID: <CAOHm=4tz1w1Ps+VvmpxR52EhWCY--xy5xDx3eBLUe=4F2FKLYA@mail.gmail.com>
From: Dean Willis <dean.willis@softarmor.com>
To: John-Luc Bakker <jbakker@rim.com>
Content-Type: multipart/alternative; boundary="20cf3071ca702f1c4c04ca061536"
X-Gm-Message-State: ALoCoQm8WAVZHuo6pFvJP279Ll5+8sePw5Sl2gIidmDglNDhY0WYzUKvZbAR0ZTOzgPG9eAEsM/H
Cc: "dispatch@ietf.org" <dispatch@ietf.org>
Subject: Re: [dispatch] New Version Notification for draft-bakker-dispatch-3gpp-ims-xml-body-handling-00.txt
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dispatch>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Sep 2012 04:03:03 -0000

Well, that was silly of me. There was already one out there.

On Tue, Sep 18, 2012 at 10:57 PM, Dean Willis <dean.willis@softarmor.com>wrote:

> Be advised, there appears to be extant IPR covering this approach. I've
> filed a 3rd party disclosure for the IETF process with respect to
> publication *US20090119382.
>
>
> *
>
>
> On Tue, Sep 4, 2012 at 10:30 AM, John-Luc Bakker <jbakker@rim.com> wrote:
>
>> Dear all,
>>
>> I have submitted a new version of the previous
>> "draft-bakker-sipping-3gpp-ims-xml-body-handling", taking into account the
>> various comments received. The most notable change is to submit the draft
>> to DISPATCH (instead of SIPPING) and to submit the draft for standards
>> track consideration.
>>
>> I welcome your comments.
>>
>> Kind regards,
>>
>>         John-Luc
>>
>> -----Original Message-----
>> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
>> Sent: Tuesday, September 04, 2012 10:26 AM
>> To: John-Luc Bakker
>> Subject: New Version Notification for
>> draft-bakker-dispatch-3gpp-ims-xml-body-handling-00.txt
>>
>>
>> A new version of I-D,
>> draft-bakker-dispatch-3gpp-ims-xml-body-handling-00.txt
>> has been successfully submitted by John-Luc Bakker and posted to the IETF
>> repository.
>>
>> Filename:        draft-bakker-dispatch-3gpp-ims-xml-body-handling
>> Revision:        00
>> Title:           Specification of 3GPP IM CN Subsystem XML body handling
>> Creation date:   2012-09-04
>> WG ID:           Individual Submission
>> Number of pages: 8
>> URL:
>> http://www.ietf.org/internet-drafts/draft-bakker-dispatch-3gpp-ims-xml-body-handling-00.txt
>> Status:
>> http://datatracker.ietf.org/doc/draft-bakker-dispatch-3gpp-ims-xml-body-handling
>> Htmlized:
>> http://tools.ietf.org/html/draft-bakker-dispatch-3gpp-ims-xml-body-handling-00
>>
>>
>> Abstract:
>>    This document registers new disposition-types for the Content-
>>    Disposition header field that apply to the application/3gpp-ims+xml
>>    body (part) used by 3GPP [5].  The applicability of these content-
>>    disposition values are limited to 3GPP IMS [5].  The application/
>>    3gpp-ims+xml body (part) has the following three distinct uses: (1)
>>    for redirecting the emergency session to use a different domain (e.g.
>>    using a Circuit Switched call), (2) for delivering user profile
>>    specific information from the SIP registrar to an Application Server,
>>    and (3) for causing a UAC to attempt to re-register with the IMS.
>>
>>
>>
>>
>> The IETF Secretariat
>>
>>
>> ---------------------------------------------------------------------
>> This transmission (including any attachments) may contain confidential
>> information, privileged material (including material protected by the
>> solicitor-client or other applicable privileges), or constitute non-public
>> information. Any use of this information by anyone other than the intended
>> recipient is prohibited. If you have received this transmission in error,
>> please immediately reply to the sender and delete this information from
>> your system. Use, dissemination, distribution, or reproduction of this
>> transmission by unintended recipients is not authorized and may be unlawful.
>> _______________________________________________
>> dispatch mailing list
>> dispatch@ietf.org
>> https://www.ietf.org/mailman/listinfo/dispatch
>>
>
>