RE: [Sip] Status of content indirection mechanism draft

"Burger, Eric" <eburger@cantata.com> Thu, 08 June 2006 19:06 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FoPqI-0002dP-SY; Thu, 08 Jun 2006 15:06:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FoPqI-0002dK-09 for sip@ietf.org; Thu, 08 Jun 2006 15:06:54 -0400
Received: from mxgate1.brooktrout.com ([204.176.74.10]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FoPqG-0003LF-NM for sip@ietf.org; Thu, 08 Jun 2006 15:06:53 -0400
X-IronPort-AV: i="4.05,221,1146456000"; d="scan'208"; a="33873692:sNHT41798232"
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sip] Status of content indirection mechanism draft
Date: Thu, 08 Jun 2006 15:06:46 -0400
Message-ID: <330A23D8336C0346B5C1A5BB196666470303A7C8@ATLANTIS.Brooktrout.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sip] Status of content indirection mechanism draft
Thread-Index: AcZ/kOK6FyiC+ivIQ72BHJPe7LCNmALnMOzgAABAyDA=
From: "Burger, Eric" <eburger@cantata.com>
To: "Drage, Keith (Keith)" <drage@lucent.com>, Martin.Hynar@tietoenator.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Cc: sip@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Errors-To: sip-bounces@ietf.org

RFC 4483.

-----Original Message-----
From: Drage, Keith (Keith) [mailto:drage@lucent.com] 
Sent: Wednesday, May 24, 2006 8:17 PM
To: 'Martin.Hynar@tietoenator.com'; 'sip@ietf.org'
Subject: RE: [Sip] Status of content indirection mechanism draft

It is currently in AUTH48 and we are just awaiting one author to confirm
OK.

He is being chased (particularly as the publication of another RFC is
being held up by this one). Expect end of the month at the moment.

Note that one a document is is the editor's queue, it cannot by
definition expire. It is still in the drafts folder, and you can ignore
the date on the cover page. The editor's queue can be viewed here
http://www.rfc-editor.org/queue.html

regards

Keith

> -----Original Message-----
> From: Martin.Hynar@tietoenator.com 
> [mailto:Martin.Hynar@tietoenator.com]
> Sent: 24 May 2006 08:28
> To: sip@ietf.org
> Subject: [Sip] Status of content indirection mechanism draft
> 
> 
> Hi all,
> 
> I've one simple question regarding status of
> draft-ietf-sip-content-indirect-mech-05. It has expired a year ago and
> it is still in rfc editor queue. Is there planned some action 
> with that
> draft (rfc release)?
> 
> br, Martin
> 
> Martin Hynar
> Software Specialist
> 
> TietoEnator
> Czech Software Center
> Phone: +420 599 096 022
> E-mail: Martin.Hynar@TietoEnator.com
> 
> Vystavni 292/13
> CZ-709 16 Ostrava
> 
> www.tietoenator.com
> 
> 
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 

_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip

_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip